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

Database: reject divergent capture source rotation forks #89

Closed
nsaspy wants to merge 2 commits from rage-database/capture-rotation-fork-20260831 into master
pull from: rage-database/capture-rotation-fork-20260831
merge into: nsaspy:master
Conversation 0 Commits 2 Files changed 2 +47 -5
nsaspy commented 2026-09-04 20:37:06 +00:00
Owner
Copy link

Slice

Harden the canonical Tek9 execution-graph boundary so one operation/capture-session predecessor source cannot persist two different successor rotations.

Why

Capture rotation lineage is used for durable restart/replay. Accepting divergent successors for the same predecessor makes resume lineage ambiguous under concurrent or replayed writers.

RED

Commit 96a7c2d3fb58056a4969d8eb824619190213adf3 adds a regression proving exact replay is allowed but a divergent successor must raise persistence-replay-conflict.

GREEN implementation

Commit 340dde0d0d798ba65e5a68d52565111681fa228b validates lineage inside the canonical Tek9 write transaction before replay-safe node persistence. Scope is operation + capture session + predecessor source. Identical stable replay remains accepted.

Boundary

Database/execution-graph only. No parser actor, Hackpert expert logic, provider execution, shadow graph/KB, second database, or StarIntel product work.

## Slice Harden the canonical Tek9 execution-graph boundary so one operation/capture-session predecessor source cannot persist two different successor rotations. ## Why Capture rotation lineage is used for durable restart/replay. Accepting divergent successors for the same predecessor makes resume lineage ambiguous under concurrent or replayed writers. ## RED Commit `96a7c2d3fb58056a4969d8eb824619190213adf3` adds a regression proving exact replay is allowed but a divergent successor must raise `persistence-replay-conflict`. ## GREEN implementation Commit `340dde0d0d798ba65e5a68d52565111681fa228b` validates lineage inside the canonical Tek9 write transaction before replay-safe node persistence. Scope is operation + capture session + predecessor source. Identical stable replay remains accepted. ## Boundary Database/execution-graph only. No parser actor, Hackpert expert logic, provider execution, shadow graph/KB, second database, or StarIntel product work.
Database: reject divergent capture rotation forks
Some checks failed
agent-pr-serialization / one-open-pr-per-agent-lane (pull_request_target) Failing after 1s
Details
agent-framework-boundary / keep-agent-framework-out-of-product-tree (pull_request) Successful in 6s
Details
core / common-lisp-core (pull_request) Failing after 40s
Details
monorepo / hygiene (pull_request) Successful in 5m57s
Details
340dde0d0d
nsaspy closed this pull request 2026-09-04 20:54:40 +00:00
Some checks failed
agent-pr-serialization / one-open-pr-per-agent-lane (pull_request_target) Failing after 1s
Details
agent-framework-boundary / keep-agent-framework-out-of-product-tree (pull_request) Successful in 6s
Details
core / common-lisp-core (pull_request) Failing after 40s
Details
monorepo / hygiene (pull_request) Successful in 5m57s
Details

Pull request closed

Please reopen this pull request to perform a merge.
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!89
No description provided.