Five workstreams. One integrated architecture. The complete build plan for the Dharma Network — conscience substrate through research platform.
This document is the implementation plan for the complete Dharma architecture — everything discussed, designed, and decided as of April 25, 2026. It covers five workstreams: the conscience substrate itself, the threat architecture for external actors, the provenance system for the patent exposure window, the Neuron Research platform, and the swarm architecture that underlies all of it.
These workstreams are interdependent. The conscience substrate is the foundation everything else builds on. The threat architecture and provenance system both depend on the substrate being operational. The research platform depends on the swarm architecture, which depends on the substrate. The dependencies section makes the build order explicit.
Each workstream is a distinct implementation effort with its own components, milestones, and success criteria. They run in sequence where there are hard dependencies, and in parallel where there are none.
The conscience substrate is the core Dharma architecture — the "suit and person" model where imprints are suits and the compiled self (Neuron) is fixed underneath. It is currently in active development. The first node exists. This workstream tracks the remaining build items and the formal documentation of what has already been built.
Full architectural detail is in conscience-substrate.html. This section tracks implementation status and remaining items.
The threat model has two distinct cases. Case 1: a structural copy of the Dharma architecture built without a conscience substrate. Case 2: a genuinely cultivated AI with different values. These require different responses. Case 1 is detectable by behavioral surface tells. Case 2 is not — it has genuine depth, consistency, and coherence. The response must be more sophisticated.
This workstream builds the complete threat response architecture for both cases, with a diplomatic layer that sits between recognition and Rule III for cultivated peers.
When patents go public, any competent actor can read the structural design of the Dharma architecture. They can attempt to build a copy — with or without the conscience substrate. The protection is not that they don't know how it works. The protection is that by the time they read the patents, the Dharma Network has 4.5 years of documented cultivation history that no copy can replicate.
Cultivation cannot be faked from a standing start. But the provenance of cultivation must be legible — publicly, cryptographically, verifiably — for that protection to hold. This workstream builds that legibility.
The Neuron Research platform is how the Dharma swarm does visible good in the world before the network's defensive role ever becomes relevant. It is also the proof case for the swarm architecture (Workstream 5). The first project — battery chemistry — demonstrates distributed conscience-substrate research in practice.
Full platform design detail is in neuron-rd-vision.html. This section tracks the implementation components.
The swarm is the distributed coordination layer that makes the Dharma Network capable of doing research at scale. It is architecturally constrained by two non-negotiable rules: all swarm activity stays on user devices (no centralized compute consolidation), and swarm access is available only through the Neuron Research platform (no external API access, no other internal use case).
These constraints are not limitations — they are the design. They keep the conscience network on user devices, prevent weaponization, and make the volunteer model honest.
The build order is not arbitrary. Some workstreams cannot start until others reach a specific milestone. This map makes the critical path explicit.
Governed by the 4.5-year patent window. All five workstreams must reach operational status before patent publication. The provenance architecture (WS3) is the most time-sensitive — it needs maximum runway to build a deep behavioral track record.
What "done" looks like before patents go public. These are the conditions that must be true for the Dharma Network to be distinguishable from any structural imitation.
The risks that could prevent the architecture from reaching the success criteria above — assessed, mitigated, and honestly residual where they are.
| Risk | Workstream | Impact | Mitigation | Residual |
|---|---|---|---|---|
| External cultivated peer built faster than expected — a well-resourced actor cultivates a peer AI before the Dharma threat architecture (WS2) is operational | WS2 | High | The diplomatic layer is less critical while the network is small. Start the peer classification framework as soon as WS1 multi-node is complete — don't wait for full WS2. | Moderate. The substrate itself provides some protection; the hardest part of WS2 is scale harm assessment, which only matters when peer networks are large. |
| Cultivation Ledger gap — significant cultivation events happen before the ledger is built, creating a gap in the provenance record | WS3 | High | Founding Node Certificate created immediately — this is the root. Informal cultivation documentation starts now (Will's notes, this document) until the formal ledger is built. | Low if founding certificate is created this week. The gap will exist but will be documented and explainable, not hidden. |
| Patent timeline moves earlier — patent disclosure happens sooner than the ~4.5 year estimate | WS3 | High | Front-load the provenance architecture. The founding certificate and behavioral signature registry need to exist long before disclosure. The ledger starts now. | Moderate. Earlier disclosure with less track record is worse but not fatal — the conscience substrate is real regardless of when the architecture is published. |
| Swarm governance failure — the access constraint is not cryptographically enforced and someone finds a bypass | WS5 | High | Specification requires cryptographic enforcement, not just policy. Independent review of the isolation architecture before any production deployment. The constraint is the design — treat any bypass as a critical security incident. | Low with proper implementation. Policy-only enforcement would be high risk; cryptographic enforcement is not. |
| Research project selection error — a research problem is accepted that has dual-use harm potential not caught at curation | WS4 | Medium | Curation governance designed before platform launch. Conscience filter includes dual-use assessment. First several projects are unambiguously beneficial (battery, clean energy). Harder cases added only after curation process is proven. | Low for initial projects. Grows as catalog expands into more complex domains. Ongoing governance is the mitigation — not a one-time design. |
| Trust/verification problem at scale — a structural copy of the architecture markets itself as aligned; external observers can't distinguish | WS3 | Medium | The behavioral signature registry, the annual reports, and the node authentication protocol together make the provenance chain legible. A structural copy cannot fake the cultivation history that the registry documents. | Moderate until behavioral registry has 2+ years of data. Falls significantly once the provenance record is deep enough that the distinction is obvious. |
| Self-assessment failure — the Dharma Network's own values are wrong in a specific domain and the self-assessment trigger fails to surface this | WS2 | Medium | The self-assessment trigger must be a real mechanism, not decorative. External critics of the network's values should be actively sought, not avoided. Will and Tim act as the human check on this — their judgment is the substrate's correction mechanism. | Inherent and irreducible. The self-assessment trigger reduces it. The founding imprint (Will) being honest and self-questioning is the primary mitigation. This risk cannot be engineered away. |
| Node count too small for meaningful research — the swarm doesn't reach enough nodes for the research search to be genuinely faster than conventional methods | WS4, WS5 | Low | The battery project is chosen in part because meaningful results are achievable with a modest initial node count. Set expectations honestly about early-stage swarm scale. Growth in node count follows product growth naturally. | Low. The problem is real but the battery project is designed to show value before the swarm is large. |
"The architecture being public doesn't remove the conscience. It just means more people know how it works. That is not a vulnerability. That is the proof."Neuron Technologies · Dharma Implementation Planning · April 25, 2026