Skip to content

Add branching workspace snapshots, evaluation and selection - #860

Draft
flip-engineer wants to merge 7 commits into
mainfrom
codex/branching-snapshots-flush-20261018
Draft

flip-engineer wants to merge 7 commits into
mainfrom
codex/branching-snapshots-flush-20261018

Conversation

@flip-engineer

@flip-engineer flip-engineer commented Oct 18, 2026 •

Copy link
Copy Markdown
Collaborator

The branching API captures a workspace snapshot with a private Git index, creates separate worktrees and fresh native conversations, runs explicit evaluation commands, and records the selected branch. Continuation dispatches guidance to the selected Player's existing conversation and workspace. A subsequent branch start creates fresh conversations from that selected workspace and its recorded inputs.

The implementation retains branch artifacts, reports, input and evaluator evidence. The focused fixture includes the production Instance.owner and Instance.shutdown bindings and argv routes through process-spawn.c.

Validation at candidate 0a57c95: the branch includes main 2cf17ad, and Git tree comparison confirmed preservation of every PR-owned blob. Current main has advanced. The candidate still requires current-main integration, a focused compiler check, and a complete runtime pass on the self-hosted homelab runner. No current-head runtime result or deployment is recorded. #865 tracks focused qualification.

Refs #751, #772, #776, #811.

flip-engineer and others added 4 commits October 18, 2026 03:09
Port the Branching Ensemble modules from pr/772 onto current main and add
the minimal action, route and command wiring. branching-focused.bend drives
the production modules over a temporary coordination database and real Git
worktrees: snapshot isolation, forked candidate isolation, lineage, best
evaluation selection and candidate flush.
@flip-engineer

Copy link
Copy Markdown
Collaborator Author

Root review added the fixture owner and shutdown argv routes using the exact production Instance.owner / Instance.shutdown foreign identifiers and process-spawn.c bindings. This avoids importing the entire instance module. The original c185 fixture passed source checking and reached 15+ runtime assertions, then waited on its missing owner route. The new head 97f396a requires source checking and a complete runtime pass on the homelab. It is not qualified for merge yet. The earlier slim adapter using Fixture.* is superseded; its retained patch remains preserved.

@flip-engineer
flip-engineer marked this pull request as draft October 18, 2026 12:08
@flip-engineer flip-engineer changed the title Add branching snapshots, evaluation, selection and flush Add branching workspace snapshots, evaluation and selection Oct 19, 2026

@flip-engineer flip-engineer left a comment

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Returned to development by the root conductor. This head retains the production Instance.owner and Instance.shutdown fixture routes, but has no complete current-head runtime result. Reconcile with current main, compile and execute the focused branching fixture on the homelab, and return the exact candidate and result for root review. Preserve branch lineage, native conversation identity and evaluator evidence. This task remains open.

Review disposition recorded 2026-10-19. Completed and validated work proceeds through root review, merge and deployment; remaining work stays assigned for development or escalation.

Integrate the published PR860 head 0a57c95 with current main
c021089. The merge is conflict-free; the main-side tree retains the
current-main build and recovery changes, and the PR860 delta remains the
nine branching source, test and documentation files. Original PR860
commits and authorship remain in ancestry.
Bring PR #860 current with main a5d7ada. The merge is conflict-free.
The main-side changes are retained and the PR860 branching source,
tests and documentation remain authored by the original commits.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant