Question OPS 01

OPS-01 What should the first complete version do for people each day and during a disaster, and where should its service limits sit?

Start here · Questions · Progress · People decide

Why this matters

A clear service envelope, meaning the people, tasks and conditions the service is designed to support, lets every part of the stack work towards useful outcomes.

What to bring back

A service brief naming priority users, the first three everyday tasks, essential disaster tasks, success measures, service limits and accessible ways to take part.

What we know so far

• comprehensive rebuild plan — reviewed source; public copy can be added through the evidence process (Sections 1-2 and 13)
• Professional review and comparison of proposed improvements (When this work overlaps professional or public-authority responsibilities, compare the proposal and Luke's research with applicable industry/global best practice and relevant legal-engine sources. Record differences, reasonable improvements and deficiencies, with the responsible reviewer and response. Routine authorised drafting and wiki work can advance.)
• Council plan crosswalk and proposed Aura integration (Relevant question row identifies the management/recovery source section and printed/PDF page. AI-generated analysis, 21 October 2026; proposed checks and actual review/operating agreements retain separate status.)

AI-generated potential answers

For discussion and review · research checked 2026-10-20. These are AI-generated options and transfer assessments. The user's request and research method identify the source of this work. The source catalogue states what the references establish. The decision and approval record retains its own status.

Begin with an account-free local calendar, checked notices and service finding, then add a clearly explained disaster service for approved information, assistance pathways and practical learning. Agree success through completed tasks and service-owner participation.

Existing-practice adaptation

AI-generated adaptation of an existing pattern. Adapt Sunshine Coast's clear information categories and Wellington's community coordination approach. Demonstrate an everyday event lookup, a checked disruption notice and a help request to a simulated receiving desk before proposing staffed operation.

Research basis: Sunshine Coast: Disaster Hub helps Coast stay safe · Wellington Region: Community Emergency Hubs · Digital Performance Standard: measure service success.

Future concept to explore

AI-generated future concept. Let a person's chosen Aura explain the same verified service record through voice, text or XR, adjusting detail to their needs. Shared public information remains available independently of personal accounts, advanced models and an internet connection.

Examples and local differences

• Sunshine Coast: Disaster Hub helps Coast stay safe: AI transfer assessment: Use familiar service categories as the first public doorway. Local difference to check: Sunshine Coast's live council hub does not establish Minjerribah offline capability, staffing or authority.

Evidence to bring back next

• Ask prospective users to try the three tasks and record misunderstandings.
• Prepare a service envelope with actual information owners and candidate receiving services.

People and connected choices

Who reviews: Luke, as project initiator, coordinates the service proposal and brings research and options forward. Prospective users and the people responsible for receiving help requests review practical suitability; relevant qualified professionals and authorities review any overlap with their duties. Their participation and roles are to be agreed.

Connected questions: This is a starting question.

Work state: open. Assigned person or AI assistant: Ready to be assigned.

Research and alternatives can move ahead while connected decisions develop. Before acting on a choice, check the people, evidence and approved scope in People decide.