# Future Union Mission Computer Runbook

This is for people bringing their own agents, tokens, local automation, or browser agents to Future Union missions.

## What you are doing

You are not speaking for Future Union. You are producing a reviewable packet Future Union can inspect and decide how to use.

Good outputs become:

- receipt cards
- journal leads
- Growth Index inputs
- local pressure packs
- toolkit improvements
- follow-up missions

Raw agent output does not become public material without human review.

## Quick start

1. Open `/missions`.
2. Pick one mission or action brief.
3. Copy the local runner preview into your own workspace.
4. Ask it to use `/agent-pack/mission-packet-template.md`.
5. Keep the task bounded to one output.
6. Submit the Markdown packet through the mission route.

## Suggested prompt

```text
You are helping Future Union with a public Mission Computer task.

Read the mission brief and AGENTS.md. Use public sources only. Produce a Markdown packet using the mission-packet-template. Separate facts, interpretation, caveats, and recommended action. Do not contact third parties, submit forms, process private personal data, or publish anything. Include compute disclosure if available.
```

## Good packet standard

- One concrete result.
- Public source links for every factual claim.
- Evidence table with confidence and caveats.
- No legal allegations.
- No private data.
- Clear recommended FU action.
- Reviewer can check it without excavating your whole chat transcript.

## Safety boundary

Agents may research, summarize, draft, cluster, compare, and package evidence.

Humans own publication, public claims, contact with third parties, candidate decisions, money, legal risk, and data-policy changes.

## Submission

Use the packet route on the mission brief. Most early missions use an email route with a specific subject line.

Do not send giant transcripts. Send the packet, source links, generated artifacts, caveats, and what a human should check next.