Spaces:
Sleeping
Sleeping
| # Reference Traversal Continuity | |
| > **Authored by Mark Holak.** | |
| > Independent personal design, preserved verbatim as a conceptual foundation of the SleeperAgents framework. | |
| > Governed by Invariant **I9** — may not be rephrased as AI-original when cited. | |
| --- | |
| ## Thesis | |
| > **Reference traversal — the act of following a reference from one entity to another — is invariant across the kinds of entities being traversed and across the realm or representational layer the traversal currently inhabits.** | |
| > | |
| > The traversal does not truncate at realm boundaries. It does not truncate at truth-class boundaries. It does not truncate at type-layer boundaries. It does not truncate at observability boundaries. Continuity is preserved by the kernel-side bookkeeping that already exists — not by any single grammar, surface, or projection strategy. | |
| > | |
| > Projection grammars are downstream rendering decisions. They choose how to display a region of the traversal field; they neither define, constrain, nor constitute the traversal itself. | |
| This is a doctrine of **motion**, not of **geometry**. The distinction is load-bearing. | |
| --- | |
| ## What this is NOT | |
| Stated up front because the failure mode this doctrine guards against is mistaking geometric projection for the underlying invariant: | |
| - **It is not a shape.** Coil, hydra, shell, spiral, treemap, force-directed graph, list, tree, ring, hex-pack — none of these are the doctrine. They are choreographies. Many other choreographies are equally valid. The motion neither requires nor privileges any of them. | |
| - **It is not a primitive.** No new entity type, edge kind, table, or interface is implied. The kernel already has every structural ingredient. | |
| - **It is not a grammar.** Grammars (chat-lineage, equal-peer, containment-pack, future grammars) consume the motion as input and produce a rendering as output. The doctrine sits upstream of every grammar. | |
| - **It is not a UI commitment.** No /mission/ surface, inspector lens, jump primitive, or rendering convention is mandated. | |
| - **It is not a graph-theory truism.** Linked-data systems can — and many do — truncate traversal at domain boundaries, type-layer changes, or observability seams. The doctrine commits this kernel to not doing so. | |
| --- | |
| ## What this IS | |
| A kernel commitment that **the bookkeeping which makes traversal continuous is load-bearing and must remain so**. Continuity is carried by, jointly: | |
| - `entity.parent_id` — structural lineage within a layer | |
| - `entity.origin_realm` + `entity.origin_id` — identity preservation across realm boundaries | |
| - `entity.correlation_id` — process continuity across whatever the process touches | |
| - `entity.causation_id` — causal lineage across transformations | |
| - `entity.derived_from` — transformation lineage across truth-class promotions | |
| - `sa_edge.kind` (`depends`, `contains`, `flows-to`, `continues`, `influences`, `link`) — typed reference relations | |
| - `sa_subtoken_event.parent_prompt_id` — descent into a parent's internal traversal | |
| - `SA_Structural_Audit::trace_origin()` — already-implemented walker | |
| These primitives, taken together, form a **typed reference graph** that crosses every internal seam of the system without breaking. The doctrine names that crossing as a first-class commitment. | |
| --- | |
| ## The four boundaries traversal does not truncate at | |
| ### 1. Realm boundaries | |
| A traversal that begins in one realm (filesystem, GitHub Actions, chat, operating-memory, future Jira / Linear / Salesforce / etc.) does not stop at the realm's edge. It follows references into other realms. `origin_realm` distinguishes which realm an entity belongs to; it does not partition the graph. | |
| ### 2. Truth-class boundaries | |
| A traversal can cross from `canonical` (realm-authoritative) to `projected` (Core's mirror) to `derived` (deterministic computation from inputs) to `inferred` (LLM-produced) without losing the through-line. Truth class is a *fiber* over the traversal — the type of authority each step carries — not a *cut* that divides the graph. | |
| ### 3. Type-layer boundaries | |
| The user's example chain — `root → folder → file → contents → include → class → function → line → command → address` — crosses from filesystem to text to AST to source-line to instruction to memory location. Each arrow changes the kind of thing being referenced. The traversal continues. The doctrine commits the kernel to continuing to bookkeep across these layer changes. | |
| ### 4. Observability boundaries | |
| A `SubTokenEvent` is "inside" its parent prompt's invocation. A traversal does not stop at the parent's outer boundary; it descends through `parent_prompt_id` into the sub-token graph and back out. The descent is the same kind of motion as a sibling traversal — just into a finer band. | |
| --- | |
| ## Operational implications | |
| ### For adapters | |
| When a new adapter (realm) is admitted, the kernel does not require the adapter to declare *how* its entities will eventually be traversed against entities from other realms. The adapter declares its own concept_map, identity scheme, and capabilities; the cross-realm traversal is pre-authorized by this doctrine. Adapters cannot break continuity by declining to participate — every realm-projected entity is reachable as a node in the typed reference graph from day one. | |
| ### For grammars | |
| A grammar admission contract (when written) consumes a *region of the traversal field* and produces a *rendering*. The grammar does not define what is reachable — that's the kernel's typed reference graph. The grammar chooses what to *display* about it. | |
| ### For projections | |
| A projection (in the read-time sense — `SA_Projection`'s row-level `can_read` predicate, ACL filtering, membrane-veiled redaction) may filter *which entities a viewer sees*. It does not break the traversal for entities the viewer can see. Two viewers with different projection scopes are walking different visible subsets of the same continuous graph. | |
| ### For the closed primitive set (Pillar 0.9) | |
| Reference Traversal Continuity is precisely what the closed primitive set buys. Because the same small vocabulary expresses every kind of relationship — within a layer, across layers, across realms, across truth classes — there is no boundary at which the vocabulary fails. Adding a new primitive only to handle a layer crossing would be an admission that the closed set was not in fact sufficient. This doctrine commits the system to **not** doing that. New domains compose existing primitives; the traversal absorbs them. | |
| --- | |
| ## Relationship to companion doctrines | |
| This doctrine sits at the **upstream** layer of an interpretation stack that includes: | |
| - **Prime Prompt Conjecture** — describes the *compression of trajectory*. A prime prompt is itself a reference (a minimal causal pointer); reconstructing the trajectory from it is one specific kind of traversal. PPC is downstream of this doctrine in the sense that PPC's trajectory IS a traversal whose continuity this doctrine names. | |
| - **Cognitive Heatsink** — describes the *dissipation of cognition*. The heatsink's thermal-transfer steps are sub-token events; the path through the heatsink is a traversal whose continuity this doctrine names. | |
| - **Signal Telemetry Doctrine** — describes the *measurement of alignment with authored fields*. Signals are produced by participants traversing fields; the traversal is what the signal measures the alignment of. | |
| - **Pillar 0.5 (perspective projection)** — `view = project(field, viewer, overlays, permissions)`. The "field" in that function is precisely the typed reference graph this doctrine names. Projection is the rendering of the traversal at a viewer's perspective. | |
| - **Pillar 0.75 (radical transparency)** — sub-token observability is a special case of this doctrine: the observability descent through `parent_prompt_id` is a traversal that doesn't truncate at the prompt's outer boundary. | |
| - **Pillar 0.9 (closed primitive set)** — the doctrine is what makes the closure stable. New domains absorb because the existing primitives already handle layer crossings. | |
| This doctrine does not amend any of those. It names what they jointly imply about traversal continuity, the same way Signal Telemetry Doctrine names what Pillars 0.5/0.75/0.9 imply about alignment measurement. | |
| --- | |
| ## Why it matters now | |
| This doctrine is articulated immediately after the third-domain proof (GitHub Actions adapter ingesting workflow runs as entities + jobs/steps as sub-token events). The proof made the cross-domain motion concretely visible: | |
| - The same kernel that holds chat prompts (with their sub-token graphs) now holds workflow runs (with their job/step sub-token graphs) | |
| - The same projection arbiter that surfaces filesystem entities on `/mission/` now surfaces workflow runs on the same surface | |
| - The same trace endpoint that walks a chat prompt's causal chain now walks a workflow run's job/step chain | |
| - The same verdict primitive that annotates chat sub-tokens now annotates GitHub Actions steps | |
| These are not three different patterns held together by the adapter contract. They are three surface expressions of one continuous motion. The adapter contract is the gateway through which new realms enter; the motion is what they enter into. | |
| Naming the motion before the next multi-layer slice (Flow milestone, self-hosting, or any third-party realm with internal type-layer structure) is cheap. Filing the doctrine here makes the kernel's commitment legible before it has to be re-derived from first principles by future work. | |
| --- | |
| ## Non-goals | |
| - **Cryptographic guarantees of traversal integrity.** Provenance hashing exists as I4 / `provenance_hash`; tamper-evidence is its concern, not this doctrine's. | |
| - **Performance commitments.** A traversal can be expensive; the doctrine commits to its *continuity*, not its asymptotic cost. Future work on caching, materialized views, indexed traversal paths, etc. is downstream of this doctrine and constrained only by it. | |
| - **Determinism of multi-realm traversal order.** Traversal order across realms may depend on cache state, source-priority ranking, or scope walks. This doctrine commits to the existence of a continuous traversal, not to a particular ordering of it. | |
| - **Single-rendering convention.** Different grammars may render the same traversal region as wildly different geometries (and should). The doctrine pre-authorizes that variance. | |
| --- | |
| ## I9 enforcement | |
| Any AI surface that emits text derived from this doctrine — whether rephrasing it, paraphrasing the four-boundary enumeration, or describing its relationship to companion doctrines — must preserve Mark Holak's authorship credit. Stripping attribution to present this framing as AI-original is a fatal violation at publication time. Citations may reference this file and the Reference Traversal Continuity ontology entry; both route back to the authored source. | |