docs: accept repository classification boundary
Some checks failed
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / pytest-smoke (push) Failing after 2s

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a0230c-b06c-7641-808a-e191b6d1da49
This commit is contained in:
tegwick 2026-08-22 00:12:03 +02:00
parent f51a5819d5
commit 6288ba3d7d
6 changed files with 201 additions and 12 deletions

View file

@ -77,6 +77,13 @@ surface runs the immutable `055cf49` image while Core Hub remains deployed with
an empty writer set through the seven-day stabilization window ending no
earlier than 2026-08-28T20:49:50+02:00.
Repository classification remains authoritative in each repository and is
validated/projected by Repo Manager. Hub-core consumes that versioned
projection for cross-domain navigation under
`docs/adr/ADR-0002-repository-classification-projections.md`; it does not own a
mutable topic or classification write surface. Implementation and A5 handoff
are tracked in `HUB-WP-0006`.
## First Slice
- SQLAlchemy base metadata and timestamp helpers.