Merge pull request #26 from tigrbl/bbdx/initialize-and-sync-ssot-with-local-adrs/2026-04-15

Add canonical .ssot registry, ADRs, schemas, and specs

Author: cobycloud

.ssot/adr/ADR-0001-canonical-json-registry.md

@@ -0,0 +1,11 @@
+# ADR-0001: Canonical registry is a single JSON document
+
+## Status
+Accepted
+
+## Decision
+The only authored machine-readable source of truth is `.ssot/registry.json`.
+
+## Consequences
+- Split manifests, spreadsheets, and parallel mapping files are non-canonical.
+- Reports, graphs, CSV projections, Markdown summaries, and SQLite mirrors are generated.

.ssot/adr/ADR-0002-features-are-targetable-units.md

@@ -0,0 +1,11 @@
+# ADR-0002: Features are the targetable units
+
+## Status
+Accepted
+
+## Decision
+Features are the only targetable implementation units. There is no separate `targets[]` section.
+
+## Consequences
+- Planning horizon and target claim tier live on feature rows.
+- Scope is defined by selected feature IDs inside boundaries.

.ssot/adr/ADR-0003-issues-are-plannable-work-items.md

@@ -0,0 +1,11 @@
+# ADR-0003: Issues are plannable work items
+
+## Status
+Accepted
+
+## Decision
+Issues and tickets can be planned as current, next, future, explicit, backlog, or out-of-bounds, but they are not substitute targets for features.
+
+## Consequences
+- Delivery scope and remediation scope remain distinct.
+- Issues may still block certification and release.

.ssot/adr/ADR-0004-entity-centric-registry-derived-graph.md

@@ -0,0 +1,11 @@
+# ADR-0004: Entity-centric registry with a derived graph export
+
+## Status
+Accepted
+
+## Decision
+The canonical registry is entity-centric JSON with explicit references. A graph export is derived from it.
+
+## Consequences
+- Authoring stays practical in Git.
+- Programmatic graph traversal remains available.

.ssot/adr/ADR-0005-normalized-prefixed-ids.md

@@ -0,0 +1,11 @@
+# ADR-0005: Normalized prefixed IDs
+
+## Status
+Accepted
+
+## Decision
+Every first-class entity uses a normalized prefixed ID.
+
+## Consequences
+- Stable references across repositories and generated artifacts.
+- Easy namespace validation and filesystem-safe projection.

.ssot/adr/ADR-0006-claim-status-vs-tier.md

@@ -0,0 +1,11 @@
+# ADR-0006: Claim status and claim tier are orthogonal
+
+## Status
+Accepted
+
+## Decision
+Claim status expresses lifecycle progression. Claim tier expresses assurance strength.
+
+## Consequences
+- Workflow and assurance are not conflated.
+- Tiers remain stable while statuses advance.

.ssot/adr/ADR-0007-feature-implementation-vs-lifecycle.md

@@ -0,0 +1,11 @@
+# ADR-0007: Feature implementation state is separate from lifecycle state
+
+## Status
+Accepted
+
+## Decision
+`implementation_status` and `lifecycle.stage` are distinct fields.
+
+## Consequences
+- Deprecation, obsolescence, and removal are modeled cleanly.
+- Implementation readiness is not overloaded with support-state semantics.

.ssot/adr/ADR-0008-immutable-boundary-and-release-snapshots.md

@@ -0,0 +1,11 @@
+# ADR-0008: Immutable boundary and release snapshots
+
+## Status
+Accepted
+
+## Decision
+Frozen boundaries and promoted/published releases emit immutable snapshots with hashes.
+
+## Consequences
+- Auditable, reproducible release state.
+- Clear separation between authored truth and frozen evidence.

.ssot/adr/ADR-0009-fail-closed-guards.md

@@ -0,0 +1,11 @@
+# ADR-0009: Fail-closed guards
+
+## Status
+Accepted
+
+## Decision
+Validation, certification, promotion, publication, and lifecycle transitions refuse to proceed on guard violations.
+
+## Consequences
+- No silent drift.
+- No optimistic release progression.

.ssot/adr/ADR-0010-generated-projections-are-non-canonical.md

@@ -0,0 +1,11 @@
+# ADR-0010: Generated projections are non-canonical
+
+## Status
+Accepted
+
+## Decision
+DOT, JSON graph exports, CSV files, Markdown summaries, and SQLite mirrors are generated views.
+
+## Consequences
+- Canonical authorship remains singular.
+- Regeneration is deterministic.