28 lines
1.3 KiB
Markdown
28 lines
1.3 KiB
Markdown
# Governance lineage decision — 2026-08-22
|
|
|
|
Status: accepted as part of DEV-000099.
|
|
|
|
## DEV-000073 resolution
|
|
|
|
The repository history contains more than one DEV-000073 packet variant: a
|
|
production-deployment packet and an earlier durable-bootstrap work-in-progress.
|
|
Neither is the current active task, and the current main lineage does not
|
|
contain one uniquely authoritative DEV-000073 packet. References such as
|
|
`DEV-000073-baseline` in later historical packets are retained as evidence of
|
|
their implementation baseline, not treated as an accepted current architecture
|
|
revision or active work pointer.
|
|
|
|
The accepted architecture authority for the current project is the accepted
|
|
ADR chain, currently ADR-0017 and ADR-0018. A future task that needs the
|
|
DEV-000073 deployment lineage must name an exact packet/revision and establish
|
|
its ancestry before activation. No historical checkpoint is rewritten.
|
|
|
|
## Current governance authority
|
|
|
|
`dev/ACTIVE_TASK.json` selects exactly one current packet. The packet declares
|
|
its own path and the active pointer in scope. `architecture-registry.yaml` is
|
|
the human-maintained registry mirror; `architecture-registry.json` is the
|
|
machine-readable equivalent consumed by `devctl`; `architecture-registry.md`
|
|
is the cold-agent-readable projection. Their semantic content is synchronized
|
|
for the current ownership/topology baseline.
|