Skip to main content

Feature Map

This repository is a docs-as-infrastructure system, not a folder of pages. The intended operating model is ownerless: every governed surface declares its canonical source, validator, repair path, and primary gate so a contributor or agent can diagnose and repair drift without private maintainer context. Use this page as the high-level system map. Use the linked feature pages for implementation details and the Gap Analysis for purge, migration, and remediation work.

Core philosophy


Feature index


System map


Three locked-decision registries

The repo carries 32 locked structural decisions across three ID-prefixed registries. All cross-referenced from the unified index at docs-guide/decisions/registry.md.

Current inventory snapshot (live, 2026-05-23)


Contributor operating loop

  1. Read the relevant governance entry point before editing: policies/governance-index.mdx or docs-guide/index.mdx.
  2. Identify the canonical source for the surface being changed (every surface declares it in operations/governance/config/*.json or its policy doc).
  3. Change the source, generator, validator, or policy that owns the behaviour – never the derived output.
  4. Regenerate derived outputs with the named generator command – never hand-edit.
  5. Run the smallest relevant validator – usually lpd test --staged.
  6. If a failure appears, fix the owning source or repair command. Bypasses are governance debt.
  7. For route or nav work, treat docs.json as production infrastructure. Validate route impact via check-docs-path-sync.js + redirect-integrity hook.

What good looks like

Every major feature should satisfy this contract: Per the 2026-05-25 audit, 4 of 5 unified surfaces fully satisfy this contract in the canonical registry repo-governance-surfaces.json (bridge_mode "retired", legacy bridge inventory empty post-D-ACT-10). The remaining surface (github-workspace-governance) is at advisory state. The legacy 8-entry ownerless-governance-surfaces.json is superseded but kept for reference. The Gap Analysis is the queue for promoting the remaining advisory surface to autofix or blocking.

Feature deep dives

  • AI Features – public AI surfaces + agent runtime + skill system + adapters
  • UI System – component library + templates + composables + design tokens + snippets
  • Automations – 4-tier composable architecture + 11 workflows + 321 scripts + hook pipeline
  • Data Integrations – 11 integration families incl. contracts (gold-standard) + OpenAPI
  • Adaptive Architecture – ownerless contract + 5-stage control loop + remediator families
  • Contributor Toolslpd CLI + scoped preview + VS Code extensions + hooks

Framework deep dives

Policy deep dives

Standards

Cross-cutting

  • Gap Analysis – implementation-ready backlog with P0/P1/P2 priorities (refreshed 2026-05-23)
  • Decisions Registry – unified index of all locked decisions (32 total across 3 ID prefixes)
  • docs-guide/index.mdx – docs-guide overview (the front door)
  • workspace/plan/active/_MY_PROCESS/ – page-authoring + checks process canonical source
  • workspace/thread-outputs/repo-consolidation-deep/ – 10 file-level slice audits + master consolidation map (~4,400 lines of evidence)
Last modified on June 2, 2026