AskRue™ phone / tablet

Canon (seed)

• AskRue™ = one system. Website + phone/tablet need each other to function until the translator rides on the device.
• You cannot open the dining hall from the phone alone — the website starts login; the phone grants or denies.
• User-facing: say AskRue™ / the phone / the tablet. Code may keep echo, dhraecho, entitlement echo — that is plumbing, not a second brand.
• Dev target: iPhone first (Expo); tablet welcome. App Store publish is not the August Phase 1 bar.

Key on the pyramid (begin)

Pyramid = door. Phone = remote deadbolt on the same AskRue™ lock. Highway on the Bar so every hub that redirects to AskRue™ inherits elsewhere-assurance.

• One brain — challenges + grants stay on chat API; phone never holds a chat session.
• Website-first — Bar mints challenge; phone Allow/Deny or scan; grant completes on desktop only.
• Same finder — triangle mark 18px white→black→white on Bar and phone camera.
• Hub unison — Mode A fleet-gate → Bar → phone highway for free on house hubs.
• Later — translator on the device; until then this face stays pure AskRue™ gate help.
• Parent hub → AskRue™ · Continuity STATE:ASKRUE-PHONE-ONE-20260725.

Sections

• GoalsElsewhere-assurance without phone-as-chat-login.
• PartsExpo app, APIs, triangle mark, phone landing.
• PlansFinder match, deep links, pair-only copy.
• ProcessWebsite-first challenge → Allow/Deny → session on web.
• DevelopedWireframe screens + Ani UI data checklist.
• DoneHighway APIs and web phone landing that exist today.
• WaitingBlocked on gate hinge / Ani polish / publish decision.
• TodoOpen Echo work list.

Stop-lines

• Website gate / TOTP enroll / soft hinge → AskRue™ (stop).
• Phone lost / recovery → AskRue™ Contact Us (stop).
• After grant → chat session lives on web → RUEZALS chat (stop).
• Do not edit askrue-keyhole pack from Echo work (stop).
• Do not redesign fleet gate / bouncing pong from Echo work (stop).
• Overlay translate product → Dhraconyx (stop).
• Wiki meta → RUEZALS wiki (stop).