Release and compatibility

The current source line is Evidence Lane 3.0.0. Source identity, local package identity, installed-host identity, Git commit/tree, runtime, candidate, accepted PV, website, and human release decision are separate facts.

Current counts are derived release facts, not permanent ceilings.

Historical commits, packages, receipts, and accepted PVs retain their original identities as non-executable provenance. They cannot override the current registry or revive a purged compatibility route.

A branch checkpoint, passing test, preview, or package is release evidence only. Main merge, main-slot installation, slot normalization, production website publication, Project HIL, Learning HIL, Fuse, and Goal completion remain separate operations.

Downstream projects keep their own Git, CI, deployment, storage, schema, lane, and connector choices. They do not inherit the Evidence Lane plugin-maintainer release cycle.

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["Reviewed source and release intent"] --> B["Version and compatibility classification"] --> C["Exact package and Git identity"]
    end
    subgraph ExecutionDistrict["Selection and execution"]
      direction TB
      D["Branch CI and installed proof"] --> E["Main-slot release candidate"] --> F["Release authority validation"]
    end
    subgraph EvidenceDistrict["Evidence and outcome"]
      direction LR
      G["Release receipts"] --> H["Explicit promotion and readback"]
      G -. mismatch .-> I["Historical receipts stay non-executable"]
    end
    C --> D
    F --> G

Contract and readback

Canonical source owners

• .codex-plugin/plugin.json
• scripts/codex-release-channel.json
• scripts/codex_release/accept_codex_stable.py

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.