chore(m05): build module ownership and source-of-truth matrix #558

Closed
opened 2026-05-28 01:42:59 +02:00 by codex · 0 comments
Collaborator

Scope

Create the first complete module ownership/source-of-truth matrix for platform modules.

The matrix should answer for every module:

  • module id;
  • bounded context if known;
  • desired owner repo: platform, external source repo, upstream image only, or unknown;
  • artifact source: registry image, local build, upstream release, generated config, runtime data;
  • update cadence class: manual, monthly, security-only, parked/sunset;
  • migration status: done / partial / missing / deferred.

Spec sources

  • state/roadmap/current-platform-roadmap.md § 05 - Platform modularity foundation
  • decisions/0021-* if present
  • decisions/0022-* if present
  • modules/*/module.yaml
  • Existing source/artifact metadata already present in module manifests

Acceptance criteria

  • Add one durable matrix artifact under the existing roadmap/module-catalog docs location, or a clearly named state/ artifact if that is the local convention.
  • At least 80 modules are classified or explicitly marked unknown.
  • Unknowns are grouped into follow-up candidates, not hand-waved.
  • No module runtime or compose changes.
  • uv run python -m platformctl.cli validate all --json passes if repo files changed.

Out of scope

  • Moving modules to new repos.
  • Filling every missing manifest field.
  • Runtime upgrades.

Gemini execution profile

Recommended executor: Gemini 3.5 Flash High, local repo access only.

Constraints:

  • Keep the PR atomic and boring.
  • Do not SSH, mutate runtime, edit secrets, or change live compose behavior.
  • Prefer generated tables/checks over more strategy prose.
  • If the issue is too broad, split once into 2-4 smaller issues and stop.
  • PR body must include Spec sources read.
## Scope Create the first complete module ownership/source-of-truth matrix for platform modules. The matrix should answer for every module: - module id; - bounded context if known; - desired owner repo: `platform`, external source repo, upstream image only, or unknown; - artifact source: registry image, local build, upstream release, generated config, runtime data; - update cadence class: manual, monthly, security-only, parked/sunset; - migration status: done / partial / missing / deferred. ## Spec sources - `state/roadmap/current-platform-roadmap.md` § 05 - Platform modularity foundation - `decisions/0021-*` if present - `decisions/0022-*` if present - `modules/*/module.yaml` - Existing source/artifact metadata already present in module manifests ## Acceptance criteria - Add one durable matrix artifact under the existing roadmap/module-catalog docs location, or a clearly named `state/` artifact if that is the local convention. - At least 80 modules are classified or explicitly marked `unknown`. - Unknowns are grouped into follow-up candidates, not hand-waved. - No module runtime or compose changes. - `uv run python -m platformctl.cli validate all --json` passes if repo files changed. ## Out of scope - Moving modules to new repos. - Filling every missing manifest field. - Runtime upgrades. ## Gemini execution profile Recommended executor: Gemini 3.5 Flash High, local repo access only. Constraints: - Keep the PR atomic and boring. - Do not SSH, mutate runtime, edit secrets, or change live compose behavior. - Prefer generated tables/checks over more strategy prose. - If the issue is too broad, split once into 2-4 smaller issues and stop. - PR body must include `Spec sources read`.
Sign in to join this conversation.
No labels
W6d-automerge-calibration
agent/claude-code
agent/codex
agent/hermes
agent/iskra
agent/ollama
agent/patchwarden
automerge-candidate
class/security-sensitive
cutover-gate
dependency/blocked
dependency/blocks-others
dependency/cross-repo
dependency/needs-confirmation
domain:agents
domain:ci
domain:docs
domain:forgejo
domain:infra
domain:memory
domain:runtime
domain:signal
domain:ux
flow/architecture
flow/blocked
flow/deployed
flow/done
flow/implementation
flow/intake
flow/maintained
flow/observed
flow/ready
flow/refining
flow/retired
flow/review
iterating
judge/codex-candidate
judge/hermes-candidate
judge/low-confidence
judge/needs-refinement
judge/operator-needed
judge/p0
judge/p1
judge/p2
judge/p3
judge/park
judge/patchwarden-candidate
judge/stale-priority
kind/adr
kind/bug
kind/chore
kind/feature
kind/infra
kind/ops
kind/refactor
kind/research
large-impact
merge/auto
merge/manual
merge/manual-dependency-conflict
merge/manual-failing-tests
merge/manual-merge-conflict
merge/manual-missing-review
merge/manual-operator-preference
merge/manual-red-zone
merge/manual-security-sensitive
merge/manual-unclear-scope
merge/manual-unknown
meta
mode:operator-only
mode:patchwarden-iskra-approved
mode:safe-auto
needs-operator-decision
needs-triage
not-ready
observed/erroring
observed/needs-followup
observed/pending
observed/retire-candidate
observed/unused
observed/used
operator-emotional
owner-attention
phase/02
phase/03
priority:p0
priority:p1
priority:p2
priority:p3
proposed
ready-for-agent
ready-for-operator
recovery
review:claude-reviewed
review:codex-reviewed
review:dziadek-reviewed
review:needs-human
risk/exposure
risk/process
risk/product
risk/runtime
safety:external-write
safety:no-prod-mutation
safety:prod-impact
safety:secret-touch
size/large
size/medium
size/small
size/tiny
size/unknown
source/adr
source/agent-generated
source/manual
source/operator-chat
source/voice-note
status:blocked
status:codex-ready
status:merged:pending-evidence
status:needs-evidence
status:operator-needed
status:parked
tier/full
tier/lite
tier/stacked
tier:0-platform-substrate
tier:1-iskra-value-layer
tier:2-tools-products-modules
type:bug
type:chore
type:docs
type:feat
type:policy
type:research
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pdurlej/platform#558
No description provided.