nsaspy/hackmode
1
0
Fork 0
Code Issues 46 Pull requests 55 Projects Releases Packages Wiki Activity Actions

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

Open
nsaspy wants to merge 4 commits from auto-rage-database/global-export-canonical-source-20260831 into master
pull from: auto-rage-database/global-export-canonical-source-20260831
merge into: nsaspy:master
Conversation 0 Commits 4 Files changed 4 +132 -21
nsaspy commented 2026-09-04 20:58:42 +00:00
Owner
Copy link

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 now 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.

This intentionally validates the long-term promotion as the export authority rather than re-evaluating later operational-KB retractions: promotion is the explicit immutable lifecycle boundary between operation-local and reusable knowledge.

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

No reviews, comments, or unresolved review threads at exact-head gate completion.

## 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` now 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. This intentionally validates the long-term promotion as the export authority rather than re-evaluating later operational-KB retractions: promotion is the explicit immutable lifecycle boundary between operation-local and reusable knowledge. ## 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 No reviews, comments, or unresolved review threads at exact-head gate completion.
Tests: persist canonical promotion before global export
Some checks failed
agent-pr-serialization / one-open-pr-per-agent-lane (pull_request_target) Failing after 2s
Details
agent-framework-boundary / keep-agent-framework-out-of-product-tree (pull_request) Successful in 5s
Details
core / common-lisp-core (pull_request) Failing after 39s
Details
monorepo / hygiene (pull_request) Successful in 3m22s
Details
1d9604d8b1
Some checks failed
agent-pr-serialization / one-open-pr-per-agent-lane (pull_request_target) Failing after 2s
Details
agent-framework-boundary / keep-agent-framework-out-of-product-tree (pull_request) Successful in 5s
Details
core / common-lisp-core (pull_request) Failing after 39s
Details
monorepo / hygiene (pull_request) Successful in 3m22s
Details
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin auto-rage-database/global-export-canonical-source-20260831:auto-rage-database/global-export-canonical-source-20260831
git switch auto-rage-database/global-export-canonical-source-20260831

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch master
git merge --no-ff auto-rage-database/global-export-canonical-source-20260831
git switch auto-rage-database/global-export-canonical-source-20260831
git rebase master
git switch master
git merge --ff-only auto-rage-database/global-export-canonical-source-20260831
git switch auto-rage-database/global-export-canonical-source-20260831
git rebase master
git switch master
git merge --no-ff auto-rage-database/global-export-canonical-source-20260831
git switch master
git merge --squash auto-rage-database/global-export-canonical-source-20260831
git switch master
git merge --ff-only auto-rage-database/global-export-canonical-source-20260831
git switch master
git merge auto-rage-database/global-export-canonical-source-20260831
git push origin master
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
bug
Something isn't working

  
documentation
Improvements or additions to documentation

  
duplicate
This issue or pull request already exists

  
enhancement
New feature or request

  
feature
New feature or capability

  
good first issue
Good for newcomers

  
help wanted
Extra attention is needed

  
invalid
This doesn't seem right

  
question
Further information is requested

  
refactor
Code cleanup without behavior change

  
wontfix
This will not be worked on

No labels
bug
documentation
duplicate
enhancement
feature
good first issue
help wanted
invalid
question
refactor
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nsaspy/hackmode!156
No description provided.