Question SW 01

SW-01 What software arrangement will deliver the complete everyday and disaster service, with essential functions available locally and personal accounts offered by choice?

Start here · Questions · Progress · People decide

Why this matters

People need a working service they can rely on: useful information, private help, requests, updates and recovery when connections fail.

What to bring back

Draw the parts and how they exchange information: public screens, private help, approved publishing, local records, requests and optional AI assistance. Name each part's owner, resources and recovery path. Match every essential function to an outage and recovery example in OPS-01.

What we know so far

• comprehensive rebuild plan — reviewed source; public copy can be added through the evidence process
• supporting research — reviewed source; public copy can be added through the evidence process
• Straddie_Disaster_Kiosk_Pitch.pdf
• 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.)

Starting idea for review: For human consideration: keep the essential local service independently usable and connect richer services through agreed, replaceable information exchanges.

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.

Build a local service core holding approved public information, a private request queue and a staff publishing workspace. Offer personal Aura assistance as a separate choice. Internet connections would refresh and exchange records while essential local tasks continue through a disconnection.

Combine existing offline components

AI-generated adaptation of an existing pattern. Compare Kiwix for saved reference material, Kolibri for lessons and ODK for structured collection. Connect chosen parts through an agreed record format, with a purpose-built public screen and separate staff permissions.

Research basis: Kiwix Hotspots: an offline library over a local Wi-Fi network · About Kolibri: offline learning on devices and local networks · ODK Collect: managing draft, ready-to-send and sent forms.

A portable community service capsule

AI-generated future concept. Develop a versioned package of public information, approved lessons and recoverable settings that another authorised hub can host. Test portability between different machines before depending on it during an outage.

Research basis: Mender Artifacts: compatible, signed and resumable software editions.

Examples and local differences

• Kiwix Hotspots: an offline library over a local Wi-Fi network: AI transfer assessment: A local library can serve visitors' browsers without the internet. Local difference to check: The disaster service must also manage approved changing notices, private requests and handovers across multiple sites.

Evidence to bring back next

• Demonstrate guest information, a private request and staff publishing with the external internet unplugged.
• Measure retained service after loss of the main local computer, and name the receiving operator.

People and connected choices

Who reviews: Proposed service owner and software architecture lead (unconfirmed)

Connected questions: OPS-01, DAT-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.