# Q&A Curveball Playbook: EVS-TAP & GCVWP System

### 1. Launch is in ~120 days. What is LIVE on Day 120 vs. Stage Two, and why is that split safe?
- **LIVE on Day 120 (Mandatory Regulatory MVP)**:
  - Public intake portal with GCVWP + EVS-TAP restricted branch (EN/ZH/JA/KO, 508 compliant).
  - Passport OCR + email verification + status lookup.
  - Core Adjudication Queue with automated rule triage and manual CBPO review.
  - Centralized Authorization Datastore integrated with PDS for carrier Board/No-Board messaging.
  - Real-time Recurrent Vetting against TSDB and active TECS lookouts.
  - Simplified Arrival port-of-entry verification at GUM and SPN.
- **Stage Two (Post-Launch Optimization, Days 121-180)**:
  - Advanced ML-assisted document anomaly detection for non-standard travel credentials.
  - Self-service biometric mobile re-verification for returning travelers.
  - Carrier self-service analytics portal and extended multi-lingual chatbot support.
- **Why it is safe**: Day 120 MVP fulfills 100% of the statutory Interim Final Rule requirements. The border is secure from hour zero; stage two only delivers operational efficiencies.

---

### 2. Airborne Derogatory Hit in Next 60 Minutes?
- **Answered in full in docs/60_min_airborne_hit_sop.md**:
  - Min 0-5: Recurrent vetting revokes token, ATS enriches flight/seat info, NTC receives Priority-1 alarm.
  - Min 5-15: NTC generates Target Assessment Package (TAP) and issues Immediate Action Directive (IAD) to Port Director and Watch Commander.
  - Min 15-35: Port Watch Commander deploys TTRT/SRT to arrival gate, locks biometric kiosk to neutral diversion, and notifies Carrier OCC under secure deplaning protocol.
  - Min 35-60: TTRT executes discreet jetbridge intercept upon touchdown, confirms identity via mobile biometrics, escorts target to Secondary Inspection, logs adverse action/lookout, and closes out national incident.

---

### 3. How is this not another duplicative datastore raising O&M cost?
- We **reuse CBP Passenger Common Core Services (PCCS)** rather than standing up an independent database silo.
- EVS-TAP applications are stored as native, schema-extended objects in the shared PCCS data fabric.
- Downstream systems (ATS, TVS, PDS, APIS, TECS) consume authorization states via existing enterprise APIs, reducing infrastructure footprint and lifecycle maintenance by over 65%.

---

### 4. Where exactly is AI in this design, and what happens when it is WRONG?
- **Where AI is applied**:
  - OCR passport parsing and fraud/tamper anomaly detection.
  - Name-matching fuzzy phonetics (handling transliteration variations of PRC names in Pinyin and Wade-Giles).
  - Risk triage suggestion ranking for officer review queue.
- **Human-in-the-Loop Safeguard**: AI **NEVER** issues an adverse adjudication (denial or revocation) autonomously.
- Automated processing can ONLY grant standard approvals for zero-hit applications. Any potential derogatory match or high-risk score is routed to a credentialed CBPO for manual adjudication with full explainability.

---

### 5. How do you segment and access-control the restricted-group (EVS-TAP) data, and prove it to an auditor?
- **Cryptographic Field-Level Encryption**: Restricted questionnaire responses are encrypted at rest using dedicated AWS KMS / HSM customer-managed keys.
- **Attribute-Based Access Control (ABAC)**: Only officers with specialized EVS-TAP training and specific roles can decrypt and view restricted-group responses.
- **Immutable Audit Logging**: Every single read, query, export, and modification event is written to a WORM (Write Once, Read Many) tamper-evident audit ledger with cryptographic hash chaining, verified via automated Splunk/Elastic compliance dashboards.

---

### 6. What is your ATO path, and does 120 days include the security authorization?
- **Yes, 120 days fully includes the ATO**.
- We execute via the **DHS Continuous ATO (cATO)** framework on CBP FedRAMP High Authorized Cloud infrastructure.
- Pre-authorized infrastructure as code (Terraform templates) and container baselines (DISA STIG hardened).
- Automated CI/CD DevSecOps pipeline with continuous SonarQube, Prisma Cloud, and OWASP ZAP scanning generating real-time OpenSCAP and OSCAL compliance artifacts for the CBP CISO.

---

### 7. The 508 Accessibility Story: Screen-Reader Narrative
- A vision-impaired applicant navigates using NVDA or VoiceOver.
- Page opens with `<a href="#main-content" class="sr-only focus:not-sr-only">Skip to main content</a>`.
- All form inputs utilize explicit `<label for="...">` bindings, `aria-required="true"`, and `aria-describedby="helper-text"`.
- Dynamic errors trigger an `aria-live="assertive"` polite notification region: *"Error: Passport Expiration Date is in the past. Please enter a valid date."*
- Color contrast exceeds WCAG 2.1 AA (4.5:1 for normal text, 7:1 for headers).

---

### 8. The rule changes 30 days before launch adding a new eligibility question. How much changes?
- **Zero code refactoring required**.
- The public intake portal and officer adjudication schema use a dynamic, metadata-driven JSON Form Schema engine.
- A new eligibility question is added simply by updating the JSON schema definition in the admin configuration repository, automatically propagating to the multilingual UI and validation layer within minutes.

---

### 9. Carrier PDS integration failure mode if message does not reach carrier?
- **Primary**: Real-time synchronous HTTPS/JSON REST or Type B MQ APIS/PDS message (SLA < 500ms).
- **Secondary / Fallback**: If carrier network times out (> 2.0s), the carrier gate agent uses the secure Web PDS Backup Portal.
- **Offline / Safe Degradation**: If all external connectivity fails, the traveler presents their signed digital 2D QR Travel Authorization Pass, verified offline via the gate agent's cryptographic public key scanner.

---

### 10. You are the incumbent. Convince me this is not "we already run this, trust us."
- We present **running code, validated benchmarks, and production-tested microservices** on day zero.
- We demonstrate deep institutional knowledge of CBP 3340-021B vetting directives, NTC-P operational battle rhythms, and direct integration hooks into TVS and PDS.
- We don't ask for trust; we provide automated traceability matrices, transparent SLA dashboards, and live working prototypes.