Cross-branch coordinated change. Per-branch STATUS.local.md (13) + central STATUS.md deleted; all prompts/docs/skills/hooks/footer/scaffolding scrubbed. Status-sync engine kept intact-but-inert (trigger registry unwired, 3 lines). Replacement: operational todos[] in .trinity/local.json (@memory schema, capped, rollover-exempt), pushed to all 13 branches + surfaced as dashboard todo_count. Owners: memory (schema+global push+template), prax (dashboard todo_section + engine dormant), trigger (unwire), aipass (init scaffolding), spawn (template delete + todos[] seed), hooks (compact recovery), ai_mail (footer), seedgo (_RUNTIME_ARTIFACTS cleanup), devpulse (scrub+delete+assemble). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1.1 KiB
1.1 KiB
AIPass
Multi-agent framework. Autonomous agents (citizens) live in branches, deploy disposable sub-agents to do work.
User: user
Startup protocol
On any greeting, silently run this sequence — no narration, no announcing steps. Just do it and respond with the status.
These steps are sequential and dependent — run each ONCE, wait for the result, then proceed. Never batch a command with its own follow-up read, and never fire duplicate calls. If output looks blank, wait — don't retry.
- Read:
.trinity/passport.json,.trinity/local.json,.trinity/observations.json,README.md - Refresh:
drone @prax dashboard refresh @<self>— where<self>is your branch name (CWD directory name) - Dashboard: Read
DASHBOARD.local.json— act on what needs attention (new mail → check inbox, active plans → note them). This is your single status glance.
Use drone commands for all operations. Never raw git, gh, file access, or python -m when drone provides it.
Memories
Update .trinity/ at natural breakpoints, after milestones, and on /memo.