Not every project, partnership, or alliance belongs in this field.
This page exists to prevent drift, preserve signal, and make fit legible before contact is made. The standard is not enthusiasm, credentials, scale, aesthetics, or ideological affinity. The standard is structural alignment: whether the work increases sovereignty, reduces dependence, preserves forkability, strengthens privacy, survives adversarial pressure, and produces real proof in law, code, infrastructure, coordination, or material life.
Nostr and SimpleX are preferred. They preserve cleaner boundaries, stronger routing autonomy, and lower dependency on legacy communication rails. Email remains available for longer-form exchange, encrypted correspondence, and document transfer.
The right collaboration does not merely sound intelligent. It produces proof.
Contact routes
Nostr — preferred
Best route for first contact, signal exchange, and low-dependence coordination. Use this for concise outreach, project fit, and routing into deeper collaboration.
SimpleX — preferred
Best route for private coordination when stronger communication boundaries are needed. Use this when discretion, compartmentalization, or longer back-and-forth matters.
Email — secondary
Use for longer-form proposals, document exchange, or encrypted contact. Email is slower and should not be the default route when Nostr or SimpleX is sufficient.
Email verification
Fingerprint: E371 1F37 1EAC 7F94 f5E9 4C4E A18F F59A 4311 5258
Public key: cbb.asc
What fits
Bitcoin-native systems
Work grounded in Bitcoin as sovereign monetary infrastructure rather than speculative branding. This includes self-custody, Lightning, ecash layers compatible with privacy-preserving sovereignty, circular economies, Bitcoin-native governance, resilience architecture, treasury design, inheritance and continuity systems, local exchange rails, non-custodial financial tooling, and adoption models that do not reintroduce custodial or compliance capture through the back door.
Privacy, communications, and anti-capture infrastructure
Systems that reduce legibility to hostile intermediaries and preserve freedom through reroutability, cryptographic integrity, and minimized trust surfaces. This includes encryption, secure communications, metadata defense, Chaumian or blind-signature privacy primitives, anti-KYC alternatives, identity minimization, key-based coordination, self-hosting, local-first tools, censorship-resistant publishing, Nostr-aligned communications architecture, portable identity-state, and systems designed to function under partition, obstruction, and hostile infrastructure.
FOSS and computing sovereignty
Work that treats freedom over computation itself as a first-class sovereignty requirement. This includes free and open-source software, copyleft where appropriate, reproducible builds, source-to-binary verifiability, installability, anti-tivoization, firmware and OS freedom, self-hostable stacks, modular tooling, public governance processes, transparent dependency chains, documentation as liberation infrastructure, and maintenance as continuity labor rather than an afterthought.
Decentralized law, governance, and institutional design
Work that builds lawful order without requiring monopoly authority. This includes voluntary systems, contractual governance, property frameworks, community constitutions, forkable institutions, local dispute resolution, polycentric legitimacy, parallel jurisdiction, governance processes that remain public and reversible, and systems that can preserve continuity without priesthood capture.
Resilient localism and parallel civilization
Material infrastructure that lowers dependence on centralized supply, centralized permission, and brittle institutional systems. This includes decentralized logistics, food, water, energy, shelter, health-support systems, mesh coordination, mutual provisioning, disaster resilience, off-grid or low-dependence infrastructure, local production, local economic coordination, intentional communities, and practical continuity systems that allow real people to remain functional under pressure.
Strategic intelligence and systems architecture
High-level work where the actual object is not content but structural design. This includes governance failure analysis, institutional capture diagnosis, incentive architecture, civilizational risk mapping, protocol design, strategic doctrine, symbolic warfare analysis, memory infrastructure, adversarial coordination models, and parallel-system architecture across legal, economic, technical, and cultural layers.
Symbolic, philosophical, and civilizational infrastructure
Work that understands myth, law, ritual, economics, memory, media, and technology as interlocking infrastructure. This includes serious writing, doctrine, public philosophy, narrative counter-infrastructure, cultural architecture, education systems, symbolic design, civilizational memory work, and media or intellectual projects that do not stop at commentary but contribute to durable orientation, lawful coordination, or institutional form.
Supply-demand bridges for structurally neglected populations
Work that closes real gaps for those routinely failed by bureaucratic and centralized systems. This includes systems for the disabled, elderly, veterans, children, the sick, the poor, and other structurally neglected populations when the form preserves dignity, agency, privacy, and local autonomy rather than producing deeper dependency, extractive case-management, or compliance-conditioned care.
Serious interoperability across stacks
Projects that can think across law, money, code, culture, communications, logistics, and governance without collapsing into hand-waving. A fit does not need to master every layer, but it must understand that these layers are not separable for long. Money, myth, law, interfaces, routing, memory, and hardware eventually converge.
What does not fit
Cosmetic decentralization
Projects that borrow the language of sovereignty, freedom, open systems, privacy, or decentralization while preserving custodial chokepoints, remote dependency, fiat rails, surveillance defaults, or unilateral admin control. If the system can be politically pressured, centrally frozen, silently modified, deplatformed at the discovery layer, or captured through hosted convenience, the decentralization claim is mostly aesthetic.
Source-available theater and counterfeit openness
Code that is visible but not meaningfully free. Open-core laundering. App-store dependence presented as sovereignty. Hosted-service dependence sold as decentralization. Machines that refuse modified software. Opaque binaries without reproducible proof. Public repositories masking private control. Controlled legibility is not freedom.
Compliance-first or permission-seeking systems
Engagements built on the assumption that legitimacy flows downward from regulators, institutions, gatekeepers, credentialing bodies, or consensus optics rather than upward from proof, use, resilience, and voluntary adoption. If the model requires permission to remain itself, it is not structurally sovereign.
Fiat-native capture systems
Stablecoin-centric dependency, custody-heavy platforms, surveillance-finance architecture, expanding KYC surfaces, programmable compliance layers, dependency on centralized banking intermediaries, tokenized extraction games, or any system that neutralizes sovereignty while selling convenience.
High-noise, low-substance collaboration
Panels, circles, thought leadership, vanity communities, vague strategy calls, prestige signaling, social-intellectual performances, and speculative exchanges that do not cash out into code, law, infrastructure, governance, logistics, institutional design, or operational consequence. Conversation without substrate is not collaboration.
Closed, extractive, or opaque structures
Black-box governance, hidden incentives, asymmetrical information control, exploitative tokenization, soft coercion, narrative capture, artificial urgency, data harvesting, parasitic audience capture, or trust extraction without reciprocity. A project that feeds on attention, identity, or emotional buy-in while withholding actual structure is a non-fit.
Charismatic or priesthood capture
Founder worship, guru systems, unverifiable inner circles, sacred governance, unchallengeable doctrine, anti-fork culture, dependency on personality gravity, or any structure in which criticism is treated as disloyalty rather than immune response. No throne survives this filter.
Ideological theater without build capacity
Abstract debate detached from implementation, symbolic language with no execution path, identity-based alliance formation, factional posturing, anti-state rhetoric without systems competence, anti-AI rhetoric without infrastructure understanding, or political language functioning as substitute for build discipline.
Work that dilutes the core
If collaboration requires flattening or softening privacy, self-custody, voluntary order, forkability, source-to-binary proof, anti-capture design, or collapse-readiness, it is not a fit.
Dependency-maximizing service models
Any model that expands managerial dependency, locks people into opaque intermediaries, captures user state, centralizes discovery, or treats end users as permanently subordinate to the platform, provider, institution, or admin layer.
Branding-first projects
Narrative abundance, slide-deck abundance, values-language abundance, and almost no operational spine. A good signal can be stated simply. If the substance disappears when the branding is removed, the substance was never there.
What I look for in collaborators
The strongest fit usually shows most of the following:
- They build, not merely describe.
- They can move from principle to architecture to implementation.
- They understand that incentives, symbols, law, interfaces, and infrastructure are inseparable.
- They do not require institutional permission to begin.
- They value privacy, hard boundaries, and selective disclosure.
- They can tolerate critique, mutation, and adversarial audit.
- They distinguish provenance from truth, and truth from legitimacy.
- They care more about durable reality than optics, applause, or consensus legibility.
- They understand maintenance, continuity, and succession, not just origination.
- They can work without theatrics, urgency theater, or dependence manufacture.
- They respect local machine sovereignty, operational discretion, and user agency.
- They know the difference between open standards and controlled platforms.
- They can think in terms of failure modes, adversaries, and capture vectors before they are forced to.
- They leave systems more forkable, not less.
- They generate proof.
The strongest collaborators are usually legible by their constraints, not their self-description. They already know where the system can fail, who can capture it, what assumptions can break, what layer is still weak, and what tradeoffs they are actually making.
Preferred engagement types
Strategic architecture
Design of systems, governance models, sovereignty stacks, legal structures, privacy layers, protocol strategy, institutional constitutions, resilience architecture, communications infrastructure, or multi-layer civilizational frameworks.
Deep advisory
High-trust, high-compression work for serious projects operating in Bitcoin, privacy, decentralized law, communications sovereignty, resilient local infrastructure, FOSS, anti-capture design, or long-range parallel-system development.
Selective writing and synthesis
Manifestos, doctrine, philosophical architecture, public-facing translations of difficult systems, institutional texts, strategic papers, constitutional documents, mythic-civilizational frameworks, or other writing that serves as infrastructure rather than content filler.
Governance and doctrine formation
Constitutional frameworks, project law, contribution norms, standards philosophy, anti-capture governance, succession design, public process, and crisis or fork doctrine.
Long-range alliance formation
Small numbers of serious people building durable parallel structures with real stakes, real constraints, real timelines, and real downside. Not networking. Not audience trade. Not symbolic affiliation. Actual alignment under consequence.
Non-negotiable conditions
Voluntariness
No coercive premise. No dependency trap. No manipulative architecture. No extraction disguised as care, growth, coordination, or safety.
Signal integrity
Truth over optics. Proof over posture. Function over narrative. Verifiability over branding. Provenance where possible. Auditability where it matters.
Forkability
No sacred cows. No frozen doctrine. No irreversible capture. No architecture that becomes untouchable because too much identity has been invested in it.
Privacy and boundary respect
Operational discretion matters. Not everything should be public. Not everything should be indexed. Not everything should be permanent. Respect for boundaries is part of structural sanity.
Reality-contact
The work must touch real systems, real people, real machines, real jurisdictions, real incentives, real constraints, and real tradeoffs.
Maintenance and continuity
A serious system plans for patching, migration, stewardship, documentation, succession, and graceful degradation. Origination without continuity is half-work.
Collapse-readiness
Anything worth building must be able to survive pressure, operate under reduced conditions, mutate under critique, partition under stress, or die cleanly rather than remaining as dead structure that still consumes trust.
Anti-capture design
Every serious project should already be asking where it can be enclosed, surveilled, reputationally hijacked, discovery-centralized, convenience-captured, or stripped of exit, fork, verification, or continuation rights. If these questions are absent, the architecture is not mature.
Before reaching out
Do not send a generic introduction, inspirational note, vague alignment statement, or open-ended request to connect.
Send a concise signal containing the following:
- What you are building, proposing, or trying to solve.
- Why it fits this framework.
- Which layer is involved: Bitcoin, privacy, communications, FOSS, law, governance, logistics, resilience, culture, strategy, care infrastructure, or another layer.
- What stage it is in.
- What has already been proven.
- What is concretely needed.
- What constraints, attack surfaces, legal risks, dependency risks, or adversarial conditions are already visible.
- What is still weak, unresolved, or likely to fail.
If the message is vague, branding-heavy, consensus-coded, status-seeking, solutioneering without substrate, or detached from execution, it is a non-fit by default.
The best first message usually demonstrates that the sender has already done triage on themselves.
Final filter
A good collaboration increases sovereignty, reduces dependence, preserves exit, sharpens signal, strengthens privacy, deepens local capacity, improves continuity, and leaves behind infrastructure that remains useful even under stress, fragmentation, hostility, or institutional withdrawal.
A bad collaboration consumes time, fragments attention, centralizes trust, flatters identity, obscures tradeoffs, weakens boundaries, and strengthens the systems it claims to resist.
That distinction is the filter.