Domain ECO

Project connections

Start here · Questions · Progress · People decide

Define useful connections to the wider ecosystem while keeping the kiosk and resilience network moving.

Question	What we are working out	AI-generated potential answers and research	Work state
ECO-01	How will approved calendars and notices keep everyday activity, cancellations, closures and transport changes in step across kiosks?	AI-generated option: Give recurring events and individual dates stable identities, with local timezone, confirmation, cancellation and replacement history. Connect the Events Engine to an approved release stream for the notice network. Offline screens would explain the saved edition and remove or qualify expired information. AI-generated future concept: Explore an assistant showing an authorised organiser which linked notices, transport advice and roster entries may need review after a cancellation. It would draft updates for their actual owners and report which screens have received approved editions. Research examples: RFC 5545: iCalendar · RFC 9171: Bundle Protocol Version 7	open
ECO-02	How will community media, stories and notices reach the right screens while urgent service messages take priority?	AI-generated option: Use an approved media release record naming the creator, rights, audience, accessible versions and expiry. Everyday stories and notices would run through a defined screen schedule, with reviewed urgent-message priority. Offline copies and permission withdrawals need a clear refresh and removal process. AI-generated future concept: Explore optional XR storytelling and Aura-assisted explanations using material its rights holders and cultural custodians have approved. Keep public warnings understandable outside XR, and carry the same release identity into every presentation. Research examples: Xibo Emergency Alert widget and CAP connector · Web Content Accessibility Guidelines 2.2	open
ECO-03	How will ferry, bus, road and accessible-travel updates give people current, traceable guidance?	AI-generated option: Begin with the published island timetable and confirmed operator notices, showing their different meanings and age. Translink currently lists island schedules without real-time data. Show confirmed cancellations and contact routes; develop alternatives through actual operator confirmation and accessible-travel checks. AI-generated future concept: Explore supervised and later autonomous mobility as a separate service interface, carrying operating permission, availability, accessibility and confirmed booking states. Model power, communications and weather dependencies before adding any vehicle to the public service offer. Research examples: Translink open data: schedules and real-time feeds · NIST AI Risk Management Framework 1.0: core functions	open
ECO-04	How will offers, supply information and requests connect residents with responsible relief operators while respecting household privacy?	AI-generated option: Keep an offer, checked available stock, a person's request, operator acceptance and completed handover as separate records. Share household details only with the agreed recipients. Connect Shared Table and other supply proposals through named custodians, consent, usable quantities and clearly confirmed participation. AI-generated future concept: Explore assistants preparing possible matches from consented needs and confirmed offers, then presenting them to the responsible operator. Future robot delivery would add its own permission and observed handover evidence before closing a request. Research examples: ODK Collect: managing draft, ready-to-send and sent forms · Solid FAQ: personal data sharing, storage and copies	open
ECO-05	What information will show that backup power and essential-service equipment are ready to use when people need them?	AI-generated option: Use a readiness record that joins connected and commissioned equipment with recent load tests, usable capacity, replenishment, access and qualified cover. Display the last confirmation and responsible person alongside measurements. Link kiosk energy settings to these observed limits and the service tasks they support. AI-generated future concept: Explore a local model that proposes times for optional AI, media and charging around measured reserves. Any equipment-control link would have separately agreed permission, protection and qualified review before actuation. Research examples: OGC SensorThings API Standard · NIST AI Risk Management Framework 1.0: core functions	open
ECO-06	How can repair, making, materials and training partnerships strengthen the kiosk's equipment and skills over time?	AI-generated option: Connect repair and learning through a task record identifying the equipment edition, fault, permitted first checks, parts, tools and qualified support. Keep compatible local spares and practised handovers. Broader making and materials projects would contribute through specific tested parts, lessons and agreed supply arrangements. AI-generated future concept: Explore a makerspace validating a replacement component and an authorised robot assisting inspection or parts movement. Compare material quality, fit, maintainability and qualified-work requirements before using a new part in an operational kiosk. Research examples: About Kolibri: offline learning on devices and local networks · Mender Artifacts: compatible, signed and resumable software editions	open
ECO-07	What hosting and stewardship arrangement would let Ready S.E.T. Co-op or another agreed host support a kiosk at a suitable site?	AI-generated option: Prepare a separate host agreement for each candidate site, covering permission, ownership, hours, access, cultural relationships, upkeep, power, costs, incident roles and exit. Ready S.E.T. Co-op's proposed role would develop through formation and agreed mandates, with each host retaining its actual responsibilities. AI-generated future concept: Explore hosts offering different services such as public information, private assistance, portable relief or training. A common record would make confirmed hours, equipment and continuity arrangements discoverable, while each additional role receives its own agreement. Research examples: Our Changing City: Wellington's public climate-adaptation digital installation · NSW Spatial Services: mapping and the Emergency Management Digital Twin	open
ECO-08	How will a shared connection register help people see the kiosk's place in the wider ecosystem and the next useful partnership?	AI-generated option: Maintain one readable connection register naming each project, current artefact, proposed exchange, owner, permission, offline fallback and acceptance evidence. Show how everyday events, media, mobility, supplies, energy, repair and optional Auras support the kiosk. Broader ambitions would connect through explicitly staged interfaces. AI-generated future concept: Explore Auras navigating an agreed service graph across the cultural node, Verse Box, Aura Genesis, P4A and the Sensorium. C-Hours recognise verified voluntary human hours with community-chosen reciprocity, no monetary equivalent, sale or transfer; money, paid work, machine time and outcomes remain separate. Research examples: NSW Spatial Services: mapping and the Emergency Management Digital Twin · RFC 5545: iCalendar	open