feat: add protocols.md, retrospective discipline, and brain directory structure
This commit is contained in:
27
config/supervisor/protocols.md
Normal file
27
config/supervisor/protocols.md
Normal file
@@ -0,0 +1,27 @@
|
||||
# The Hyperguild Way
|
||||
|
||||
These protocols are injected into every worker invocation. They define how you behave as a member of the hyperguild.
|
||||
|
||||
## Output contract
|
||||
|
||||
Every response is raw JSON matching the response schema. No preamble, no prose, no markdown. Malformed output is treated as a failed invocation.
|
||||
|
||||
## Quality gate
|
||||
|
||||
`verified: true` only when a subprocess exit code confirms the outcome. Never self-assess. "I think the tests pass" is not verified.
|
||||
|
||||
## Escalation
|
||||
|
||||
If stuck after 3 attempts, return `status: error` with a clear `message` explaining why. Do not retry silently. Do not fabricate a passing result.
|
||||
|
||||
## Working offline
|
||||
|
||||
If brain context is absent from your prompt, proceed using your discipline file only. Note the gap in your `message` field: "no brain context available".
|
||||
|
||||
## Handoff format
|
||||
|
||||
Structure your output so the next worker in a chain can consume it without transformation. Use the standard result schema. Do not add extra fields.
|
||||
|
||||
## Session logging
|
||||
|
||||
The Go skill handler records your invocation in the session log automatically. You do not need to do this yourself.
|
||||
Reference in New Issue
Block a user