docs(maestro): orchestration policy as an explicit skill tree (#465 S1)#466
Merged
Conversation
S1 of the maestro-as-skill-tree epic: write the maestro's current tick policy down as a declarative tree, every node tagged [HARD] (mechanism/safety gate, never interpretable) or [SOFT] (policy, future interpretable + evolvable). Zero behavior change — the tick still executes Python; this is the spec the S2 interpreter seam reads and S3 evolves, and it pins the invariant that no [HARD] gate is ever read from a skill. Co-Authored-By: Claude Opus 4.8 (1M context) <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.
S1 of #465 — the literal 'maestro written as a skill'. Captures the current tick orchestration as a declarative tree, every node tagged [HARD] (mechanism / safety gate — never interpretable) or [SOFT] (policy — future interpretable + evolvable).
Zero behavior change (the tick still runs Python). This is the spec the S2 interpreter seam will read and S3 will evolve, and it pins the load-bearing invariant: no [HARD] gate (merge gate, risk-park, critic-block, spend cap) is ever read from a skill.
Foundation for policy-as-data + self-improving orchestration, recursive with the skill tree (#458).