Question OPS 04

OPS-04 What should people be able to do in everyday, disaster, disconnected and low-energy operation, and who should authorise the changes?

Start here · Questions · Progress · People decide

Why this matters

People need a clear explanation of the service available now, while operators need agreed conditions for changing it.

What to bring back

A service-state table showing available tasks, change conditions, responsible roles, public explanations, priority functions and the human handover when capability changes.

What we know so far

• comprehensive rebuild plan — reviewed source; public copy can be added through the evidence process (Sections 2, 5-7 and 8)
• 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.

Agree four visible service states: everyday, disaster, disconnected and low energy. Each state should explain available tasks, information age, connection limits, human responsibility and the next change trigger, keeping essential public guidance available throughout.

Existing-practice adaptation

AI-generated adaptation of an existing pattern. Prepare a signed-off state table. In low energy, prioritise approved text notices, local lookup and request receipts; reduce display brightness and optional media. An accountable operator changes the public service state using measured conditions and agreed rules.

Research basis: Shoalhaven: Community Information Hubs Launched · Australia's AI Ethics Principles.

Future concept to explore

AI-generated future concept. Let Aura explain why functions changed and forecast available service from measured energy and connection data. AI/SI could propose a change with supporting evidence; a narrowly delegated controller might apply only pre-agreed bounded actions and record the result.

Examples and local differences

• Shoalhaven: Community Information Hubs Launched: AI transfer assessment: Treat power, connectivity and the public information experience as one service design. Local difference to check: Shoalhaven's equipment example does not provide this project's thresholds or authority to change an emergency service.

Evidence to bring back next

• Reconcile the state table with measured hardware power budgets.
• Test whether users understand disconnected status and the meaning of saved requests.

People and connected choices

Who reviews: Luke, as project initiator, coordinates proposed service behaviour and the reasons for each choice. The future operator and actual information issuers review the proposal and agree responsibility for changes within their authority, with relevant qualified professionals reviewing overlapping requirements.

Connected questions: OPS-01, OPS-03

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.