capture(ecosystem): the amnesiac clone — intelligence ships, the corpus stays home - #24
Open
ascalva wants to merge 7 commits into
Open
capture(ecosystem): the amnesiac clone — intelligence ships, the corpus stays home#24ascalva wants to merge 7 commits into
ascalva wants to merge 7 commits into
Conversation
…us stays home New brainstorm topic docs/brainstorms/ouroboros-cloud-clones.md, one capsule (2026-07-30T01:57Z): encrypted-backup-only cloud clones — points and edges ship, the corpus never does; per-node unseal keys with trip→flinch self-destruct; one-way key asymmetry so proper learns from clones, never the reverse; overlay of a clone's vectors/edges is on-demand, in proper's own words. Owner seed verbatim; orchestrator restructure tagged.
… local clocks, home-held brick authority Second capsule on ouroboros-cloud-clones: the trained-model analogy (weights ship, corpora don't), PROJECTION as the operative noun, brick authority at home (oq-0051 type-check: reversible = automatable), local clocks with letters as the meshing events, the harness-as-skin anatomy, the void (write-only, ack-free, study-not-interact), the L0/L1/L2 letter dial + the disk-durability switch, and the addendum sharpening L0 to vector-membership histograms per temporal cut.
… what lands Third capsule: "a mirror image of ouroboros" completes the triple (projection = the operator, image = im(pi) the individual, seed = the carrying artifact); the mirror-mirrored and real-image-at-a-distance resonances; the container-image pun is load-bearing; amnesia stays as the fidelity calibration.
…closes the door Fourth capsule: delete the unseal capability immediately after use on remote bodies. Unique birth-scoped boot key disjoint from the recovery CMK; steady state holds no invocable key (the row-3 hole shrinks to one boot moment); restart-class attacks void; trip -> self-seal becomes the image's one un-retractable act, pre-authorized at birth, whose only casualty is the live process. Home auto-disables the birth key on first letter — no ack flows back.
…tches once Fifth capsule: encrypt the whole deployment payload; only a small bootstrap shell stays plaintext. Two yolk compartments by consequence class (code+config boot-key-only; seed+stores dual-wrapped for post-mortem); hatch into tmpfs, run from RAM, disk is shell+ciphertext in every phase of life. Stronger than native EBS/AMI encryption (standing capability vs one-shot). Honest edge: the shell is the residual plaintext trust root, bounded by the pre-birth window + measured boot options.
…plements, shifts, lineages Sixth capsule: does every body carry its own models? Tiered by mission (scout=embedder-only / analyst / full); pooling structurally illegal as inherited (loopback-only core, plaintext prompts); API models coherent for public-material missions under NN-11's adapter category; the mayfly's cheap pattern is shifts within an owner-blessed lineage envelope.
…on is the one poolable model Seventh capsule: inference from one point. Partially reverses capsule-6's flat pooling ban — the embedder is the special case (stateless text->vector, holds nothing at rest, safest to share). Edge stays blind (core seals locally to the embedder pubkey, letters mechanism); embedder-node exposure splits public (NN-11 adapter, clean) vs private (attested Nitro enclave + accepted blast radius, the parked frontier). Two-channel: control queue carries attestation + endpoint, data plane seals to the attested ephemeral enclave pubkey. Bonus: a shared embedder guarantees fleet coordinate coherence (kills F6 drift). Graduates into its own note as fleet infrastructure.
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.
What
One new brainstorm topic,
docs/brainstorms/ouroboros-cloud-clones.md, with a single capsule (2026-07-30T01:57Z). Captured from owner chat under standing capture authority; the owner's seed is inside the capsule verbatim (plus a moments-later addendum), with the orchestrator restructure and its additions explicitly tagged[ORCHESTRATOR].The idea
Since document and sqlite backups must ship to the cloud encrypted anyway, a clone of Ouroboros can be spawned on any node without ever downloading the decrypted corpus — points and edges remain, no data. The amnesia frame: intelligence is shipped, not knowledge; the clone leans on inherited structure as a prepared semantic language. Per-node unseal keys make any clone individually brickable (trip → flinch: zero memory, destroy the key; AWS may keep-but-disable it for a later merge home). One-way key asymmetry: proper learns new vectors/edges from clones, never the reverse — and the flow home is lazy: proper overlays a clone's structure only on demand, in its own words.
Why
Owner chat, 2026-07-29 (local). Sibling threads it should ripen with, named in the capsule's references:
the-distributed-ecosystem(speciation),palace-instances-as-nodes,nodes-are-nodes-cross-node-protocols,kms-threat-layering(composes with the RULED oq-0057 KMS mechanism — encryption context, awskms seal).For the reviewer
Verification
Docs-only surface; read-through against the capsule template (
docs/templates/capsule.md) — seed verbatim preserved, no parked item invented, orchestrator additions tagged.🤖 Generated with Claude Code
https://claude.ai/code/session_014BV9GWAXxwSP97UVHFmeLk