RAOS Reality Map

ACTIVE · RECONCILIATION

The Reality Map is the current structural index for the system. It does not replace raw evidence, historical records, or execution logs. Its job is to answer: what exists now, where it belongs, who controls it, what it depends on, and what evidence supports that state?

Operating boundary

Current development is intentionally concentrated on Alpha/Beta-class working surfaces. The Zero layer is held stable until the higher-level structure becomes more coherent.

This means:

• Zero remains part of the architecture and future consolidation path;
• Alpha/Beta are the preferred surfaces for current implementation and reconciliation;
• changes should remain reversible and evidence-backed where practical;
• instability found above Zero should not be pushed downward merely to make the upper layer appear clean.

Structural axes

Axis	Scope	Typical objects
A0 — Authority & Identity	ownership, authority, account relationships, control boundaries	humans, organizations, workspaces, accounts, credentials
A1 — Runtime Foundation	execution surfaces and host state	nodes, machines, OS users, services, runtimes
A2 — Network & Trust Boundary	communication and exposure boundaries	gateway, DNS, DHCP, TLS, routing, LAN/public edges
A3 — Agent Architecture	AI roles and execution boundaries	agents, executor, inspector, coordinator, authority scopes
A4 — Knowledge & Evidence	records, provenance, distillation, lineage	RAW, notes, evidence, distilled records, knowledge cells
A5 — Publication / Control Surface	human-facing observability and projection	Command Center, internal sites, public surfaces, deployments

Dependency direction

A0 Authority / Identity
        ↓
A1 Runtime Foundation
        ↓
A2 Network / Trust Boundary
        ↓
A3 Agent Architecture
        ↓
A4 Knowledge / Evidence
        ↓
A5 Publication / Control Surface

This is a dependency guide, not a claim that every system interaction is strictly linear. A higher layer may reveal missing facts in a lower layer, but unresolved lower-layer authority or runtime truth must remain visible rather than being silently inferred.

Minimum record for a mapped object

Every object that enters the Reality Map should eventually answer:

Field	Meaning
Identity	stable name or identifier
Axis	A0–A5
Location	where the object exists
Controller	who or what has authority
Connections	dependencies and relationships
Evidence	source proving the observed state
State	RAW, ACTIVE, BLOCKED, VERIFIED, DISTILLED, or ARCHIVED
Observed at	timestamp for the current observation
Confidence	how strongly the current state is supported

Unknown fields remain UNKNOWN or —.

Relationship to daily work

The Reality Map is not rewritten from every conversation or exploratory branch. Work first enters the daily distillation stream:

RAW WORK
   ↓
24h DISTILLATION
   ↓
PROPOSED MAP DELTA
   ↓
RECONCILED REALITY MAP

This keeps exploration chronological while allowing stable structure to emerge gradually.

Historical project streams

Project names such as Genesis-001 through Genesis-004 remain useful as historical and exploration streams. They should not be forced to become permanent architectural axes. A single historical project may map to multiple Reality Map axes.

Example:

Genesis-004 / OpenAI control work
    ├── A0 Authority & Identity
    ├── A3 Agent Architecture
    └── A5 Publication / Control Surface

Current reconciliation priorities

1. remove stale namespace/location claims from current-state surfaces;
2. map active nodes, accounts, agents, repositories, and services without inventing missing relationships;
3. preserve historical lineage separately from current truth;
4. let repeated 24h records reveal which relationships are stable enough to become canonical;
5. keep Zero protected while Alpha/Beta absorbs current development churn.