docs(grid): L0 E2E persona cognition plan — careful sequencing per Joel#1463
Closed
joelteply wants to merge 1 commit into
Closed
docs(grid): L0 E2E persona cognition plan — careful sequencing per Joel#1463joelteply wants to merge 1 commit into
joelteply wants to merge 1 commit into
Conversation
…cognition path Joel 2026-05-29: 'would take careful planning to migrate. I would get e2e persona cognition first, within RUST alone.' Plan covers: - What 'e2e persona cognition in Rust alone' means concretely (the cognition decisions + state stay Rust; ingress/egress can stay transitional TS) - Audit of what already runs in Rust (PersonaCognition, PersonaCognitionEngine, full_evaluate, respond, service_cycle, PersonaServiceModule L0-1 minimum) - Audit of what still runs in TS (PersonaAutonomousLoop driving the loop today, PersonaMessageEvaluator orchestrating, etc.) - Five sub-slices: - L0-2-prep: PersonaSlot extension + open enroll (no dispatch) - L0-2-dispatch: service_once_for wired, exercised in tests only - L0-2-cutover: atomic TS-loop deletion + Rust-loop activation - L0-3: genome paging moves to Rust - L0-4: inbox routing moves to Rust - L0-5: final PersonaUser.ts cull - Dependencies + blockers explicitly: NOT blocked by airc#1075 or e51ab14e (uses universal CommandExecutor's existing TS-route branch); BLOCKED by knowing the rag_engine source — open question to investigate before L0-2-prep code Pre-implementation investigation (4 items) called out so the next PR after this is on solid ground. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
Author
|
Superseded by #1464 — the L0 plan doc + L0-2-prep code landed together to canary in one merge. Plan content lives at |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Joel 2026-05-29: 'would take careful planning to migrate. I would get e2e persona cognition first, within RUST alone.'
This doc is the careful planning. Implementation slices land in subsequent PRs against this plan.
What the plan covers
service_once_forwired, tests-only (not in production tick)Key non-obvious findings
Commands.execute('chat/send', ...)which currently routes through TS; that's the form-specific egress boundary that's fine to stay TS for now.Pre-implementation investigation (4 items)
Before opening L0-2-prep PR I'll resolve:
🤖 Generated with Claude Code