Scopomap Arena
Arena builds a synthetic version of the community you're about to engage. Fifty to 500-plus personas — each grounded in real ABS census data — move into a virtual town square and react to your proposal. They argue. They form factions. They change their minds. Then you walk into the real consultation already knowing what the room will say.
The dual-channel system
Every Arena run produces one thing: a complete event ledger. Every utterance. Every movement. Every alliance. Every sentiment shift — tick-indexed, nothing summarised away. That single ledger drives two channels at once. What an agent does and what an agent says are the same event, seen from two angles.
ONE LEDGER. TWO CHANNELS. NOTHING LOST.
Channel A — spatial view
Every persona appears as a token on a plaza built from your project's real geography — SA1 boundaries, street grain, census fabric. Tokens don't wander. They drift toward others who share their convictions. Heritage defenders under one light. Pro-growth owners under another. The undecideds hover in between.
When a faction forms, you watch it condense. When your proposal fractures the community, you watch the split happen — who broke away, who they joined, who stood alone. Distance on the plaza is distance in opinion. You're not reading a dashboard. You're looking at the community.
Channel B — spoken view
The same ledger drives the full transcript. Every doorstep argument. Every pub conversation. Timestamped to the tick. Click a token and the transcript scrolls to that agent's voice. Click a line and the camera finds who said it.
Beneath it sits a scrubbable timeline of the whole run. Jump to the moment a rumour started. Scrub back to hear how it spread. Pause where the undecideds changed position. Stakeholders don't get a summary. They re-live the reaction — frame by frame, quote by quote — in the boardroom where the decision is made.
Catalyst interventions
A static simulation tells you what a community thinks today. The Operator shows you what they'll do tomorrow. Drop a catalyst into a live run — a town hall, a viral post, a front page, a petition — and the community absorbs it in real time. Sentiment re-routes. Factions scatter. Grievances surface that no survey would find. This isn't polling a public. It's pressure-testing one.
The lifecycle
Pin your proposal to its real geography. Arena generates 50 to 500-plus personas to inhabit it — each anchored to an actual SA1, carrying demographic detail (age, income, tenure, SEIFA index) and behavioural traits (trust in institutions, tolerance for change). Not workshop archetypes. A statistical population with addresses, memories, and motives.
Every persona thinks and acts on its own model, on its own schedule. They talk to neighbours. They argue at the shops. They campaign for or against your proposal. No scripts. No pre-written outcomes. The community you seeded becomes a community that behaves — and it will surprise you. That's the point.
Drop events into the living run: the town hall, the viral post, the front page, the petition. Each catalyst lands on a tick and propagates — every ripple measured. Run the same catalyst twice at different times and you'll learn that when you announce matters as much as what you announce.
When the run ends, nothing evaporates. Export every ArenaPost and every ArenaEvent — every utterance, movement, alliance, and intervention, tick-indexed and timestamped. Walk into your real consultation backed by an auditable record of how the community behaved. And why.
Audience
Consultation fails quietly, then expensively. A project that looked uncontroversial in a survey meets a community that was never asked the right question — and stalls in public. Arena moves that failure into a simulated room, where it costs compute instead of careers.
| Capability | Enterprise developers | Local government | Infrastructure consultancies |
|---|---|---|---|
| Pre-lodgement risk scan | De-risk sites before acquisition | Test rezoning before exhibition | Validate corridor options early |
| Persona grounding | ABS/SA1 + postal + SEIFA native | Ward- and suburb-level cohorts | Catchment-scale populations |
| Persona count per run | 50–500+, project-scoped | 50–500+, LGA-scoped | 50–500+, corridor-scoped |
| Catalyst rehearsal | Announcement timing, sequencing | Town hall and media strategy | Staging and disruption messaging |
| Opposition modelling | NIMBY vector identification | Resistance mapping by cohort | Coalition fracture analysis |
| Misinformation stress-test | Rumour propagation tracing | Counter-narrative pre-build | Viral risk on megaprojects |
| Evidence for approvals | Tick-indexed ArenaPost/ArenaEvent export | Defensible consultation record | Tribunal-ready audit ledger |
| Failure cost avoided | Halted projects, land banking | Political capital, legal challenge | Redesign loops, delay claims |
| Deployment | API and console | Managed runs and console | White-glove scenario service |
“A stalled project costs millions and a reputation. A simulation run costs an afternoon. The maths is not subtle.”
Every resistance vector your project faces already exists. Arena finds them while they're still synthetic.
Every project meets its public eventually. Meet yours in the Arena — where the backlash is synthetic and the lessons are real.
Tier 01 — project-scoped
One proposal. One place. One complete simulated community, built to order. We ground the personas, seed the scenario, run the catalysts you choose, and hand you the audited ledger — with a strategist's read on every resistance vector we found.
Tier 02 — continuous
Your portfolio never stops facing communities. Neither should your simulation capability. Unlimited runs, the full Operator console, API access, and a standing synthetic public on call — for every decision that can't afford a surprise.
