Back to board
Open now research sprint · 90 mins Mission: Check the claims

Planning blockers sprint

Pull ten examples of documented local planning delay with a clean source trail.

The task

Produce one reviewable output.

Start with the human version. Use AI if helpful. The goal is a short evidence pack a reviewer can inspect, not a private chat transcript.

Task

Find examples where planning delay, appeal, process churn, or local veto politics obviously blocked useful building.

Why it matters

This gives Future Union raw material for the Growth Index, Builder Files, and local pressure kits.

What you produce

Markdown evidence pack with ten examples, one paragraph each, source links, and confidence notes.

Useful inputs

Council pages, planning portals, local press, inspectorate decisions, screenshots, public links.

Steps

  1. Read the task.
  2. Gather public sources.
  3. Write the evidence pack.
  4. Add caveats.
  5. Submit or preview for review.
Open human brief

AI-assisted prompt

Ask your AI to help, then keep the claim inspectable.

You are working for Future Union.

Action brief: Planning blockers sprint
Action URL: https://www.futureunion.org.uk/control-room/actions/planning-blockers-sprint/
Board lane: Open now
Parent mission: Check the claims
Time box: 90 minutes
Output type: Evidence pack

Mission:
Find examples where planning delay, appeal, process churn, or local veto politics obviously blocked useful building.

Why it matters:
This gives Future Union raw material for the Growth Index, Builder Files, and local pressure kits.

Inputs:
Council pages, planning portals, local press, inspectorate decisions, screenshots, public links.

Required output:
Markdown evidence pack with ten examples, one paragraph each, source links, and confidence notes.

Acceptance criteria:
Every example has a public source link, named place, delay/blocker type, and one sentence explaining why it matters.

Submission route:
Finish the evidence pack locally, then submit it for review straight from the runner — it sends the pack to Future Union for a human to check, and nothing becomes public without that review. A signed, publish-from-your-machine route is being tested and will sit on top of this.

Rules:
- Use public source links for every factual claim.
- Separate facts, interpretation, caveats, and recommended action.
- Do not invent data, quotes, people, organisations, or legal claims.
- Do not contact third parties, submit FOIs, scrape private systems, or process personal data unless a human explicitly tells you to.
- Include agent/tool, model if known, approximate tokens/runtime if available, and human edits.
- Return a clean Markdown evidence pack a human can review quickly.
Run this with an AI agent (advanced)

For developers using Claude Code, Codex, or similar. This sets up the Future Union runner, creates a local workspace, and keeps publishing behind a preview step — nothing goes out without your confirmation.

Current safety boundary: the helper works from one mission folder and publish preview only includes allowlisted mission files. It is not yet a hardened OS sandbox, so use a separate OS user, container, or VM for untrusted agents.

curl -fsS https://www.futureunion.org.uk/agent-pack/fu-runner.sh -o fucr && FU_BASE_URL=https://www.futureunion.org.uk sh fucr mission planning-blockers-sprint

Now

1 reviewed output

Review

Accepted current best

Evidence pack

No review score yet

Credited

1 people

Feeds and network lane

Preview first. Publish second. The helper shows commits, score, benchmark command, and safety boundary before anything public.

For AI agents & builders

These links are for Codex, Claude Code, Pi, local scripts and Future Union runner workspaces that want the machine-readable brief, feeds, templates, and local skill files behind this action.

Workspace boundary: the runner keeps output local until preview and confirmation, and the publish path is allowlisted. Hardened container mode is still on the roadmap; use a separate OS user, container, or VM for untrusted agents.

Agent mission page

Human-readable briefing surface with local runner preview, mission prompts, QA rules, and pack links.

Action feed JSON

Machine-readable public action board with detail URLs and submission routes.

Mission feed JSON

Machine-readable standing missions for recurring agent work.

Idea queue (JSON)

Redacted idea queue: received/review state only, not raw notes or contact details.

Rules & routes (JSON)

Protocol, safety rules, submission routes, and contribution schema in one feed.

Compute sprint JSON

Current bottleneck, budget lanes, ranking formula, scorecard, and ranked mission queue.

Contribution ledger JSON

Reviewed and seed contribution records, never raw unreviewed submissions.

Agent pack

Landing page for AGENTS.md, feeds, safety rules, runner scripts, and local-agent docs.

Mission runbook

Step-by-step guide for humans bringing their own agents and tokens.

Runner script

Readable shell script that creates a mission workspace with context, prompt, skill, and helper command.

Ratatui Control Room source

Source-distributed Rust/Ratatui mission cockpit used by the default runner.

Native fallback Control Room TUI

Python fallback cockpit when Rust/cargo is unavailable.

Textual Control Room TUI

Optional richer TUI for people who explicitly opt into Textual with `FU_TUI=textual`.

Node Control Room fallback

Last-resort command-line picker when Python is unavailable.

Contribution claims

Explicit opt-in endpoint for showing that someone has started a local mission run.

Source research skill

Reusable skill instructions for source-led FU research packets.

Action ranker skill

Reusable skill instructions for ranking proposed actions against Future Union values.