Files
SluijsensandClaude Sonnet 5.5 288b0e3838
Continuous Integration / check (pull_request) Successful in 1m50s
Continuous Integration / deploy-test (pull_request) Skipped
Continuous Integration / lighthouse (pull_request) Successful in 8m50s
Continuous Integration / deploy-production (pull_request) Skipped
Adds the AI-DLC documents of the CMS and API foundation feature
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-08 02:06:00 +01:00

2.1 KiB

Unit of Work Dependencies: cms-api-foundation

Dependency matrix

Rows depend on columns.

U1 core-site-hosting U2 andreaslop-client U3 site-delivery
U1 core-site-hosting
U2 andreaslop-client x (code: WebsiteMode, StrictSite)
U3 site-delivery x (a deployed host to deliver into and verify)

Diagram

flowchart LR
    U1["U1 core-site-hosting<br/>(CMS repo)"]
    U2["U2 andreaslop-client<br/>(CMS repo)"]
    U3["U3 site-delivery<br/>(web repo)"]
    CP1{{"Checkpoint: hand-back after U1"}}
    U1 --> CP1 --> U2 --> U3
    classDef cms fill:#63b3ed,stroke:#2b6cb0,stroke-width:1px,color:#000;
    classDef web fill:#9ae6b4,stroke:#2f855a,stroke-width:1px,color:#000;
    classDef gate fill:#f6e05e,stroke:#c05621,stroke-width:1px,color:#000;
    class U1,U2 cms;
    class U3 web;
    class CP1 gate;

Text alternative: U1 and U2 are built in the CMS repo, with a hand-back checkpoint after U1; U3 in the web repo follows U2. Blue = CMS repo, green = web repo, yellow = checkpoint.

Sequence and coordination

  • Critical path: U1, U2, U3. No parallelism between units, because each needs the previous one's result; inside U2 the admin theme can be built in parallel with the host project.
  • Checkpoint after U1: Api and Api.SlpSoftware tests green and the hand-back note delivered. U2 starts only then (the brief for both units tells the CMS session to report here).
  • Coordination points: the reserved paths and the wwwroot/web/ contract; the 404 page name (404.html) and the page files without folders (name.html); the exact CSP value (checked by U3); the host name and database of the test instance (decided in U2 Infrastructure Design).
  • External dependency for U3: the Testimonials feature merged, or overlap ruled out, because U3 touches the web CI and web/deploy/.
  • Rollback: U1 is additive and inactive by default (SpaFallback); U2 deploys a new host alongside the old test site; U3 retires the static test site only after verification, so every step can be reverted on test without data loss.