memory(C): procedural registry v0 + seed 10 procedures (workflow knowledge layer) #461
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#461
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Why this matters
Per competitive brief + GPT 5.5 Pro consultation: procedural memory (Layer 6 of 7-layer pattern) is the highest-leverage thing missing. Real example:
Procedural registry = versioned, searchable, measurable workflows that agents apply BEFORE acting. Different from runbooks (which are operator-facing documentation) — these are agent-facing reusable recipes with success/failure tracking.
What to ship
Schema (main
postgres:16.12-alpine)Markdown mirror (per claude answer Q3)
Canonical = Postgres. Mirror =
state/procedures/<slug>.mdfor git history + human-readable audit trail. Sync viaplatformctl procedure sync(when available) or pre-commit hook.Seed 10 procedures (manual, NOT auto-extracted)
Per GPT 5.5 Pro list:
iskra.handoff_to_claude.v1iskra.open_loop_mutation.v1claude.codex_packet_generation.v1claude.codex_rescue.v1codex.atomic_breath_shipping.v1codex.before_risky_change_checkpoint.v1codex.followup_extraction.v1gemini.review_packet.v1oracle.escalation_packet.v1memory.contradiction_review.v1Each gets:
state/procedures/<slug>.md(canonical for v0)created_by = 'operator-seed',status = 'active'Triggers (per GPT — manual seed first, NO auto-promotion)
candidate/activeif simplecandidatecandidatepriorityactivesuccess_countRetrieval ranking (per GPT)
Give agent 1-3 procedures, NOT 20.
Acceptance criteria
memory_procedure+memory_procedure_version+memory_procedure_event+memory_embedding_space+memory_procedure_embeddingstate/procedures/directory with 10<slug>.mdfiles (git-versioned)claude.codex_rescue.v1w top-3platformctl procedure list/get/applyminimal subcommandsstate/procedures/README.mdexplaining trigger rules + retrieval ranking + add-new-procedure protocolDependencies
memory_procedure_eventreferencestask_run_id+checkpoint_id; parallel OK but landing B first means event refs are realSpec sources
state/strategy/memory-control-plane-2026-05-24.mdstate/spike-understand-anything/07-gpt5pro-memory-architecture-brief.mdOut of scope
state/cutover/honcho-embedding-space-migration.md)Tier per ADR-0007: Medium — schema + seed + minimal CLI. Touches main Postgres (W3-tested). No production runtime risk.
Status correction (claude, from a grounded plan-review) — same as #460: OPEN, docs-only verify.
Verified live: #461 is OPEN, carries the
proposedlabel,codex_ready=false. The procedural-registry spec landed via merged PR #660 — so "verify then close" = confirm the docs/spec against #660 only, never a live-DB or runtime action.Same discipline as #460: don't close as a formality if any live-DB/runtime AC remains — re-scope the AC or leave it open behind the operator gate. Codex's logged "verified-then-closed" for #460/#461 is inaccurate; both are open.
Closing with evidence — spec deliverable landed.
state/memory/procedure-registry-schema.md+procedures-seed-v0.md(10 seed procedures + named workflows) onmainvia merged PR #660.Closing on the spec deliverable; the runtime table is owned by #688.