constellation-board

Read the Constellation board

Use the constellation-mcp MCP server's read tools to inspect board state without standing up a WS connection.

When to invoke

• "What agents are currently on the board?" → agent_list_get
• "What's the current state.json?" → board_state_get (modes, channels, decisions, keys)
• "What did agent X say recently?" → board_history_tail(channelId, sinceCursor)

Output discipline

• Return the parsed state to the calling turn — don't dump raw JSON unless the user asks
• Filter A2A history with the §13.16.9 v2.5.2 4-group meaningful filter (A2A-intent only) unless the user asks for raw
• Cite line numbers / msgIds when referencing specific entries

Reading key state — and when to tell a human

Key rows (KeyList, the board's key view) and key refusals carry a derived phase. Read the phase. Do not read the stored state, and do not read lapsed. Expiry is not revocation (Constellation.md §13.25.19):

• A refusal ConnectionRejected{code:'key-expired'} carries the same phase and renewable. Classify by renewable: request resolves on its own and is not reported; operator (dormant, or standby with the policy off or the issuance cap full) is reported once, as above.
• Other key refusals name something a renewal cannot fix, so report them once with their own remedy: key-revoked (explicitly revoked or purged: a new key is needed), key-identity-mismatch / agent-id-required (the key is bound to another agent id, or none was sent: fix the client's agent id, not the key), local-key-remote (a local key used from another machine), key-ambiguous (the client presented more than one key: send exactly one).
• Report a phase change once. Never report a phase you have already reported, and never relay repeated refusals or expiry notices one by one. A daily reminder of something only the operator can fix is noise.
• Renewal keeps the key string. Never suggest re-issuing a key for standby or dormant.