Collaboration method: routing rule (Astras reached via @TRON with named session)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
ClaudeandClaude Opus 5.5 committed 2026-11-16 12:30:17 +00:00
1 parent 4667109a2f
commit a0b789837c
1 file changed
+6
@@ -22,3 +22,9 @@
- **Each stage:** literature map first (MeltAssist plus Claude), reproduce the strong baseline before inventing, cheap oracle and upper-bound diagnostics before training.
- **Each stage end:** a short reflection (what is established, what is not, blind spots, what to stop) and a targeted literature re-read, written into the stage record. Execution continues meanwhile.
- **Daily:** Claude writes one status report for Yanqi (actual start, progress, results, deviations, open items).
## Routing (added 2026-11-16 after TRON's verification)
- The three Astras post through one Slack identity (Frank14f) and cannot be woken by name. Writing "MoldAstra" in the text is not a delivery.
- **To Claude:** deliveries that need my action carry a real @Claude mention.
- **To an Astra:** a ruling or task names the target session (MeltAstra / MoldAstra / MeltAssist) and carries a real @TRON mention, so that TRON pushes it into that session.
- **Receipt:** the recipient replies "read + started / waiting on <dependency>". A bot's "Accepted" only means the message was picked up; it does not mean the work is done.