Lifecycle hook events

Hooks are ordered host-event adapters. They improve capture and continuity but do not own business logic, HIL, completion, or pointer movement.

Current counts are derived release facts, not permanent ceilings.

The current registry contains 11 event classes and 44 ordered handlers. Explicit skills and native actions remain available when hooks are disabled for repair. An event runs only when the host emits it, and a failing event can be isolated without granting unrelated hooks authority.

Source-bound workflow map

This page is projected from the same current executable snapshot as the rest of the documentation set. The map is deliberately two-directional: each horizontal district shows peer stages while vertical edges show ownership and state progression.

flowchart TB
    subgraph InputDistrict["Input and classification"]
      direction LR
      A["Native Codex host event"] --> B["Event and timing classification"] --> C["One of 11 hook classes"]
    end
    subgraph ExecutionDistrict["Selection and execution"]
      direction TB
      D["Four ordered handlers"] --> E["Validate, emit, transport, and seal"] --> F["Trust and invocation proof"]
    end
    subgraph EvidenceDistrict["Evidence and outcome"]
      direction LR
      G["Hook receipt"] --> H["Bounded lifecycle strengthening"]
      G -. mismatch .-> I["Disable only the failing untrusted event"]
    end
    C --> D
    F --> G

Contract and readback

Canonical source owners

• hooks/hook-event-registry.v1.json
• hooks/hooks.json
• schemas/hooks/hook-runtime.v1.json

Exact backend readback

Cross-surface invariants

• The current snapshot contains 91 public actions, 26 skills, 11 hook events / 44 handlers, 119 tool requirements, 18 sector lanes, and 11 named authorities. These are derived counts, not fixed ceilings.
• Executable ownership stays one-way: skills select, MCP exposes, the outer SDK routes, the internal SDK executes, ENV selects, UOP governs, tools perform bounded work, hooks emit receipts, and the owning authority validates effects.
• Any missing identity, schema, grant, capability, dependency, receipt, or authority proof must fail closed at its owning phase; a later green check cannot retroactively authorize the skipped boundary.
• A changed route refreshes every dependent schema, manifest, generator, test, diagram, and documentation reference; the superseded executable route is directly purged in the same Delta.
• Tests, Git, CI, installation, restart, deployment, discussion, or a rendered page never imply Project HIL, Learning HIL, Goal completion, or pointer movement.

This page is a Git-tracked documentation projection. Executable source, SQLite authorities, installed-runtime receipts, and explicit human gates remain the governing evidence.