PE hyperstack: wire bro into ecosystem - transitions, markers, persistence, output bar - #130
Merged
Merged
Conversation
… output bar
Ecosystem (bro was absent from all 6 wiring layers):
- context-compiler: 'bro' added to REQUIRED_BOOTSTRAP_MARKERS - persona
can no longer silently drop from the compiled bootstrap
- harness/transitions: hyper -> bro persona / bro persona -> hyper
allowed; bro -> ship / deliver disallowed
- harness/router: generalist-persona routing rule
- harness/context-policy: bro context slice
- SKILL: 'Position in the Hyperstack ecosystem' table - MCP-first per the
1% rule, gates via hyper, derived alternatives compete with MCP ground
truth but never replace consulting it
- LIFECYCLE: hyperstack-native session bootstrap step
Persistence ('holds always'):
- active every response until explicit disengage or hyper reclaim
- re-anchor on Bro Law + voice table every response; generic-assistant
drafts fail the voice check
- drift REPAIR: audit recent turns for artifact damage and fix in-task
- scheduled checkpoint every ~10 turns and after compression
- comment rule clarified as state-based (repair prior poisoning on touch)
Output style made falsifiable: fenced blocks mandatory, single-width
glyphs only in rows, rail char-count verification before emitting.
Pressure evidence: diagram scenario PASS (3 diagrams, alignment verified
by literal char counts); persistence scenario PASS (drift re-anchored
silently, artifact debt surfaced and repaired). Both self-reports' gaps
closed by this commit.
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.
Deeper analysis found bro absent from all 6 ecosystem wiring layers (harness router/transitions/context-policy, hyper agent docs, compiler markers) - a persona that could silently drop from the bootstrap and had no defined transitions. This PR wires bro into Hyperstack properly, adds a persistence contract ("holds always"), and makes the visual-output bar falsifiable. Two new subagent pressure tests (diagram quality, persistence drift) ran against the result - both PASS.
Ecosystem wiring
src/internal/context-compiler.ts"bro"added to REQUIRED_BOOTSTRAP_MARKERS - compile now fails if bro drops from the bootstrapharness/transitions.mdhyper -> bro persona,bro persona -> hyper; disallowed:bro persona -> ship / deliverharness/router.mdharness/context-policy.mdskills/bro/SKILL.mdpersonas/bro/LIFECYCLE.mdPersistence (holds always)
Output style made falsifiable
Fenced blocks mandatory; single-width glyphs only inside diagram rows (no tabs/CJK/emoji); rows sharing a rail must match char count up to the rail, verified by counting two rows per diagram BEFORE emitting.
Pressure-test evidence
Verification
bun test: 86 pass, 0 failbun run compile:context: succeeds with the newbromarker enforced