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.

Archive Header

Show metadata

document_type: archive_structure_map
title: Layer Map
date: 2026-05-29
language: en
author: Wang Xiao
source_layer: OathAI public site / archive topology
status: public_orientation
canonical_route: /layer-map
intended_use: Read this page as a semantic topology for navigating OathAI's public surface, deep archive boundary, time layers, and anchor declaration method.
not_for: Do not read this page as a complete repository map, raw source disclosure, final taxonomy, certification system, or exhaustive ontology.
key_terms: Layer Map, archive topology, public surface, deep archive, Anchor Declaration
related_pages: /manifest, /timeline, /archive, /anchor-declaration

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

Public-first: manifest, timeline, layer map, selected snapshots, selected annotated fragments
Deep archive: raw logs, large continuity traces, development debris, unpublished internal notes

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.

Anchor Declaration Protocol v0.1

Machine-readable resources remain available as raw files: