docs(modules): classify missing statefulness metadata #263
No reviewers
Labels
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 milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
pdurlej/platform!263
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "codex/hardening/statefulness-classification"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Canary status: missing — module metadata batch touches
modules/; fire canary before merge if operator wants full ADR-0007 enforcement. Local validation passed.Canary Context Pack
Product story
Future F2 smoke dispatches must be built from repo metadata, not memory or optimism. This PR makes every module queryable by
spec.runtime.statefulnessso stateless candidates can be selected mechanically.What changed
Added
spec.runtime.statefulnessto 49 module manifests that were missing the field.Why it changed
Pan Herbatka's corrected F1.5 dispatch found that many modules lacked statefulness metadata, making the original F2 candidate list unsafe. Hardening D now creates a classified universe for the next session.
Files touched
modules/*/module.yaml— 49 one-line metadata additionsRelevant context
prompts/codex-f1.5-hardening-f2-2026-05-13.mdHardening D, overridden by the operator-pasted Pan Herbatka correctionschema/module.schema.jsonallowsstateless,stateful, andsidecar-boundonly. The correction mentionedephemeral, but the schema does not currently accept it, so this PR does not introduce that value.Runtime evidence
Read-only evidence used:
compose/apps/compose.yamland included compose filesdocker ps --format '{{.Names}}'on RS2000docker inspectmount metadata only for relevant containers; env/secret values were not read or printedKnown constraints
statefulhere means the module owns local persistent state, writable data mounts, protocol identity, media/model state, or a dedicated backing store.statelessmay still depend on stateful upstreams, matching existing repo precedent (umami,n8n-worker).sidecar-boundis used for one-shot or profile modules whose state is materially owned by a paired primary service.Explicit out-of-scope
ephemeralRequested decision
Merge if the classifications are acceptable as the next-session F2 candidate filter foundation.
Merge blockers
ephemeralto schema first instead of using current enum valuesClassification report
agent-plane-shadow-postgres-data/statebind mount under legacy root/statebind mount for integration state/stateand/configintegration binds/stateand/configintegration binds/datavolume/datavolume and manifest data store/vault/datavolume and AOF/RDB commandsafe_session_statevolumeVerification
for f in modules/*/module.yaml; do grep -q "statefulness:" "$f" || echo "$f"; done→ no outputpythoncount after change →{'stateless': 31, 'stateful': 45, 'sidecar-bound': 4}modules/*/module.yaml→ all passedpytest control-plane/platformctl/tests/test_validate.py -q→ 6 passedSpec sources read
schema/module.schema.json— valid enum and semanticsprompts/codex-f1.5-hardening-f2-2026-05-13.md— original Hardening D contextcompose/apps/compose.yaml,compose/core/compose.yaml,compose/edge/compose.yaml— compose service/mount evidencemodules/*/module.yamlfor missing-field modules — lifecycle, runtime service, dependencies, and intentdocker psanddocker inspectmount metadata — live evidence without env/secret valuesRefs #142.