Shut Up and Serve (SUAS) — Specification v0.6.0

Product: Shut Up and Serve System: SUAS Version: 0.6.0 Lifecycle: released Phase: IMPLEMENTATION_AUTHORIZED Implementation authority: RELEASED_FOR_IMPLEMENTATION Release manifest: RELEASE_MANIFEST-0.6.0.md

SUAS-specs is canonical. Three implementation repositories implement released contracts and may not redefine them from code, prototype behavior, provider behavior, deployment state, or traction. Named inventory: REPOS.md.

Product surfaces

Surface	Repository	Role
Specs	https://github.com/scrimshawlife-ctrl/SUAS-specs	Canonical released contract
Web + API	https://github.com/scrimshawlife-ctrl/suas	TypeScript Cloudflare Worker; /api/v0, /app
iOS	https://github.com/scrimshawlife-ctrl/suas-ios	Native Swift client; consumes /api/v0
Android	https://github.com/scrimshawlife-ctrl/suas-android	Native Kotlin client; consumes /api/v0

A change to the product API, Veteran journey, auth, or environment class must be considered against all three clients.

The weekend-build document HACKATHON BUILD SPECIFICATION Rev 3 (2026-08-14) is build direction, not a released SUAS product spec. Where it touches this repository, FENCE_POSTS.md, SURFACES.md, ISLANDS.md, and RIDES.md define draft contracts that may be reviewed during the event. They are not implementation authority. If Rev 3 and this released stack conflict, record the conflict as DECISION_PENDING in DECISIONS.md. Santa Clara County v0.1 remains the same consent-governed identified coordination platform already defined on main.

Start here for implementation / Fable handoff

1. REPOS.md
2. RELEASE_MANIFEST-0.6.0.md
3. HANDOFF.md
4. ENVIRONMENT.md
5. STATUS.md
6. PRODUCT.md
7. GLOSSARY.md
8. AGENTS.md
9. ARCHITECTURE.md
10. DOMAIN_MODEL.md + DATA_MODEL.md
11. API.md + APIS.md
12. TESTING.md
13. MVP_REFERENCE.md
14. domain/operations files required by the active SPEC-017 slice

Mission

Coordinate the shortest safe and consented path between a veteran's current need and an available human or material support resource.

SIGNAL → NEED → CONSENT → COORDINATION → FULFILLMENT → FOLLOW-UP → SETTLEMENT

MVP categories: FOOD, TRANSPORTATION, SHELTER, PEER_SUPPORT.

SUAS is not an EHR, diagnosis system, suicide-prediction product, automated emergency dispatcher, or MVP billing platform.

Current lifecycle

• SPEC-001 through SPEC-015: accepted
• SPEC-016: released implementation authority
• SPEC-017: recorded against pin 0.6.0 (implementation evidence; not production)
• SPEC-018: pilot/production go/no-go, still blocked
• Pilot readiness: NOT_READY
• Production readiness: NOT_READY
• All 12 readiness gates: NOT_READY

v0.4.0 releases only the D-035 gate qualifier IMPLEMENTATION_EVIDENCE_AUTHORIZED for the status-only VA OAuth path in LOCAL fixture and VA SANDBOX, solely to produce final-review evidence. D-035 itself remains DECISION_PENDING; D-016 self-attestation remains available; production, broader VA data access, and offline_access remain blocked. See D035_SANDBOX_EVIDENCE_AUTHORITY.md. v0.3.0 closes D-033 by releasing the native mobile client surface in MOBILE_SURFACE.md and opens D-034 (on-device data protection). It adds a client surface only: no domain concept, state, event, capability, or configuration variable. Device push remains FUTURE. It does not authorize production operation or application-store distribution. v0.2.0 (inherited) closes D-011 by releasing qv-001 + sv-001 in SIGNAL_SCORING.md. TEST/CI stay on SUAS_SUPPORT_SIGNAL_MODE=fixture. G-I-28 remains open. It does not authorize production operation. v0.1.6 (inherited) is a Wave A editorial hygiene patch over v0.1.5: it aligns D-015/D-016 domain wording with the already-decided v0.1 defaults, points SPEC-003 at the 0.1.4 effective-signal rule (including the two-override / chain case), and stamps leftover high-traffic draft headers as stale. It closes no D-0xx and invents no product behavior. v0.1.5 (inherited) is a D-012 safety/crisis copy decision patch: it approves the on-screen crisis copy and destinations (911 / 988) in SAFETY_COPY.md and the REQUESTED ≠ ACCEPTED ≠ DISPATCHED ≠ ARRIVED ≠ RESOLVED state-truthfulness contract; it approves copy only (no automated dispatch, no production-operating approval). v0.1.4 (inherited) is an implementation-conformance codification patch adopting accepted Bucket I gaps (P-1..P-23). v0.1.3 (inherited) is a D-018 shelter adapter decision patch: Amadeus may be implemented adapter-locally for commercial shelter search/inventory behind TemporaryShelterPort, ManualShelterAdapter remains mandatory, and production use remains blocked.

Environment and configuration

ENVIRONMENT.md is mandatory. Logical environments are LOCAL, TEST, STAGING, PRODUCTION; LOCAL/TEST/STAGING prohibit real veteran data and real external support effects. Configuration may disable more functionality but cannot enable a release-manifest UNAVAILABLE or FUTURE surface.

Required implementation provenance includes app version/commit, spec version, manifest identifier, schema/migration version where applicable, build version/time, and environment class.

Architecture doctrine

• scalable modular monolith;
• shared/persistent correctness state, not process-local truth;
• durable production-critical async work;
• persistent command idempotency distinct from event identity;
• replay-safe required Domain Event publication;
• deterministic one-winner contested operations;
• deterministic current projections while preserving history;
• provider-neutral ports and Manual/Fake adapters first;
• bounded/paginated growing APIs;
• evidence-based scale/resilience.

MVP visual authority

The existing MVP at https://suasqrf.org/app/ remains the visual/interaction reference. Preserve its action-first veteran/QRF/resource/responder/admin experience while applying the mandatory truthful/safe divergences in MVP_REFERENCE.md.

Production-unavailable surfaces

Until later decisions/evidence close, do not make operational:

• real production infrastructure or real veteran data;

• production Support Signal compute (SUAS_SUPPORT_SIGNAL_MODE stays disabled|fixture; G-I-28 remains open);

• production safety operation on real veteran data (the on-screen crisis copy/destinations are approved by D-012 in SAFETY_COPY.md, but real operation remains SPEC-018-gated and SUAS performs no automated emergency dispatch);

• real food/external peer provider adapters; real transportation bookings; and real Amadeus inventory effects, holds, reservations, or cancellations until SPEC-018 readiness. Shelter reservation also remains BLOCKED_BY_PAYMENT_ARCHITECTURE absent a documented card-free enterprise contract;

• production workload/SLO/RTO/RPO claims;

• sensitive aggregate reporting;

• unsupported compliance claims.

• device push, application-store distribution, and any real-veteran use of a native client (MOBILE_SURFACE.md §5, §8).

See RELEASE_DECISIONS-0.4.0.md, RELEASE_DECISIONS-0.3.0.md, RELEASE_DECISIONS-0.2.0.md, RELEASE_DECISIONS-0.1.5.md, RELEASE_DECISIONS-0.1.3.md, RELEASE_DECISIONS-0.1.2.md, and RELEASE_DECISIONS-0.1.0.md.

Core index

Authority/product: REPOS.md, PRODUCT.md, GLOSSARY.md, STATUS.md, VERSIONING.md, ROADMAP.md, DECISIONS.md, AGENTS.md, HANDOFF.md, ENVIRONMENT.md.

Architecture/API: ARCHITECTURE.md, DOMAIN_MODEL.md, DATA_MODEL.md, EVENT_MODEL.md, API.md, APIS.md, PROVIDER_INTEGRATIONS.md, SCALING.md, RESILIENCE.md.

Domain: AUTH.md, CONSENT.md, CHECKINS.md, SUPPORT_SIGNALS.md, SAFETY.md, SAFETY_COPY.md, TRUSTED_CIRCLE.md, CASES.md, DISPATCH.md, RESOURCES.md, REFERRALS.md, FULFILLMENT.md, FOLLOWUP.md, SETTLEMENT.md, RESPONDER_WORKFLOWS.md, NOTIFICATIONS.md.

Released Support Signal scoring: SIGNAL_SCORING.md (qv-001 + sv-001; D-011 decided by RELEASE_DECISIONS-0.2.0.md).

D-035 limited sandbox-evidence authority: D035_SANDBOX_EVIDENCE_AUTHORITY.md (gate qualifier only; D-035 remains DECISION_PENDING; no production authority).

Released client surfaces: MOBILE_SURFACE.md (native mobile client; D-033 decided by RELEASE_DECISIONS-0.3.0.md). Named implementation repos: REPOS.md. Draft implementation-binding specify/plan for the existing iOS and Android forks: D033_NATIVE_CLIENT_INTEGRATION.md, D033_NATIVE_CLIENT_PLAN.md (not a stack bump; not production authority).

Draft Rev 3 contracts (not implementation authority): FENCE_POSTS.md, SURFACES.md, ISLANDS.md, RIDES.md.

Operations/verification: MVP_REFERENCE.md, ADMIN.md, SECURITY.md, PRIVACY.md, COMPLIANCE.md, ONBOARDING.md, PILOT.md, ANALYTICS.md, TESTING.md, DEPLOYMENT.md, OPERATIONS.md, INCIDENT_RESPONSE.md.

Draft administration design (not implementation authority): ADMIN_SURFACE_DESIGN.md defines the proposed complete web console, role-specific information architecture, interaction contract, and API-gap ledger. ADMIN.md remains authority until owner release.

Next work

SPEC-017 implementation evidence is recorded for pin 0.6.0. Operator fail-closed calls: OPERATOR_CALLS_2026-09-25.md. Next stage is SPEC-018 (blocked — owner KEEP_BLOCKED on SPEC018_OWNER_LAUNCH_PACKET.md). Use HANDOFF.md as the entrypoint. A change to the product API, Veteran journey, auth, or environment class must be considered against all three clients in REPOS.md. Semantic gaps return here; they are not resolved by implementation defaults. Draft Rev 3 files are not released contracts. Do not invent chat, duty matching, dashboard formulas, or PARTIAL commands.

Skill source selection, migration and safe checks: SKILL_PROVENANCE.md.