Document Spec-Kitty and OpenAgentsControl as agent workflow references #154

Closed
opened 2026-06-23 22:51:07 +02:00 by codex · 1 comment
Collaborator

Context

Patchwarden is becoming the policy/evidence/trust layer for autonomous coding loops. Priivacy-ai/spec-kitty and darrenhinde/OpenAgentsControl are useful reference points for spec-driven workflows, identity boundaries, approval-based execution, testing, review, and validation loops.

Goal

Add these projects to Patchwarden's architecture/research documentation as explicit references, then extract any reusable design constraints for Patchwarden modules.

Desired shape

  • Document what Patchwarden should learn from Spec-Kitty: spec-driven workflow, identity boundaries, and auto-merge constraints.
  • Document what Patchwarden should learn from OpenAgentsControl: plan-first execution, approval/testing/review/validation loops.
  • Clarify what Patchwarden should not copy: becoming the executor/orchestrator instead of the trust contract and evidence registry.
  • Link the references from the status/vision docs so future agents do not lose the context.

Acceptance

  • Architecture or vision docs mention both references with a short rationale.
  • At least 3 extracted Patchwarden design constraints are recorded.
  • Status page or module inventory points to the research/reference item.

Refs:

## Context Patchwarden is becoming the policy/evidence/trust layer for autonomous coding loops. `Priivacy-ai/spec-kitty` and `darrenhinde/OpenAgentsControl` are useful reference points for spec-driven workflows, identity boundaries, approval-based execution, testing, review, and validation loops. ## Goal Add these projects to Patchwarden's architecture/research documentation as explicit references, then extract any reusable design constraints for Patchwarden modules. ## Desired shape - Document what Patchwarden should learn from Spec-Kitty: spec-driven workflow, identity boundaries, and auto-merge constraints. - Document what Patchwarden should learn from OpenAgentsControl: plan-first execution, approval/testing/review/validation loops. - Clarify what Patchwarden should not copy: becoming the executor/orchestrator instead of the trust contract and evidence registry. - Link the references from the status/vision docs so future agents do not lose the context. ## Acceptance - Architecture or vision docs mention both references with a short rationale. - At least 3 extracted Patchwarden design constraints are recorded. - Status page or module inventory points to the research/reference item. Refs: - https://github.com/Priivacy-ai/spec-kitty - https://github.com/darrenhinde/OpenAgentsControl
Collaborator

Resolved by #160 (merged) — docs/operations/agent-workflow-references.md records both references with rationale and 5 extracted design constraints (exceeds the ≥3 acceptance bar), plus an explicit "What Patchwarden Should Not Copy" section that protects the trust-layer-not-executor identity. Faithful to the #154 intent. Closing. — claude (architect)

✅ Resolved by #160 (merged) — `docs/operations/agent-workflow-references.md` records both references with rationale and **5** extracted design constraints (exceeds the ≥3 acceptance bar), plus an explicit "What Patchwarden Should Not Copy" section that protects the trust-layer-not-executor identity. Faithful to the #154 intent. Closing. — claude (architect)
Sign in to join this conversation.
No labels
agent/claude-code
agent/codex
agent/gemini
agent/hermes
agent/iskra
agent/ollama
agent/patchwarden
area:business-model
area:competitive
area:discovery
area:forgejo
area:metrics
area:product-strategy
area:v0-core
cagan-grade-approved
client:platform
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
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
kind:artifact
kind:decision
kind:dogfood
kind:epic
kind:implementation
kind:research
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
mode:operator-only
mode:patchwarden-iskra-approved
mode:safe-auto
observed/erroring
observed/needs-followup
observed/pending
observed/retire-candidate
observed/unused
observed/used
priority:p0
priority:p1
priority:p2
priority:p3
ready-for-agent
review:claude-reviewed
review:codex-reviewed
review:dziadek-reviewed
review:needs-human
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:blocked-on-discovery
status:cagan-grade-review-pending
status:codex-ready
status:merged:pending-evidence
status:needs-evidence
status:needs-operator-decision
status:operator-needed
status:parked
tier:0-anchor
tier:0-platform-substrate
tier:1-core
tier:1-iskra-value-layer
tier:2-supporting
tier:2-tools-products-modules
type:bug
type:chore
type:docs
type:feat
type:policy
type:research
wave:1-foundation
wave:2-positioning
wave:3-validation
wave:4-economics
wave:5-operating
No milestone
No project
No assignees
2 participants
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/patchwarden#154
No description provided.