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

Database: persist capture source rotation lineage #94

Closed
nsaspy wants to merge 1 commit from hackmode-rage-database/capture-source-rotation-20260830 into master
pull from: hackmode-rage-database/capture-source-rotation-20260830
merge into: nsaspy:master
Conversation 0 Commits 1 Files changed 5 +187 -4
nsaspy commented 2026-09-04 20:37:08 +00:00
Owner
Copy link

Slice

Issue #26 database-owned persistence slice: preserve capture-source rotation lineage inside the existing operation-scoped execution graph.

RED contract

The regression requires a typed immutable rotation record carrying capture session, predecessor/successor source identity, predecessor final durable offset, framing version, and provenance. Identical replay must keep stable identity, self-rotation must fail closed, reads must stay operation/capture scoped, and returned lineage must be durable-offset ordered.

This PR is intentionally opened with the regression wired before implementation so exact-head CI can prove RED first.

Boundary

No parser/proxy implementation, Hackpert behavior, provider execution, StarIntel product work, shadow graph, second KB, or second database.

## Slice Issue #26 database-owned persistence slice: preserve capture-source rotation lineage inside the existing operation-scoped execution graph. ## RED contract The regression requires a typed immutable rotation record carrying capture session, predecessor/successor source identity, predecessor final durable offset, framing version, and provenance. Identical replay must keep stable identity, self-rotation must fail closed, reads must stay operation/capture scoped, and returned lineage must be durable-offset ordered. This PR is intentionally opened with the regression wired before implementation so exact-head CI can prove RED first. ## Boundary No parser/proxy implementation, Hackpert behavior, provider execution, StarIntel product work, shadow graph, second KB, or second database.
Database: reconcile capture source rotation onto current master
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 4s
Details
core / common-lisp-core (pull_request) Failing after 45s
Details
monorepo / hygiene (pull_request) Successful in 3m50s
Details
cacb89eb2f
nsaspy closed this pull request 2026-09-04 20:54:11 +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 4s
Details
core / common-lisp-core (pull_request) Failing after 45s
Details
monorepo / hygiene (pull_request) Successful in 3m50s
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!94
No description provided.