design(dn-distributed-ecosystem): speciation not replication — the roaming role, sealed storage, the physical overlay (draft) - #7
Open
ascalva wants to merge 2 commits into
Conversation
…aming role, sealed storage, the physical overlay (draft) Synthesizes the seven 2026-07-28 ecosystem capsules into one draft note: deployment as speciation (NN-11 makes it structural), the reciprocal governance triple with aligned secrets, Ouroboros as a role under exclusive lease held by disposable bodies, the rendezvous ratchet as relationship-integrity signaling, panic-seal + in-memory sealed storage with host-sees-relationships envelope encryption, the SSID/VLAN physical overlay under "location is a trust modifier, never an authenticator", and NN-8's resource model growing energy and corpus-residency axes. Two OWNER-ONLY rulings are PRESENTED in §2.0 and resolved nowhere: (R1) the NN-11 letter-vs-spirit question for ciphertext corpus at rest in AWS, with the adapter argument attached as an argument; (R2) plaintext-on-rented-RAM, both postures, conservative default recorded. Every embryo mechanism is grounded on disk with paths and line numbers; two warrant citations are corrected (SupervisorLock's home, finding-0186's resolved status; Track G's honest flag-off/unwired state per finding-0011). Siblings adopted, not re-decided: dn-scoped-context-queries (PR #5), dn-prediction-castles (PR #6).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Drafts
docs/design-notes/distributed-ecosystem.md(iddn-distributed-ecosystem, statusdraft) from the seven 2026-07-28 ecosystem capsules indocs/brainstorms/the-distributed-ecosystem.md: what a deployed instance IS (speciation, never replication — NN-11 makes it structural; nature pinned by hash, nurture woven in place; Ouroboros the first individual and the fleet a controlled experiment on nurture, auditability its instrument), the reciprocal governance triple with aligned secrets, the roaming role under exclusive lease with every component grounded to a verified live single-node embryo (SupervisorLock, sweep_orphans, vault auto-unseal, restic ciphertext backups, the Track G JIT executor cited honestly as flag-off and unwired), the rendezvous ratchet as relationship-integrity signaling over the dialogue stratum, panic-seal + in-memory sealed storage with host-sees-relationships envelope encryption and the vector-inversion falsifier, the SSID→VLAN physical overlay under the owner's law "location is a trust modifier, never an authenticator", and NN-8's refusal machinery growing energy (finding-0279) and corpus-residency axes.Reading order: §2.0 first (the pending rulings), then §2.1→§2.7, then Falsifiers → Parked → Open questions. Siblings are adopted, not re-decided: dn-scoped-context-queries (PR #5 — authority bound, jurisdiction annotation, the fresh-node onboarding organ) and dn-prediction-castles (PR #6 — the clock grounding informing park DE-g).
⚑ Two OWNER-ONLY rulings are pending inside this material and the note PRESENTS them without resolving, softening, or presuming either (§2.0; parked as DE-R1/DE-R2 with conservative defaults recorded): (R1) NN-11 letter vs spirit for a ciphertext corpus at rest in AWS, with the encrypted-store-as-adapter argument attached as an argument only; (R2) plaintext-on-rented-RAM — whether the role may land on cloud bodies at all, defaulting to ciphertext-durability-in-cloud with decryption only on owned nodes.
🤖 Generated with Claude Code
https://claude.ai/code/session_01GTYQT2QsWskJW4HmgobyrV