Consolidated into #371. Closed only as a superseded review thread, following Joel Z. Leibo’s category guidance. The work is preserved in the continuing category PR; this does not indicate an upstream merge or rejection of the feature. Continuing issue: #371; continuing PR: #372. Reusable model-adapter/prefab additions continue in PR #356; the Bellwether example continues in PR #372.

Need

The shared Bellwether service in #316 currently ends after one explicitly labelled fixture action. It does not provide the complete three-watch human-player journey described by the example: residents can respond, but resource allocation, consent, work completion, watch accounting, and grounded dawn consequences need explicit implementation.

Proposed bounded contribution

• Dusk, High Tide, and Before Dawn, with four consequential human choices per watch, free inspection, public/private dialogue and proposals, explicit commitments, allocations, authorized transfers, repair orders, and waiting.
• Scenario-specific resolution components inside the example, using standard Inventory.apply, Simulation, Sequential, prefabs, observation routing, and logs. Six generator fuel plus two owned reserve units versus nine baseline demands; the spare part and accepted/performed labor are required to reduce final beacon demand. Spoken narration must not create consent or materials.
• Four independently configured resident actors using standard minimal/basic policies, with a clearly separate cooperative fixture and bounded local Ollama mode. Basic must not silently drop optional account/affiliation components: reuse minimal's existing optional-component assembly rather than duplicate the prefab.
• Reuse Add shared attached operations and Bellwether human-play fixture #316's fixed-audience player/editor/attached-CLI operation service, privacy filtering, revisions, retries, and true worker-quiescence guard.
• A coastal player page with cast, watch/choices, inventory, commitments, dialogue and an epilogue derived from actual recorded outcomes.

Acceptance and limits

Verify two materially different complete strategies, resource conservation and consent/refusal/repair, private observation recipients, atomic errors, stale revisions, retry idempotency, default prefab parity, real Chromium plus attached CLI, and a bounded local-model journey to dawn. Report model calls and latency separately from automated interaction time. A fixture is not a live simulation result, and neither establishes scientific or human-usability validity.

This is dependent on #316 (which depends on #306 and #312), not a duplicate of those contributions. Full editor authoring, checkpoint continuation/isolation, experiment/branch workflows, undo/redo and general institution editing remain outside this game contribution. No automatic consensus, unrestricted physical-action inference, or deterministic hosted-model guarantees are proposed.

Related overlap: #260 changes Ollama markdown sanitization; the local-call change needed here is optional request timeout/output limits, not response sanitization.