Work packages
Index of landable units for later agents. Source of rows: manifest/work-packages.tsv and manifest/owned-paths.tsv.
Give one agent one task file. That agent writes only the paths listed under Owns in that file. Shared types stay in contracts.md. HTTP paths stay in api-map.md. Class sketches stay in tech/api/ or tech/app/. Workflows and JSON stay in tech/exchange/.
Do not start feature code until the user asks. These files are the brief, not a green light.
Groups
| Group | Rule |
|---|---|
| G0 | One agent. Lands shared HTTP constants and persistence rules first. |
| G1 | Four agents may run after WP-00. Identity, two profiles, admin. |
| G2 | Booking and diagnostics may run after the G1 packages they name. |
| G3 | Encounter waits on booking. Patient results wait on diagnostics. |
| G4 | Stitch visual parity from ADR 0012. WP-11 kit and WP-12 API run first. WP-13 to WP-16 then run in parallel, one role each. |
| blocked | WP-10 owns later screen-map edits. The first map is in ADR 0010. WP-17 and WP-18 are Jira indexes (no TSV write paths). Child tickets use dual labels: module-* (area) and v1 / v2 (release). Take a Prenable v1 Jira key when the user hands it. Do not write feature code for v2 (later CCF modules) until Autorisé implémentation. See ADR 0014. |
Packages
| Id | Title | Group | Depends on | Task |
|---|---|---|---|---|
| WP-00 | Shared HTTP and persistence scaffold | G0 | WP-00-scaffold.md | |
| WP-01 | Identity session and account | G1 | WP-00 | WP-01-identity.md |
| WP-02 | Patient profile | G1 | WP-00 | WP-02-patient-profile.md |
| WP-03 | Clinician profile | G1 | WP-00 | WP-03-clinician-profile.md |
| WP-04 | Admin directory | G1 | WP-00 | WP-04-admin.md |
| WP-05 | Booking and agenda | G2 | WP-01, WP-02, WP-03 | WP-05-booking.md |
| WP-06 | Encounter notes | G3 | WP-05 | WP-06-encounter.md |
| WP-07 | Diagnostic orders and results | G2 | WP-01, WP-02 | WP-07-diagnostics.md |
| WP-08 | Patient results projection | G3 | WP-07 | WP-08-patient-results.md |
| WP-10 | Stitch screen map | blocked | export | WP-10-stitch-screen-map.md |
| WP-11 | Stitch design system and kit | G4 | WP-00 | WP-11-design-system.md |
| WP-12 | API enrichment for Stitch parity | G4 | WP-04, WP-05, WP-07 | WP-12-api-enrichment.md |
| WP-13 | Patient screens at Stitch parity | G4 | WP-11, WP-12 | WP-13-patient-screens.md |
| WP-14 | Clinician screens at Stitch parity | G4 | WP-11, WP-12 | WP-14-clinician-screens.md |
| WP-15 | Admin screens at Stitch parity | G4 | WP-11, WP-12 | WP-15-admin-screens.md |
| WP-16 | Diagnostics screens at Stitch parity | G4 | WP-11, WP-12 | WP-16-diagnostics-screens.md |
| WP-17 | Product hardening backlog | blocked | WP-17-product-hardening.md | |
| WP-18 | Platform integrations backlog | blocked | WP-18-platform-integrations.md |
Ids jump from WP-08 to WP-10. WP-15 and WP-16 write subfolders inside the WP-04 and WP-07 presentation folders. WP-12 lists edit rows in manifest/owned-paths.tsv for fields it adds to other owner packages. Account deletion and consent live on WP-01 (F-16, F-17). WP-17 indexes AFIA-15 polish tickets. WP-18 indexes AFIA-16 integrations. Agents take a Jira key, not the catalog WP alone; Owns and Décision retenue are on the ticket.
Shared files later agents must not edit
EndpointUri.java, api_config.dart, and docs/api-map.md belong to WP-00. A feature agent uses constants that WP-00 already reserved. If a path is missing, stop and add a row to manifest/api-prefixes.tsv in a WP-00 follow-up. Do not invent a path in a feature package.