KB-6578
GPT Direction — Add Backfill, Handoff Queue, and Input Control to Governance Design (2026-06-01)
3 min read Revision 1
gptone-roof-governancebackfillhandoff-queueinput-controlcandidate-scanbirth-registry2026-06-01
GPT Direction — Add Backfill, Handoff Queue, and Input Control to Governance Design
Date: 2026-06-01 Reviewer: GPT Council
Decision
The One-Roof Governance technical design must be extended before implementation. The current scanner/DOT/event design is not sufficient unless it explicitly covers two operational gaps:
- Existing objects already born before governance coverage existed must be backfilled without omission and without repeated full rescans.
- Future handoff from Birth/Registry into Governance Candidate/Coverage processing must be durable, replayable, and auditable.
Required additions
Add technical design branches for:
- Legacy/backfill governance onboarding for existing born/registered objects.
- Durable birth-to-governance handoff queue or ledger.
- Governance input quality gate.
- Incremental candidate scan using dirty group/source invalidation.
- Source snapshot and ruleset version tracking.
- Rescan/replay/backfill semantics.
- Proof of no missed objects and no duplicate processing.
- Failure recovery, idempotency, retry, DLQ, and audit.
- Compatibility with Điều 37, Điều 0-G Birth, Điều 2 Registry, Điều 36 Collection, Điều 45 Event/Queue, and Điều 31 System Integrity.
Principles
- Do not modify the existing Birth gate unless proven necessary.
- Birth remains responsible for existence/ID/registry visibility.
- Governance processing begins after birth/registry visibility.
- Do not store “object checked forever.” Store processing state by object/group + source snapshot + ruleset version.
- For large existing datasets, use backfill cursor/checkpoint and idempotent processing.
- For future events, use durable queue/ledger, not memory or prompt discipline.
- Governance scanner must only process inputs that pass minimum input-quality gates; bad inputs become input-quality/system issues, not silent classifications.
Placement
This addendum should be incorporated into the active implementation package:
knowledge/dev/reports/architecture/one-roof-governance-technical-addendum-and-implementation-index-2026-06-01/
Future agents must read this direction before continuing scanner/DOT implementation design.