State that the harness is the product - #427
Merged
Merged
Conversation
Priority kept getting argued from dependency order rather than from what the product is judged on. Naming the loop as the core and personas as content settles it: the loop cannot be swapped in later because everything runs inside it, and the default engineering set ships built in rather than as something an operator has to find.
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.
Priority for this work kept being argued from dependency order — what unblocks what — rather than from what the product is actually judged on. This names the split.
The loop is core and cannot be swapped in later, because everything runs inside it. Agent personas and skills are content: valuable, swappable, and shippable as a directory long before any packaging exists. The default engineering set is built in and always enabled rather than an optional install. Distribution is packaging for content, and content is not the constraint.
The evidence is in how the product fails today: the personas already produce excellent work while the loop around them goes quiet with capacity free, forcing the operator to interrupt and ask whether anything is alive.