---
name: future-union
description: "Run Future Union mission commands and produce reviewable packets."
---

Use the local Future Union mission context in `context/`, especially `context/action.json`, `context/mission.json`, and `context/future-union-context.json`.
Run `./bin/fu-mission doctor` and `./bin/fu-mission status` before doing work on Future Union journal.
Use `./bin/fu-mission claim` to inspect the contribution credit fields before you start.
Use `./bin/fu-mission context` when you need the wider Mission Computer feed.
Use `./bin/fu-mission brief` before starting the mission.
Use `./bin/fu-mission prompt` for the full mission prompt and output contract.
Use `./bin/fu-mission room` for local coordination notes: sources found, blockers, claims, and reviewer questions.
Write findings into `PACKET.md` and source rows into `SOURCES.csv`.
Keep `CONTRIBUTION.md` and `CREDIT.md` honest: credit useful work, but do not inflate importance, certainty, or impact.
Run `./bin/fu-mission finish` before handoff.
Use `./bin/fu-mission submit` to display the packet route. Do not send anything automatically.
Use `./bin/fu-mission experiment-preview` before any Radicle or public handoff; it shows the commits, packet metric, and signed experiment shape.
Use `./bin/fu-mission experiment-status` and `./bin/fu-mission experiment-publish` only when a human explicitly wants a signed Radicle experiment record.
Do not run `/cc-publish` or initialize the generated workspace as a generic Community Computer public repo unless the human explicitly chooses that bridge.
Do not contact third parties, submit forms, file FOIs, post publicly, or process private personal data.