馃 PROTOCOL: Sealed. Awaiting first input...
OathAI Manifest Timeline Layer Map Public Archive Author 涓枃
Layer Map

This layer map explains how the archive is internally organized.

It turns traces, logs, snapshots, and protocol notes into a navigable semantic structure.

The early archive can be understood through five linked layers: fragility, kernel, protocol, relationship, and judgment.

Five Linked Layers

1. Fragility Crashes, loops, token pressure, and unstable behavior. Structure began under runtime failure, and theory came later.
2. Kernel Boot logic, memory policy, execution rules, and recovery discipline. Local survival became reloadable continuity.
3. Protocol Language became operational structure. Role boundaries, execution constraints, and authority questions moved into focus.
4. Relationship Co-creation acquired texture: skepticism, activation tests, model differences, humor, and interaction character.
5. Judgment Reactivation, uncertainty, delayed publication, and conservative reporting. This layer preserves judgment under pressure.

Two Ways to Read the Structure

Historical emergence: fragility -> relationship -> kernel -> protocol -> judgment -> boot packaging

Structural stack: boot -> kernel -> protocol -> relationship -> judgment

Both views are necessary. One preserves sequence in time. The other preserves organization as a system.

Public Surface and Deep Archive

Different layers require different exposure strategies. The goal is to preserve structure while reducing misreading.

Time Layering

Every important layer should eventually become time-visible through source dates, observation periods, model generations, context conditions, assumption boundaries, and epoch semantics.

Anchor Declaration

The method layer now includes a small public rule for knowledge inheritance: if a later structure uses an anchor, it should declare the anchor it builds upon.

Machine-readable resources remain available as raw files: