This document serves as the cross-reference index for all Igor specification documents. It maps every document to its specification layer, describes its purpose, and lists cross-references to related documents.
Constitutional documents define WHAT Igor must guarantee — non-negotiable execution invariants that hold regardless of implementation.
| Document | Description | Category | Cross-References |
|---|---|---|---|
| RUNTIME_CONSTITUTION.md | Constitutional specification root. Declares non-negotiable guarantees and the foundational separation between checkpoint lineage and ownership authority. | Root | EXECUTION_INVARIANTS, OWNERSHIP_AND_AUTHORITY, MIGRATION_CONTINUITY, SPEC_GOVERNANCE |
| EXECUTION_INVARIANTS.md | Foundational runtime invariants (EI-1 through EI-11): single active instance, checkpoint lineage integrity, authority separation, safety over liveness, migration preservation. | Identity, Continuity, Authority, Safety, Migration | RUNTIME_CONSTITUTION, OWNERSHIP_AND_AUTHORITY, RUNTIME_ENFORCEMENT_INVARIANTS |
| OWNERSHIP_AND_AUTHORITY.md | Authority lifecycle model (OA-1 through OA-7): canonical identity, lifecycle states (ACTIVE_OWNER, HANDOFF_INITIATED, HANDOFF_PENDING, RETIRED, RECOVERY_REQUIRED), transfer rules, conflict resolution. | Identity, Authority | EXECUTION_INVARIANTS, RUNTIME_CONSTITUTION |
| MIGRATION_CONTINUITY.md | Migration continuity contracts (MC-1 through MC-9, FS-1 through FS-4): migration as continuity transfer, safe migration guarantees, overlap constraints, lineage fork detection, failure safety matrix. | Migration, Safety | EXECUTION_INVARIANTS, OWNERSHIP_AND_AUTHORITY, RUNTIME_CONSTITUTION |
| AUTHORITY_STATE_MACHINE.md | Formal authority lifecycle state machine: state definitions, normative transition table, forbidden transitions, tick permission matrix. Operationalizes single-active-ticker guarantee. | Authority, Lifecycle | EXECUTION_INVARIANTS, OWNERSHIP_AND_AUTHORITY, MIGRATION_CONTINUITY, RUNTIME_CONSTITUTION |
| CAPABILITY_MEMBRANE.md | Capability membrane invariants (CM-1 through CM-7): total mediation, explicit declaration, deny by default, observation determinism, side effect attribution, capability immutability during tick, capability survival through migration. | Boundary, Integrity, Authority, Migration | EXECUTION_INVARIANTS, AUTHORITY_STATE_MACHINE, MIGRATION_CONTINUITY, RUNTIME_CONSTITUTION |
Enforcement documents define HOW constitutional guarantees are upheld through runtime enforcement rules and invariant derivation mappings. Every enforcement invariant derives from one or more constitutional invariants.
| Document | Description | Cross-References |
|---|---|---|
| RUNTIME_ENFORCEMENT_INVARIANTS.md | Enforcement rules (RE-1 through RE-8): checkpoint atomicity, state persistence, budget conservation and monotonicity, tick duration and determinism, storage isolation, lifecycle ordering. | RUNTIME_CONSTITUTION, EXECUTION_INVARIANTS, OWNERSHIP_AND_AUTHORITY, MIGRATION_CONTINUITY |
| INVARIANT_DEPENDENCY_GRAPH.md | Maps dependency relationships between constitutional and enforcement invariants. Traces the derivation chain from single-ticker law through authority lifecycle, ownership sidecar, migration ordering, and recovery fencing. | EXECUTION_INVARIANTS, OWNERSHIP_AND_AUTHORITY, MIGRATION_CONTINUITY, RUNTIME_ENFORCEMENT_INVARIANTS |
| CAPABILITY_ENFORCEMENT.md | Capability enforcement rules (CE-1 through CE-6): hostcall namespace isolation, manifest validation, tick observation log, authority-gated side effects, pre-migration capability verification, hostcall cost accounting. | CAPABILITY_MEMBRANE, RUNTIME_ENFORCEMENT_INVARIANTS |
Runtime documents describe HOW Igor operates — implementation details, protocol mechanics, and operational flows.
| Document | Description | Cross-References |
|---|---|---|
| ARCHITECTURE.md | System structure, component overview, and implementation details. | RUNTIME_ENFORCEMENT_INVARIANTS, EXECUTION_INVARIANTS |
| AGENT_LIFECYCLE.md | Agent development guide: lifecycle functions, building and deploying agents. | RUNTIME_ENFORCEMENT_INVARIANTS, EXECUTION_INVARIANTS |
| MIGRATION_PROTOCOL.md | P2P migration protocol mechanics and message flows. | MIGRATION_CONTINUITY |
| BUDGET_MODEL.md | Economic model, execution metering, and budget enforcement. | RUNTIME_ENFORCEMENT_INVARIANTS |
| THREAT_MODEL.md | Canonical runtime threat assumptions: system/failure model, adversary classes, network assumptions, and trust boundaries. | SECURITY_MODEL, EXECUTION_INVARIANTS, MIGRATION_CONTINUITY |
| SECURITY_MODEL.md | Current security mechanisms and explicit limitations under the threat assumptions. | THREAT_MODEL |
| HOSTCALL_ABI.md | Hostcall interface design: WASM module namespace, capability namespaces (clock, rand, log, wallet, x402, http, kv), function signatures, error conventions, manifest format, wazero integration. | CAPABILITY_MEMBRANE, CAPABILITY_ENFORCEMENT, ARCHITECTURE |
| EFFECT_LIFECYCLE.md | Effect lifecycle model: crash-safe external action tracking, intent state machine (Recorded→InFlight→Confirmed/Unresolved→Compensated), resume rule, SDK API, checkpoint serialization. | CAPABILITY_MEMBRANE, HOSTCALL_ABI, ARCHITECTURE |
| REPLAY_ENGINE.md | Replay engine design (draft): event log structure, replay verification flow, divergence handling, replay modes. | CAPABILITY_MEMBRANE, CAPABILITY_ENFORCEMENT, EXECUTION_INVARIANTS |
| LEASE_EPOCH.md | Lease-based authority epochs design (draft): time-bounded authority, epoch advancement, anti-clone enforcement, renewal protocol. | AUTHORITY_STATE_MACHINE, OWNERSHIP_AND_AUTHORITY, THREAT_MODEL |
| SIGNED_LINEAGE.md | Signed checkpoint lineage: Ed25519 agent identity, checkpoint format v0x04, signing protocol, hash chain, content addressing, migration. | EXECUTION_INVARIANTS, OWNERSHIP_AND_AUTHORITY, MIGRATION_CONTINUITY |
Governance documents define HOW Igor evolves — processes, workflows, and change control.
| Document | Description |
|---|---|
| SPEC_GOVERNANCE.md | Specification change control, layer classification, and constitutional freeze rules. |
| DOCUMENTATION_SCOPE.md | Documentation boundaries and layer definitions. |
| DEVELOPMENT.md | Developer setup and workflow. |
| CI_PIPELINE.md | Continuous integration documentation. |
| RELEASE_PROCESS.md | Release management procedures. |
| TOOLCHAIN.md | Build toolchain and version requirements. |
| ROADMAP.md | Future development phases. |
| KEYWORDS.md | Keyword governance policy. |
Philosophy documents explain WHY Igor exists — motivation and conceptual framing.
| Document | Description |
|---|---|
| VISION.md | Why autonomous software needs survival. |
| OVERVIEW.md | Introduction to Igor concepts and current status. |
| Layer | Purpose | Scope |
|---|---|---|
| Constitution | WHAT Igor guarantees | Non-negotiable invariants. Mechanism-agnostic, field-agnostic, implementation-agnostic. |
| Enforcement | HOW guarantees are upheld | Enforcement rules derived from constitutional invariants. May reference runtime concepts. |
| Runtime | HOW Igor operates | Implementation details, protocols, algorithms, operational flows. Must comply with all higher layers. |
| Governance | HOW Igor evolves | Change control, development process, release management. |
| Philosophy | WHY Igor exists | Motivation, worldview, conceptual framing. |
Each layer derives authority from the layer above. No lower layer may introduce or weaken guarantees defined at a higher layer.