feat(memory): #461 procedural registry v0 — schema + seed + named workflows #660
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
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
pdurlej/platform!660
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "claude/m07/procedure-registry"
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?
#461 procedural registry v0 — the L6 "how to do X, learned from success" layer per ADR-0025, completing the M07 memory trio (ADR-0025 #620 -> #460 templates #636 -> #461 registry). Two files in state/memory/: procedure-registry-schema.md (tables + no-auto-promote triggers + storage + read-path) and procedures-seed-v0.md (10 seed procedures + named workflows /review-pr //implement-feature //debug-regression //refactor-safely //ship-adr). COUSIN OWNERSHIP: claude authors claude.* + memory.; every cousin owns + authors its own procedures (candidate until confirmed). iskra. are slots awaiting Iskra — she has the self-model; claude does not define her workflows for her (AGENTS.md §3.3/§4). No table creation (runtime PR, gated). Docs-only. Tracks #461. Per ADR-0025 + #625 seam.
Patchwarden PR sanity
advisory_findings660520c0e03bd6eeb5dab30ce668b2d76bf17cdc29fmissingDeterministic findings
No deterministic findings.
Model reviewers
global-glm/glm-5.1:cloudStatus:
okVerdict:
OKmediummemory_procedure_embedding table schema undefinedprocedure-registry-schema.md line 28: '## memory_procedure_embedding Separate embedding table (per ADR-0025 §7 — embedding-space lifecycle, not inline).' — unlike memory_procedure (lines 10-18) which has full column/type/notes table, embeddglobal-deepseek/deepseek-v4-pro:cloudokOKredteam/kimi-k2.6:cloudStatus:
okVerdict:
NOT_OKhighOperator approval bypasses cousin ownership governancestate/memory/procedure-registry-schema.md 'Registration triggers' table lists 'Operator / owning-cousin approve → active', but state/memory/procedures-seed-v0.md states 'cousin-owned procedures stay candidate until the owning cousin confirmPolicy notes
PLATFORMCTL_PR_SANITY_REDTEAM_MODELis configured.