Question SW 05

SW-05 How will shared equipment keep public information, private assistance, staff work and a person's optional Aura separate?

Start here · Questions · Progress · People decide

Why this matters

A resident should be able to get private help and leave the kiosk ready for the next person, with their information still under the agreed protection.

What to bring back

Describe the separate workspaces, what each saves and how a session ends. Check screen changes, copied text, downloads, browsing history, stored records and AI context. Demonstrate that the next visitor and public display receive the intended public material while private details remain protected.

What we know so far

• PUBLIC_BOUNDARY.md
• app.js (sessionStorage and localStorage code)
• Aura_Genesis_Protocol_Game_Design_Document_V2.pdf (p.27)
• Verse_Box_Trial_Proposal_Version_1_Corrected.pdf (pp.8-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.)

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.

Provide separate public, private-visitor and staff workspaces, with a clear session exit and tested removal of temporary data. A person could keep their Aura on their own device or open a chosen temporary session. Public screens would use only material approved for publication.

Separate sessions and selective personal sharing

AI-generated adaptation of an existing pattern. Compare isolated guest sessions with a personal-device connection that shares selected records. Use Solid's selective-access approach as one reference; separately verify screen privacy, clipboard handling, downloads, speech and locally stored copies.

Research basis: Solid FAQ: personal data sharing, storage and copies · Web Content Accessibility Guidelines 2.2.

Private continuation across different doorways

AI-generated future concept. Explore a visitor-approved continuation token that moves a task from public touch screen to private phone, headset or assisted room. Show exactly what travels and expire the token without leaving a reusable public-session identity.

Research basis: Solid FAQ: personal data sharing, storage and copies.

Examples and local differences

• Solid FAQ: personal data sharing, storage and copies: AI transfer assessment: Selective access can keep a personal record separate from the application reading it. Local difference to check: A shared kiosk additionally needs physical privacy, session isolation and careful handling of any already received copies.

Evidence to bring back next

• Have a second visitor inspect history, clipboard, downloads, AI context and resumed sessions after exit and power loss.
• Test equivalent access for someone using neither an Aura nor a personal device.

People and connected choices

Who reviews: Proposed privacy lead and device software lead (unconfirmed)

Connected questions: DAT-01, SW-04

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.