Skip to content

chore(drive): close out the system-composition project - #43

Merged
wmadden-electric merged 1 commit into
mainfrom
claude/close-hex-composition
Jul 11, 2026
Merged

chore(drive): close out the system-composition project#43
wmadden-electric merged 1 commit into
mainfrom
claude/close-hex-composition

Conversation

@wmadden-electric

Copy link
Copy Markdown
Contributor

The system-composition (hex-composition) project is complete — H1 boundary (ADR-0016), the control plane loading through prisma-app.config.ts (ADR-0017), and a reusable System + testing seam (mockService/bootstrapService), all merged and live-proven (#39).

This removes the project's transient scratch (plan, spec, slice specs) and leaves a durable completion record in the design-notes: what shipped (pointing at the ADRs, docs/design/10-domains, and skills/testing-prisma-apps), and two off-critical-path follow-ups (a ControlClient dedup; folding @prisma/alchemy into @prisma/app-cloud). Docs/.drive only — no code change.

DoD met and merged: the System boundary (ADR-0016), the control plane loading
through prisma-app.config.ts (ADR-0017), and a reusable System + testing seam
(mockService/bootstrapService), proven by unit + integration tests and a live
deploy (PR #39). The durable record lives in the ADRs, docs/design/10-domains
(system-composition, deploy-cli, testing), skills/testing-prisma-apps, and the
code; the transient scratch (plan, spec, slice specs) is removed. Two off-path
follow-ups recorded in the completion note (a ControlClient dedup; folding
@prisma/alchemy into @prisma/app-cloud). forcing-function-apps consumes the
durable ADR outputs; its cron reverse-edge question is answered by ADR-0020.

Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>
@wmadden-electric
wmadden-electric merged commit c2e6e35 into main Jul 11, 2026
12 checks passed
wmadden-electric added a commit that referenced this pull request Jul 11, 2026
Integrates #44 (pnPostgres) / #43 (hex-composition close-out). Regenerates
pnpm-lock.yaml from the merged manifests — the auto-merge left it internally
inconsistent (a dangling snapshot ref) because my branch predated main's large
dependency change, which is what failed CI's frozen install on the PR merge.

Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants