AURA
1. Executive Summary
AURA turns a passenger's face into their boarding pass — securely, privately, and under full human control.
Today, a traveler shows a passport and boarding pass five to eight times between the terminal door and the aircraft. AURA replaces those repeated manual checks with one trusted identity, created once at sign-up and reused at every step — security, boarding, and beyond.
What makes AURA different is how carefully it is built:
- It never stores your face. It stores a protected mathematical template that cannot be turned back into a photo.
- Privacy and security are designed in from day one — not added later.
- AI assists staff but never decides identity. Humans and fixed rules stay in control.
- The most sensitive data stays physically at KSIA, never in the open cloud.
We have completed the full design foundation and built a working demonstrator that proves these principles are real, not just promises. The program is now positioned to move toward a credible Terminal 6 pilot.
2. Platform Overview
What AURA is: a secure platform that lets passengers move through the airport using their verified identity, anchored to a real travel document and a real booking.
The business problem it solves
| Today's friction | AURA's outcome |
|---|---|
| Documents shown 5–8 times | Identity verified once, reused |
| Manual, inconsistent checks | Automated, consistent, faster flow |
| Lost / forged documents | Cryptographically linked identity |
| No single audit trail | Every step recorded for compliance |
| Privacy concerns about biometrics | No raw images; templates only |
Who it serves
- Passengers — a faster, smoother, less stressful journey.
- The airport (KSIA) — higher throughput, stronger security, clear compliance.
- Airlines — confidence that the right person boarded the right flight.
- Regulators — privacy-by-design, full auditability, human oversight.
First deployment: KSIA Terminal 6, supporting the passenger flow from enrollment through checkpoint to boarding.
3. The Passenger Journey (in simple terms)
A passenger — call her Layla — experiences AURA in five simple steps:
- Enroll (one time): Layla scans her passport and confirms her booking. A protected face template is created — the photo itself is discarded.
- Check-in: Her booking is linked to her identity; her journey becomes active.
- Checkpoint: She looks at a camera; in about a second she's confirmed and waved through. No documents needed.
- Boarding: One more glance confirms she matches this flight, and she boards.
- After travel: AURA honors its promises — data is cleaned up on schedule, and she can request deletion at any time.
Built-in safety net: if a check is ever uncertain, the passenger is calmly referred to a human officer — never wrongly denied, never stranded.
4. Architecture & Trust Model (high level)
AURA is built as a hybrid system — the right data in the right place.
- The "crown jewels" stay physically at KSIA — identities, face templates, audit records, and the decision engine never leave the airport.
- The cloud handles only convenience — dashboards, monitoring, and non-personal reporting.
- Systems talk in tokens, not identities. A token is a meaningless claim-ticket; only the on-prem vault can connect it back to a real person.
5. Privacy, Security & Controlled AI
This is where AURA earns trust. Every safeguard below is already designed and demonstrated.
Privacy
No raw face images — protected templates only.
Minimum data, minimum time; privacy-first deletion schedule.
Consent is central — recorded, explained, revocable.
Right to be forgotten is built in.
Security
Encrypted at rest and in transit.
Role-based access — staff see only what their job requires.
Even system admins cannot read passenger data.
Tamper-evident audit; two-person control for risky actions.
Controlled AI
AI advises; the core decides; humans stay accountable.
AI never sees raw faces — only masked/aggregated data.
A kill switch disables AI instantly; the core keeps running.
Riskiest actions locked behind founder approval gates.
6. Integration Approach & Trust Boundaries
AURA is integration-ready — designed to plug into the airport ecosystem safely.
- Connects to the essentials: the airline reservation/boarding system, the airport's flight & gate database, a passport-authentication service, staff sign-on, the decision engine, and passenger notifications.
- Every connection follows one rule: Authenticated · Encrypted · Token-based · Audited.
- A firm boundary: raw identity and biometric data never cross to outside systems. Partners coordinate using tokens only.
- Fails safe: if a partner system is unavailable, AURA degrades gracefully to a human-assisted process — it never makes an unsafe automatic decision.
7. The Demonstrator — What It Proves
We have built a working, clickable demonstrator that makes the design real and visible. It proves the program's hardest claims are achievable:
| Claim | Proven in the demonstrator |
|---|---|
| Verify once, reuse at every step | Full journey: enroll → checkpoint → boarding |
| No raw images; templates only | Only protected placeholders are created |
| Staff see only what they should | Admins are blocked from personal data |
| Every action is auditable | Tamper-evident log, integrity-checked |
| AI assists but never decides | AI labeled, masked, and kill-switchable |
| Integrations are token-based & safe | Live request/response shows tokens, not identities |
| Gates keep working in outages | All external systems down → gate still operates |
| Failures are safe, not silent | Outages route to human review, never auto-approve |
In short: the demonstrator turns the policy promises into observable behavior.
8. What Is Real Today vs Simulated in the Demo
We are deliberately transparent about the demonstrator's maturity.
| Area | Status in the demonstrator |
|---|---|
| Passenger journey logic (enroll, verify, board) | REAL demonstrator-grade |
| Role-based access control | REAL enforced on every action |
| Audit trail + integrity check | REAL demonstrator-grade |
| AI guardrails + two safe AI features | REAL no external AI model used |
| Integration connectors & trust boundary | REAL patterns · SIMULATED partners |
| Face matching / biometric engine | SIMULATED no real biometrics, no images |
| Encryption, on-prem vault, key management | DESIGNED not yet hardened in software |
| Live partner systems (airline, airport, gov) | MOCKED to the agreed contracts |
9. Pilot-Readiness View
Where we are: the foundation is complete — strategy, journey, architecture, privacy/security model, AI governance, and integration blueprint — plus a working demonstrator.
| Dimension | Status |
|---|---|
| Vision & scope | COMPLETE |
| Privacy & security design | COMPLETE |
| AI governance | COMPLETE |
| Integration design | COMPLETE |
| Working demonstrator | COMPLETE |
| Production hardening | NEXT |
| Real biometric engine | NEXT excluded this phase |
| Regulatory sign-off | NEXT |
10. Why This Matters — for Stakeholders
AURA is not a research curiosity. It addresses a concrete operational and reputational opportunity for KSIA and its partners:
- For the airport: measurably higher throughput at security and boarding, a stronger security posture, and a clean compliance story — a differentiator for Terminal 6 and a template for future terminals.
- For airlines: stronger assurance that the right passenger boards the right flight, fewer document-handling delays, and a smoother customer experience without owning the privacy risk.
- For passengers: a faster, calmer journey with a credible privacy promise — their face is never stored and they can be forgotten on request.
- For regulators: a privacy-by-design system with human oversight, full auditability, and AI that is demonstrably kept on a leash.
- For investors: a de-risked program — the hard architectural and governance questions are already answered and demonstrated, so the remaining path is hardening and integration, not invention.
11. Recommended Next Steps
A practical, staged path from demonstrator to pilot:
- Confirm the pilot scope with KSIA Terminal 6 stakeholders (gates, volumes, success measures).
- Select & integrate the biometric matching engine (separate commercial track; cost out of current scope).
- Harden the platform — production encryption, on-prem vault, key management, monitoring.
- Onboard the essential partners — airline reservation/boarding, airport flight data, passport authentication, staff sign-on.
- Complete privacy & regulatory review — consent, retention, deletion, and audit validated with authorities.
- Run a controlled pilot at a limited set of gates, with human fallback fully staffed.
- Evaluate and plan scale-up — more gates, then frequent-traveler features, then multi-terminal.
12. Closing Message
AURA is more than an idea — it is a fully designed, privacy-first identity platform with a working demonstrator that already proves its most important promises: faces are never stored, AI never decides identity, sensitive data stays at KSIA, every action is auditable, and the system keeps passengers moving even when things go wrong.
We have built the foundation the right way — putting privacy, security, and human control first — so that the path from here to a Terminal 6 pilot is about hardening and integration, not rethinking.
Prepared as the consolidating overview of the AURA program (Stages 0–6). For detail, see the full design set: Foundation Charter, Passenger Journey, System Architecture, Data & Privacy Model, Security & Access (RBAC), AI Services Layer, and Integration Readiness — plus the running demonstrator.