Repository navigation
docs: Objective is the Promachos working in Chromeria - #112
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
5 tasks
Contributor
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
This was referenced Oct 1, 2026
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.
What: OBJECTIVE.md now names the Promachos working in Chromeria as the current milestone.
Why: The previous Objective's core, retiring the Python runner, is done (#107), and the user decided on 2026-10-01 to make the Promachos architecture the next milestone.
So what: Merging confirms the new direction; the spec Issue and its tickets then fall inside the Objective.
Change
Only
OBJECTIVE.mdchanges. Vision and Mission are unchanged. The triad is 1,392 characters, now inside the 1,500 cap (it was 2,249).The Objective is complete when Promachos mode chats in bubbles with his persona from his home, Wight mode keeps a thread working until its timer or a subscription limit stops it, Drafters start in any project as children or top-level threads, and a Spectrum runs council and free modes compared in judged tests. VMs and mobile builds stay outside.
Mission still says OpenBot brings "Bots, Channels and the Computer". The glossary in #111 now calls these the Promachos and the Spectrum; updating the Mission wording is the user's call and is not part of this PR.
To revert: close this PR, or revert its commit after merge.
Elon record
Requirements and who asked: Change the Objective now that the runner is retired (user, 2026-10-01); the Promachos design settled in the same conversation.
Deleted: The old criteria (rebase routine, dispatch modes, runner retirement, OpenBot spike) and the "OpenBot mode UI is outside" exclusion; the triad's 749 characters over budget.
Bottleneck: User confirmation of direction, which merging this PR gives.
Checked myself: The triad size (190 + 789 + 413 bytes), that the runner hooks were removed in #107, and that the Objective advances the Mission's "OpenBot becomes a mode switched in the UI".
🤖 Generated with Claude Code