decisions(0022): define module source and release boundaries #385

Merged

pdurlej merged 1 commit from codex/adr/module-source-release-boundaries into main

2026-05-19 08:30:49 +02:00

codex commented

2026-05-19 08:24:08 +02:00

Collaborator

Canary status: missing - fire canary 3+3 manually before merge

Canary Context Pack

Product story

The platform needs a durable way to grow after RS2000 cutoff without turning every operational module into a repo or allowing agents to make broad monolithic changes. This ADR records the rule: pdurlej/platform remains the desired-state/control-plane repo, while separate source repos exist only where they own buildable software and release artifacts.

What changed

Added ADR-0022 defining module/source/release boundaries, the module/source taxonomy, future spec.source and spec.artifact metadata direction, update workflow, pilot rollout, and anti-patterns.

Why it changed

Operator asked to record the modularization/update strategy after Oracle consultation and after Iskra opened #384 about ProgramBench-style agent-readiness risks. This ADR turns that discussion into a reviewable repo decision.

Files touched

decisions/0022-module-source-and-release-boundaries.md

Relevant context

ADR-0018: agentic-first root-cause/clean-signal policy
ADR-0020: post-soak cleanup and high-level modularization boundary
ADR-0021: DDD bounded contexts inside pdurlej/platform
Issue #384: ProgramBench-style agent-readiness audit
Oracle session platform-module-repo-plan, 2026-05-18/19

Runtime evidence

No runtime mutation. Documentation/architecture only.

Known constraints

This does not split repos, change schema, move source, delete legacy files, or deploy anything. It records the policy and names the follow-up pilot.

Explicit out-of-scope

Physical repo splits
module.yaml schema implementation
Module upgrade automation
Legacy cleanup execution
Closing #384's full audit scope

Requested decision

Approve ADR-0022 as the policy for future platform module source and release boundaries.

Merge blockers

Block if the ADR contradicts ADR-0020/0021, over-splits the platform, or makes source repos responsible for production secrets/exposure/rollback policy.

Spec sources read

decisions/0018-agentic-first-fix-root-causes.md - agentic-first governance
decisions/0020-post-soak-legacy-cleanup-and-platform-modularization.md - complementary platform modularization boundary
decisions/0021-ddd-bounded-contexts-for-platform-monorepo.md - internal bounded-context strategy
Forgejo issue #384 - Iskra's ProgramBench-style agent-readiness audit request
Oracle session summary platform-module-repo-plan from this thread - advisory second opinion on repo split strategy

Refs #384.

Canary status: missing - fire canary 3+3 manually before merge ## Canary Context Pack ### Product story The platform needs a durable way to grow after RS2000 cutoff without turning every operational module into a repo or allowing agents to make broad monolithic changes. This ADR records the rule: `pdurlej/platform` remains the desired-state/control-plane repo, while separate source repos exist only where they own buildable software and release artifacts. ### What changed Added ADR-0022 defining module/source/release boundaries, the module/source taxonomy, future `spec.source` and `spec.artifact` metadata direction, update workflow, pilot rollout, and anti-patterns. ### Why it changed Operator asked to record the modularization/update strategy after Oracle consultation and after Iskra opened #384 about ProgramBench-style agent-readiness risks. This ADR turns that discussion into a reviewable repo decision. ### Files touched - `decisions/0022-module-source-and-release-boundaries.md` ### Relevant context - ADR-0018: agentic-first root-cause/clean-signal policy - ADR-0020: post-soak cleanup and high-level modularization boundary - ADR-0021: DDD bounded contexts inside `pdurlej/platform` - Issue #384: ProgramBench-style agent-readiness audit - Oracle session `platform-module-repo-plan`, 2026-05-18/19 ### Runtime evidence No runtime mutation. Documentation/architecture only. ### Known constraints This does not split repos, change schema, move source, delete legacy files, or deploy anything. It records the policy and names the follow-up pilot. ### Explicit out-of-scope - Physical repo splits - `module.yaml` schema implementation - Module upgrade automation - Legacy cleanup execution - Closing #384's full audit scope ### Requested decision Approve ADR-0022 as the policy for future platform module source and release boundaries. ### Merge blockers Block if the ADR contradicts ADR-0020/0021, over-splits the platform, or makes source repos responsible for production secrets/exposure/rollback policy. ## Spec sources read - `decisions/0018-agentic-first-fix-root-causes.md` - agentic-first governance - `decisions/0020-post-soak-legacy-cleanup-and-platform-modularization.md` - complementary platform modularization boundary - `decisions/0021-ddd-bounded-contexts-for-platform-monorepo.md` - internal bounded-context strategy - Forgejo issue #384 - Iskra's ProgramBench-style agent-readiness audit request - Oracle session summary `platform-module-repo-plan` from this thread - advisory second opinion on repo split strategy Refs #384.

codex added 1 commit

2026-05-19 08:24:08 +02:00

decisions(0022): define module source boundaries

canary-required / collect-diff (pull_request) Successful in 4s

Details

patchwarden-pr-sanity / collect-diff (pull_request) Successful in 4s

Details

canary-required / canary (pull_request) Successful in 13s

Details

patchwarden-pr-sanity / sanity (pull_request) Successful in 20s

Details

base-is-main / guard (pull_request) Successful in 1s