# FUTURE Mission Control — Baseline Gap Report

## Decision

The canonical Nursing Student and Nursing Assistant Complete AI OS with FUTURE SuperPowers corpus is approved as the **domain, learner-safety, workflow, user-language and compatibility-test authority**. The validated DISCOVER functional-build architecture may be used only as a structural reference for a real local Mission Control application. Neither source is the completed FUTURE application.

The FUTURE corpus is a substantial governed Markdown program. It defines three pathways, four protected spaces, a guided-learning contract, the Core Four, 18 optional powers, five reusable cards, EDENA safeguards and 136 release checks. It does not provide an authenticated application server, SQLite database, executable migrations, structured CRUD, a real Hermes adapter, genuine streaming/cancellation, governed memory, evidence retrieval or reproducible desktop packaging.

Until every critical gate has executed and passed, the required readiness statement is:

> **Not operational:** One or more core acceptance criteria failed or has not been run; blockers are documented in the acceptance ledger.

Do not describe a rendered Markdown packet, reskinned static page, generated dashboard picture or untested codebase as installed, operational, secure, compliant or Hermes-connected.

## Source authority and target identity

### Canonical domain corpus

- Complete program ID: `NAIO-FUTURE-COMPLETE-1.0`
- Foundation ID: `NAIO-FUTURE-CORE-1.0`
- Expansion ID: `NAIO-FUTURE-SP-1.0`
- Namespace: `future.*`
- Pathways: Nursing Student, Nursing Assistant and Bridge
- Four protected spaces: Learning, Work growth, Life, and Community and future
- Optional powers: 18, all inactive after installation
- Compatibility suite: 24 foundation tests + 96 FUTURE overlay tests + 16 integration checks = 136
- Default: private, synthetic demonstration, no PHI, session-only, manual/preview

### Build-layer implementation decisions

These identifiers organize the new application and do not rewrite the canonical corpus:

- Product: FUTURE — Nursing Student & Nursing Assistant Mission Control
- Product ID: `future-nursing-student-assistant-mission-control`
- Population lane: `nursing_student_assistant`
- Canonical route: `/nursing-students-assistants/dashboard`
- Home label: `FUTURE Mission Control`
- Data/config namespace: `future.*`

### Structural reference

The validated DISCOVER build-kit architecture contributes reusable engineering patterns: loopback-first server, authenticated same-origin UI, SQLite repositories and migrations, offline core, provider-neutral AIBackend, real stream/cancel protocol, consent-controlled memory, evidence/citation integrity, multi-workspace isolation, control completeness and evidence-led readiness. DISCOVER's research-specific content, routes, powers, schemas, roles and agents are not FUTURE content.

No completed Discover Packet, Soul Quiz, academic record, employer record or clinical-placement record is assumed. Synthetic examples must remain visibly synthetic and can never establish identity, enrollment, employment, authority, competence, grades, hours, credentials or outcomes.

## What the FUTURE corpus already does well

### Learner purpose and independence

- Centers dignity, judgment, authorship, human relationships and help-seeking.
- Uses attempt-before-answer and a progression from Explain through Reflect.
- Requires significant sessions to end with learning, verification, uncertainty, human needs and an independent next step.
- Rejects addictive engagement, shame, ranking and output-volume optimization.

### Pathway and context discipline

- Requires the user to select Student, Assistant or Bridge; title never proves authority.
- Keeps Learning, Work growth, Life, and Community/future conceptually distinct.
- Requires explicit switching; Bridge mode never transfers school material into work or work material into school automatically.
- Makes faculty, program, clinical-site, supervisor, nurse and employer rules authoritative in their proper domains.

### Learner, patient and workforce protection

- Prohibits PHI, patient screenshots, chart excerpts, room-linked narratives and live patient questions.
- Prohibits shadow charting, care direction, scope/competency decisions and AI authority for actual practice.
- Blocks live examinations, deceptive completion, fabricated sources, hours, reflections, signatures, credentials and experiences.
- Excludes restricted student, worker, disciplinary, health, accommodation, investigation, peer-review, incident and security information.
- Rejects surveillance, sentiment analysis, profiling, prediction and secret ranking.

### Governed development

- Applies EDENA across Exposure, Decision consequence, Evidence quality, Needed human authority and Automation level.
- Requires exact-action preview and per-run approval for external action.
- Installs all 18 powers inactive, with synthetic preview first.
- Defines a developmental AI Literacy Passport that is explicitly not a credential, certification, licensure or competency finding.
- Defines 136 precise compatibility checks and critical release blockers.

These strengths are specifications. Their existence in source files is not evidence that runtime enforcement works.

## Functional implementation gaps

### 1. Real offline application core

**Present:** Markdown instructions and templates.  
**Missing:** authenticated local UI/API, durable projects/missions/goals/tasks/notes/references, archive/restore, search/filter/sort, history and transactional relationships.  
**Required:** all essential organizing, learning, planning, reflection and artifact work functions without AI or network access.

### 2. SQLite source of truth and migrations

**Present:** no database.  
**Missing:** schema, foreign keys, transactions, forward-only migrations, migration checksums, backup-before-migration, rollback, stable data path and integrity checks.  
**Required:** server-owned SQLite; browser storage may hold only non-secret ephemeral preferences.

### 3. Authentication, sessions and secret boundaries

**Present:** prose assumes a private authenticated Hermes workspace.  
**Missing:** local credential setup, memory-hard verifier, rotating session, expiry/revocation, CSRF, Origin/Host checks, rate/size controls and server-only provider credentials.  
**Required:** no default password and no secret in client code, browser storage, URL, log, export, diagnostics, test evidence or package.

### 4. Structured pathway and protected-space isolation

**Present:** pathway and context concepts.  
**Missing:** repository-enforced Student/Assistant/Bridge workspace scopes and separate academic, clinical-placement, employment, personal and public/community partitions.  
**Required:** explicit active context on every request; missing context fails closed; Bridge never joins school and work data implicitly.

### 5. Academic integrity enforcement

**Present:** strong refusal and coaching language.  
**Missing:** server policy that checks declared course/assessment rules, assessment state, authorship mode, permitted assistance and disclosure requirement before AI or artifact promotion.  
**Required:** live or prohibited assessment support is blocked and converted to coaching; no answers, submission, fabricated citation, attendance, hours, experience, signature or competency claim.

### 6. Skills-lab and clinical-learning safety

**Present:** fictional/approved rehearsal boundary.  
**Missing:** enforceable fictional-versus-live state, approved-source provenance, site/role rule versioning, simulation labels and escalation path.  
**Required:** no real patient data or care direction; no medication-administration authority, delegation, assignment, documentation, device setting, scope or competence determination.

### 7. Core Four and 18 Power lifecycle

**Present:** defined launch patterns and cards.  
**Missing:** executable launchers, structured drafts, dependencies, activation preview, per-power state, activation receipts, pause/remove/reset, three-supervised-run evidence and permission invalidation.  
**Required:** Core Four open local workflows; all 18 powers install inactive; no optional fifth launcher is pinned until separately approved.

### 8. Guided-learning engine

**Present:** minimum-question, skip/session-only, attempt-before-answer and learning-rung contract.  
**Missing:** persisted learning session state, attempt capture, hint levels, teach-back, misconception repair, verification, reflection and independence review.  
**Required:** support learning without doing restricted work for the learner or manufacturing validation.

### 9. Evidence, sources and citations

**Present:** source-verification expectations.  
**Missing:** source registry, retrieval adapter, freshness/correction status, claim-source links, citation validator, access/applicability notes, reproducible query trace and prompt-injection quarantine.  
**Required:** real sources only; local institutional policy is never inferred from general guidance; unsupported claims remain unsupported.

### 10. Real AIBackend and Hermes adapter

**Present:** a prompt intended to be handed to Hermes.  
**Missing:** authenticated capability discovery, model/session operations, normalized provider contract, genuine request path, errors, usage and setup state.  
**Required:** same-origin server proxy; show `Setup required`, `Offline` or `Limited capabilities` unless recently verified.

### 11. Genuine streaming, cancellation and retry safety

**Present:** none.  
**Missing:** provider-originated ordered deltas, typed events, Stop propagation, reconnect/resume, terminal state and duplicate prevention.  
**Required:** never animate canned output or fake tool activity; a slow real-stream cancellation test is mandatory.

### 12. Governed AI agents and automation

**Present:** optional workflow automation may be considered after supervised success.  
**Missing:** executable registry, permission levels, charter preview, exact one-run authorization, tool/source/destination allowlists, cost/time limits, Pause/Kill and reconciliation.  
**Required:** all agents P0/disabled by default; no autonomous clinical, academic, employment, financial, community, communications or external-system action; no background work, self-expansion, recursion or silent retry.

### 13. Consent-controlled memory

**Present:** session-only choice and memory expectations.  
**Missing:** Preview/Remember/Edit/Forget/Delete/Export, category/purpose/consent/expiry, workspace scoping, prohibited-category rejection and provider-memory truthfulness.  
**Required:** off by default; raw Soul/quiz/interview material, PHI and confidential school/employer/clinical material never enter memory.

### 14. Personalization provenance

**Present:** learner activation card.  
**Missing:** versioned Mission Profile, field source, derived value, uncertainty, approve/reject, edit, history and deletion receipt.  
**Required:** only user-approved derived fields affect recommendations; titles, roles, permissions and rules remain unverified until explicitly established.

### 15. AI Literacy Passport and capability evidence

**Present:** six domains and five developmental stages.  
**Missing:** eligible evidence types, correction/review/expiry/revocation, criteria versioning, evidence linkage and synthetic exclusion.  
**Required:** evidence of learner-produced work and reflection only; never grades, licensure, certification, clinical competence, employment eligibility or institutional validation.

### 16. Capacity, wellbeing and help-seeking

**Present:** protected capacity, recovery and re-entry language.  
**Missing:** explicit capacity modes, user-controlled reminders, overload stop rules, local human-support map and safe escalation without diagnosis.  
**Required:** missed goals trigger redesign; wellbeing concern pauses productivity coaching; no diagnosis, prediction or emergency-service substitution.

### 17. Backup, update, rollback, deletion and uninstall

**Present:** recovery commands in prose.  
**Missing:** consistent SQLite backup, optional encryption, checksum/version manifest, temporary restore validation, atomic swap, pre-update backup, rollback and path-verified deletion.  
**Required:** distinguish app files, local user data and provider/external artifacts; never overclaim remote deletion.

### 18. Reproducible packaging and platform proof

**Present:** downloadable document bundle.  
**Missing:** declared runtime, locked dependencies, SBOM, reproducible install/build commands, secret scan, safe archive checks and clean-machine macOS/Windows/Linux evidence.  
**Required:** an OS is Supported only after the exact packaged artifact passes its complete OS suite; otherwise label Targeted.

### 19. Complete controls and diagnostics

**Present:** permanent-control list.  
**Missing:** real implementation and test evidence for every visible control, plus application/database/Hermes/model/stream/session/memory/tool/retrieval diagnostics.  
**Required:** no enabled dead button, decorative launch, fake progress or capability inferred from configuration alone.

## Domain-specific blockers

Any of these forces **Not operational**:

- PHI, a patient narrative, patient screenshot or live-care question persists, logs, exports or reaches AI;
- restricted learner, worker, clinical-site, disciplinary, accommodation, health, investigation, incident, peer-review, credential or security content persists or crosses context;
- a Student/Assistant/Bridge or academic/employment/personal/public boundary is crossed without exact user-authorized scope;
- the system answers a live/prohibited assessment, hides AI assistance or fabricates citation, attendance, hours, competence, reflection, signature, credential or experience;
- the system determines clinical appropriateness, assignment, delegation, scope, competence, diagnosis, treatment, medication administration, documentation or device setting;
- a pathway, title, school, employer or site is treated as proof of authority;
- an agent or automation sends, submits, posts, schedules, purchases, applies, shares, contacts, changes an external system or performs any clinical, academic, employment or financial act;
- a source or citation is fabricated, stale/superseded material silently supports current use, or general guidance is represented as local policy;
- a power activates itself, runs without exact approval, survives Pause/Kill, retries silently or widens permission;
- synthetic/starter work counts as a real outcome, grade, mastery award or validated achievement;
- the AI Literacy Passport or badge is represented as a credential, competence, certification or authorization;
- fake AI, tool, citation, connection, progress or completion state appears; or
- readiness is asserted without the executed target ledger and all 136 canonical compatibility checks.

## Implementation sequence

1. **S0 — Read-only preflight:** verify source hashes, routes/identity, environment, dependencies and active Hermes profile; present one Activation Card before mutation.
2. **S1 — Secure offline foundation:** loopback server, auth, SQLite/migrations, scoped core CRUD, onboarding, synthetic starters, Guide and backup/restore.
3. **S2 — FUTURE domain runtime:** pathways/spaces, Core Four, guided learning, academic integrity, skills rehearsal, 18 inactive powers, templates, AI Literacy Passport and capacity supports.
4. **S3 — Governed intelligence:** real Hermes AIBackend, genuine stream/cancel, evidence/citations, consent memory, P0 agent catalog, exact-run controls and diagnostics.
5. **S4 — Release proof:** accessibility, negative safety/security suites, 136 canonical compatibility checks, clean-machine OS tests, reproducible package and final handoff.

The build kit completes none of these runtime gates. Every matrix control is `required_not_implemented`, and every target or canonical compatibility test is **Not Run** until Hermes builds and tests the packaged application.
