Question COM 01

COM-01 What information must each type of connection carry, how quickly should it arrive, who can send it and how will receipt be confirmed?

Start here · Questions · Progress · People decide

Why this matters

Matching the message to the connection helps urgent notices get through while richer maps and simulations remain useful locally.

What to bring back

Make a service-and-connection table for notices, maps, requests, device status and sensor readings. Show message size, acceptable delay, priority, sender authority, privacy and receipt status. Compare essential-service and richer-service options.

What we know so far

• Straddie Disaster Kiosk Pitch.pdf — reviewed source; public copy can be added through the evidence process
• 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.)

Starting idea for review: For review: give short, verified essential notices priority and keep large maps and media available locally or transfer them over connections with suitable capacity.

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.

Give each information class a clear journey: urgent checked notices, help requests, equipment status, maps and richer media. Set size and delay targets before choosing links. Treat saved, transported, received, accepted and acted-on as separate states, with sender authority and privacy attached to each record.

Message classes and existing uplinks

AI-generated adaptation of an existing pattern. Map notices to CAP-compatible identifiers, times and update references. Compare ordinary fixed/mobile service with an activated satellite alternative; use compact summaries where bandwidth or energy is constrained while preserving the authoritative source.

Research basis: How to prepare: nbn and emergency events · Starlink Mini specification sheet, pages 3 and 8 · Common Alerting Protocol Version 1.2.

Adaptive fidelity envelope

AI-generated future concept. Design one signed information record with text, audio and richer spatial layers. A local Aura could choose the layer that fits available power and bandwidth while retaining common identity, issue time, meaning and receipt status.

Examples and local differences

• How to prepare: nbn and emergency events: AI transfer assessment: NBN's restoration and community-support equipment illustrate several connectivity roles within disaster response. Local difference to check: Local delivery targets and receiving-service agreements remain to be designed and tested.

Evidence to bring back next

• Measure representative record sizes and acceptable waits with prospective users and operators.
• Confirm authority, privacy and receipt meaning for each information class.

People and connected choices

Who reviews: Proposed communications architect with publishers and operator; role and appointment awaiting confirmation

Connected questions: OPS-01, DAT-01, PHY-01

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.