Pin the operator harness instruction block with tests - #4
Merged
Conversation
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
Milestone 3 of the v0.1 plan: the instruction block content that makes an agent behave as the operator's team, guarded by tests.
Changes
src/template.ts): onboarding now closes the loop deterministically (the agent sets communication dimensions withtod config set, runstod sync, and marks onboarding complete in operator memory); persona composition explicitly reads the profile from~/.tod/operator.mdto decide which disciplines to supply.tests/template.test.ts): content assertions for every required harness section (onboarding, memory rules, communication, virtual team, work tracking, git workflow, do-not-edit rules), a guard that tod's own implementation stack never leaks into operator-facing instructions, a check that configuration changes the rendered rules, and an 8 KB size budget enforced across all 81 communication-dimension combinations.Why
The block is the product: everything the operator experiences flows through it. Pinning its sections and size in tests means later edits cannot silently drop a rule (say, the git workflow) or bloat the block until it crowds agent context windows.
🤖 Generated with Claude Code