Repository map

The repository separates the installable plugin, public documentation application, GitHub Markdown, Pages assets, tests, and repository-level generators.

Current counts are derived release facts, not permanent ceilings.

Local virtual environments, caches, runtimes, rehearsal evidence, RAG indexes, temporary support lanes, and secrets are excluded from release staging.

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["Repository member"] --> B["Executable, generated, docs, test, or local classification"] --> C["Canonical owner directory"]
    end
    subgraph ExecutionDistrict["Selection and execution"]
      direction TB
      D["Manifest and source-impact graph"] --> E["Package or Git allowlist"] --> F["Hash and path-policy validation"]
    end
    subgraph EvidenceDistrict["Evidence and outcome"]
      direction LR
      G["Membership receipt"] --> H["Included release member or excluded local byte"]
      G -. mismatch .-> I["Purge stale duplicate ownership"]
    end
    C --> D
    F --> G

Contract and readback

Canonical source owners

• manifests/executable-surface-registry.v1.json
• src/evidence_lane_plugin/source_fingerprint.py
• scripts/audit_repository_semantic_currentness.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.