README.md

Echo Docs

Echo's documentation describes a deterministic WARP runtime over witnessed causal history. Git history is the archive; GitHub owns live work and status.

Start Here

• Documentation standards
• Architecture outline
• Application contract hosting
• Local contract host quickstart
• Echo 1.0 release contract
• WARP core runtime
• Scheduler WARP core

Current Architecture

• There Is No Graph
• Continuum transport
• Echo optics adapter notes
• Echo × Keep physical content boundary

Case Studies

• Jim and Echo

Living Topics

• Topic map
• Runtime authority
• Generated rules
• WARP optics
• Strands and braids
• Obstructions
• Causal anchors
• Contract inverse admission
• External actions
• WAL
• Runtime constellation
• Security posture and threat models

Decision History

Current decisions are reached through the semantic architecture, topic, and contract sections above and below. This section routes to the retained numbered archive; it is not an allocation queue or a substitute for explicit relationships.

• Legacy numbered decision archive
• Superseded repository knowledge model
• Echo/Continuum authority boundary
• Generated rule authorship and footprints
• Registry, provider, and host boundary
• Continuum transport identity
• Universal little-endian codec
• Session causal posture and authority
• Bunny owns reusable geometry
• Retained reading storage and proof boundary
• Public optic and observation boundary
• Application-requested causal-anchor admission
• Admitted executable-operation packages
• Anchored-node creation from absence
• Scheduler-owned executable-operation Actions
• Durable external-action settlement

Normative Contracts

• WASM ABI
• JS-to-CBOR mapping
• ABI golden vectors
• Two-plane law
• Strand contract
• Fixed timestep
• Declarative rule authorship

Determinism Evidence

• Deterministic math policy
• Deterministic math hazards
• DIND harness
• Scheduler performance

Knowledge Ownership

Current architecture belongs in architecture documents, specifications, invariants, and living topics. Durable decisions update the named document that owns their concept and state relationships explicitly. Numbered ADRs are a closed historical archive, not the current decision queue. Externally meaningful shipped behavior belongs in CHANGELOG.md. Live design, priority, dependencies, review state, and follow-up work belong in GitHub Issues, Projects, pull requests, and review threads. The documentation standards define the complete contract.