Database: require canonical long-term source for global KB export #86

Closed

nsaspy wants to merge 4 commits from auto-rage-database/global-export-canonical-source-20260831 into master

nsaspy commented

2026-09-04 20:37:05 +00:00

Owner

Slice

Issue #24 database/KB lifecycle: global-KB export must prove its source long-term promotion is the exact canonical Tek9 promotion, not merely a caller-constructed in-memory object.

TDD

RED head: ff8d6438caf87f112dd489fcd1ef18879a13929d

core: RED exactly on non-canonical long-term promotion unexpectedly exported
monorepo: GREEN
agent-framework-boundary: GREEN

Implementation head: 1d9604d8b1ef316c53a95ea8850174f2d5d33817

core: GREEN
monorepo: GREEN
agent-framework-boundary: GREEN

Typed persistence decision

persist-global-kb-export resolves the referenced long-term promotion from the canonical long-term Tek9 graph and compares the exact exported claim/provenance fields before writing global state. Validation and global persistence execute under the same Tek9 write transaction.

The long-term promotion is the export authority; global export does not collapse the lifecycle by re-evaluating later operation-local retractions.

Boundary

database/KB persistence only
no Hackpert/provider/expert behavior
no shadow KB or second database
canonical Hackmode/Tek9 remains persistence authority
no StarIntel product work

Replacement for #110 because the draft→ready API mutation was unavailable; exact tested head is unchanged.

## Slice Issue #24 database/KB lifecycle: global-KB export must prove its source long-term promotion is the exact canonical Tek9 promotion, not merely a caller-constructed in-memory object. ## TDD RED head: `ff8d6438caf87f112dd489fcd1ef18879a13929d` - core: RED exactly on `non-canonical long-term promotion unexpectedly exported` - monorepo: GREEN - agent-framework-boundary: GREEN Implementation head: `1d9604d8b1ef316c53a95ea8850174f2d5d33817` - core: GREEN - monorepo: GREEN - agent-framework-boundary: GREEN ## Typed persistence decision `persist-global-kb-export` resolves the referenced long-term promotion from the canonical long-term Tek9 graph and compares the exact exported claim/provenance fields before writing global state. Validation and global persistence execute under the same Tek9 write transaction. The long-term promotion is the export authority; global export does not collapse the lifecycle by re-evaluating later operation-local retractions. ## Boundary - database/KB persistence only - no Hackpert/provider/expert behavior - no shadow KB or second database - canonical Hackmode/Tek9 remains persistence authority - no StarIntel product work Replacement for #110 because the draft→ready API mutation was unavailable; exact tested head is unchanged.

nsaspy added 4 commits

2026-09-04 20:37:05 +00:00