Frozen document. Dates and status refer to its original source. Private resources and unreviewed images are unavailable.
Atlas vertical-slice proposal — owner review
Status: owner-approved, September 26, 2026. The owner confirmed the 22 slices, blocker order, parallel groups, and HITL/AFK split. This document is the to-issues source for publication; no application worker starts until the published issue packet and dispatch gates pass. The four published specifications remain unchanged.
Reading the proposal
P refers to a numbered user story in shared platform #22, C to customer journeys #23, E to employer work #24, and D to certification/promotion #25. Story ranges are inclusive. A story can appear in more than one slice where the behavior must be proven at both a shared contract and a journey boundary.
All implementation vertical slices use the tracer-bullet pattern. Each issue must deliver one narrow, independently demoable behavior through every layer that behavior actually needs: a production SPA route/form, BFF contract, authoritative persisted state, Camunda task or payment/scanner integration where applicable, and focused tests. A layer with no role in the behavior is not added for symmetry. No implementation issue may be only a database, API, UI, workflow, or test task; those are work within the owning tracer bullet. If a row proves too broad to complete and demonstrate independently, split it into smaller end-to-end paths before publication, preserving one owner and explicit blockers for each path.
Rows #1–17 and #21 are proposed implementation tracer bullets. #18 is an integrated certification gate, #19–20 are owner decision gates, and #22 is a journey-publication deliverable; none is a substitute for an end-to-end product slice. Small means roughly one bounded contract and screen, medium one journey or integration, and large a multi-state journey requiring more than one convergence check. These are relative effort guides, not calendar estimates. High reasoning is reserved for session, durable-effect, workflow, and deployment seams. HITL rows record the owner's choice or evidence and do not authorize spending or account provisioning on their own.
For the journey feature trend, tag rows #1–17 with atlas:feature when published. Count each only after closure; keep #18–22 outside the feature count because they certify, decide, deploy, or document existing behavior.
Numbered issue breakdown
| # | Proposed issue and demonstrable result | Type | Blocked by | Stories | Complexity / effort / reasoning | Parallel group |
|---|
| 1 | Sign in to a running local Atlas shell. Built SPA over loopback HTTPS reaches the BFF, Keycloak/TOTP and PostgreSQL; a seeded user signs in, signs out and sees session expiry. Compose starts the pinned local core. | AFK | None | P1, P6; D1–5 | High / large / high | F0 alone |
| 2 | Enforce personal and employer views. Same user switches contexts; server-side relationship checks filter a basic dashboard and deny another customer, employer, manager or reviewer through public routes. | AFK | 1 | P2–5, P15; C1; E1–2, E4–5 | High / medium / high | F1 alone |
| 3 | Publish and resume a bilingual form draft. Contentful source compiles to a pinned en-US/es-US release; a synthetic form renders, validates, saves, resumes and switches language without changing answers. Invalid release activation fails. | AFK | 1, 2 | P8–14, P16; D3 | High / large / high | F2 content |
| 4 | Submit and review one durable generic case. A saved form becomes one accepted operation and Camunda task; assigned reviewer action changes owner state once, while stale and replayed actions show truthful status. | AFK | 2, 3 | P17–19, P25; C28 | High / large / high | F3 alone |
| 5 | Upload and review private evidence. Customer uploads an allowed versioned file; real ClamAV scan gates availability; authorized reviewer/download and document center work; bad, oversized and unscanned files do not pass. | AFK | 2, 4 | P20–23; C26 | High / medium / high | F4 evidence |
| 6 | Complete life intake with EOI. Customer starts, saves and submits; reviewer requests EOI on the same case or approves/declines; approved coverage appears once with a safe reason and document version. | AFK | 3–5, 17 | C2–5, C27, C29 | High / medium / medium | Product A life |
| 7 | Complete Medicare supplement intake. Synthetic existing-coverage reference and effective date flow through information request and simulated enrollment; no live Medicare check is implied. | AFK | 3, 4, 17 | C6–8, C27, C29 | Medium / medium / medium | Product A Medicare |
| 8 | Decide a dental claim once. Service evidence reaches reviewer; allowed amount is bounded by claim and seeded benefit; approval consumes benefit once and invalid/excess requests get a reason. | AFK | 3–5, 17 | C12–14, C26, C29 | Medium / medium / medium | Product A dental |
| 9 | Decide and disburse disability benefit. Evidence-gated seeded claim produces a benefit decision separate from simulated payout, including missing-evidence and unknown-payment states. | AFK | 3–5, 12, 17 | C9–11, C29–30 | High / large / high | Product B disability |
| 10 | Decide and disburse long-term-care benefit. Seeded period request, evidence review, benefit decision and simulated payout have distinct statuses and recovery. | AFK | 3–5, 12, 17 | C15–17, C29–30 | High / medium / medium | Product B LTC |
| 11 | Withdraw from an annuity contract. Owner sees balance; positive in-balance amount is reserved, reviewed and disbursed once; over-balance and unknown outcomes preserve truthful available funds. | AFK | 3, 4, 12, 17 | C18–21, C29–30 | High / large / high | Product B annuity |
| 12 | Manage an account alias and collect a premium. Step-up protects synthetic account change; a seeded obligation is collected once through the simulator; failed/unknown collection stays unpaid or pending. Establish a stable payment-instruction interface for later payouts. | AFK | 2–4, 17 | P7; C22–25, C30 | High / large / high | F5 payment |
| 13 | Administer one employer's benefits. Benefits admin edits seeded membership/coverage for their employer and sees the employee result; direct cross-employer and private-field access is denied. | AFK | 2 | E3–5 | Medium / medium / medium | F2 employer |
| 14 | Request and decide continuous leave. Employee saves/submits a valid range; assigned manager approves, requests information or declines on the same case; stale/ineligible actions and withdrawal race are rejected. | AFK | 3, 4, 13, 17 | E6–12, E20–21, E23 | High / large / high | Product A leave |
| 15 | Review and decide return to work. Employee submits date/evidence; insurer reviewer gates it before manager decision; manager sees only permitted status and an on-hold path when evidence or assignee is unavailable. | AFK | 5, 13, 14, 17 | E13–17, E20–23 | High / large / high | Product B RTW |
| 16 | Show linked leave and disability without crossing roles. Employee sees both case references; manager's view omits diagnosis, claim, payout, bank and document data; leave approval never changes insurer benefit state. | AFK | 9, 14 | E18–19; P3; C11 | Medium / small / medium | Cross-case convergence |
| 17 | Recover an uncertain case operation. User sees pending/confirmed owner status after lost response, restart, duplicate delivery or uncertain Camunda transition; operator can reconcile without inventing a second effect. Reusable recovery contract precedes financial journeys. | AFK | 4 | P18–19, P24–25; C28, C30; E22; D10 | High / medium / high | F4 recovery |
| 18 | Certify the six-journey local stack. Versioned two-employer synthetic seed/reset, six success/exception pairs, cross-role denials, scanner/engine outages, accessible bilingual checks and resource samples run through the built SPA on Mac loopback HTTPS. Publish exact redacted evidence and gaps. | AFK | 5–16 | D6–12, D20; P24 | High / large / high | Local convergence |
| 19 | Set timing thresholds from measured baseline. Owner reviews cold start, reads, acknowledgements, 10 MiB scan, full-demo and resource measurements from #18, then records numerical pass/fail targets or a follow-up measurement request. | HITL | 18 | D12–13 | Medium / small / medium | Owner gate |
| 20 | Choose hosted provider and budget. Check current static-host/VPS eligibility, size, cost and account access; owner selects a supported plan before any purchase or credential setup. | HITL | None | D19 | Medium / small / medium | Owner gate; may run during product work |
| 21 | Promote and verify the hosted Atlas route. After local certification and provider choice, deploy the same contracts/content/process versions to hosted UI and private VPS services; prove cookies, callbacks, CSRF, uploads, persistence, backup/restore, security denials and representative success/exception through public HTTPS. | AFK | 18–20 | D14–18, D20 | High / large / high | Hosted convergence |
| 22 | Publish the final journey film and evidence index. Link fixed repository snapshots, dates, transcript-derived wall time/tokens/model settings, decisions, local and hosted results, synthetic demo footage and known limits in a short narrated artifact. | AFK | 21 | Journey archive request; D20 | Medium / medium / low | Documentation convergence |
Dependency and ownership rules for dispatch
Foundation #1–4 stabilizes the session, relationship, bilingual release and case-operation contracts. #5 and #17 can run together after #4 because evidence storage/scanning and operation recovery own separate contracts. #3 and #13 may run together after #2 if the employer slice consumes the existing context API without changing it. Product A and Product B rows are candidate parallel sets, not fixed calendar waves: dispatch only when listed blockers are closed and their handoffs agree. Up to three disjoint product owners may work concurrently. At most two high-reasoning workers touch shared runtime or architecture at once. The orchestrator alone integrates shared navigation, seed manifest and map updates.
| Ownership | Allowed conceptual modules | Forbidden scope |
|---|
| #1–2, shared runtime/security | Ingress, sessions, identity adapter, role/relationship projections, basic shell | Product rules, payment settlement, employer leave decisions |
| #3, content/forms | Contentful compiler, release manifest, generic renderer and draft contract | Executable CMS actions, product underwriting, identity policy |
| #4 and #17, case/workflow | Operation receipt, owner outbox, Camunda correlation, task contract, recovery status | Product decision rules, payment amounts, evidence bytes |
| #5, evidence | Quarantine, scanner, version metadata, authorized transfer and document view | Contentful binary storage, claim approval, payment |
| #6–11, product journeys | One named product's owner/process/form/screen and focused tests | Other products' ledger/rules; shared session/form/payment contracts unless a blocker handoff requests change |
| #12, payments | Alias, obligation, simulator instruction, reconciliation and premium screen | Real ACH, annuity contract balance, disability benefit decision |
| #13–16, employer | Employer membership, leave, RTW and cross-case projections in named rows | Insurer claim decision, medical/EOI/banking visibility, manager impersonation |
| #18–22, convergence | Integrated evidence, measured targets, provider choice, hosted configuration, journey archive | Unreviewed product-policy changes or purchase without owner action |
Before publishing each implementation issue, verify that its acceptance criteria name the user-visible entry point, the authoritative outcome and relevant integration boundary, plus a focused end-to-end demonstration of success and at least one material denial, failure or recovery path. Each published issue will copy its exact blockers, minimum context (only relevant accepted ADRs/contracts and blocker handoffs), owned interface, forbidden scope, focused test responsibility and the structured handoff in agent orchestration. Workers run slice-level tests and touched-package checks. The master runs affected cross-module checks at wave convergence and the complete local and hosted gates. Any shared interface change returns to its owner before dependent work proceeds. No parent specification is closed or modified by issue publication.
Owner review record
The owner approved the proposed granularity, blockers, parallel groups, and HITL/AFK split as written on September 26, 2026. No row was split or merged. to-issues published the 22 issues in blocker order, with 65 native GitHub dependencies. The dispatch gate still verifies each worker packet before implementation starts.