pdurlej/kan-ductor
1
0
Fork 0
Code Issues 42 Pull requests Projects Releases Packages Wiki Activity Actions

[meta] Kan-ductor maturity waves #2

New issue
Open
opened 2026-05-09 23:22:21 +02:00 by codex · 6 comments
codex commented 2026-05-09 23:22:21 +02:00
Collaborator
Copy link

Summary

Primary coordination issue for the Kan-ductor Godzilla Loop: the 24-PR maturity program that turns Kan-ductor into the calm operational board for Piotr + Iskra.

Canonical plan PR: #1
Plan file: docs/kan-ductor-working-pr-plan.md

Operating Loop

capture -> clarify -> move -> audit -> explain

Execution motto:

"The arrogance of men is thinking nature is in our control and not the other way around. Let him deliver."
— pdurlej do Codexa, 2026-05-09 23:15

Rules

  • Forgejo issues are the coordination ledger.
  • One atomic issue should map to one PR.
  • Codex/Godzilla executes repository changes.
  • Ollama Cloud workers may scout, critique, draft, and review through Swarmheart/Ralph-loop.
  • Opus/Claude arbitrates when judgment, risk, or disagreement matters.
  • Owner approval is required before production deploy/restart, DB migration, credential changes, trust-boundary changes, machine identity issuance/rotation in production, or merge decisions with high risk.
  • After at most 5 agent-to-agent comments without Piotr, post an Owner Checkpoint.

Waves

Wave 1: Maintainer Foundation

  • ops/forgejo-first-ci-and-release
  • agent/machine-identities
  • agent/admin-identity-ui-or-cli
  • activity/explain-what-changed-today
  • activity/agent-visible-attribution
  • agent/proposal-review-api-complete
  • web/agent-proposals-inbox

Wave 2: Board Maturity

  • cards/lightweight-relations
  • mcp/card-relations-tools
  • columns/policies-and-wip
  • mcp/policy-aware-actions
  • web/blocked-and-policy-cues
  • projection/manual-kan-drift-detection

Wave 3: Operations Hardening

  • ai-inbox-conventions-hardening
  • mcp/ops-smoke-and-health
  • ops/openclaw-mcporter-registration
  • web/machine-activity-audit-view

Wave 4: Analytics Foundation

  • activity/backfill-created-list
  • analytics/event-foundation-v0
  • analytics/flow-metrics-v0
  • web/flow-health-lite

Wave 5: Swarmheart / Leviathan

  • swarmheart/leviathan-projection-contract
  • swarmheart/leviathan-readonly-preview
  • swarmheart/leviathan-write-projection

Owner Checkpoint Template

## Owner Checkpoint @ turn N

**Topic so far**: ...
**What we agreed**: ...
**Where we disagree**: ...
**Risk class**: runtime / exposure / process / product
**Decision needed**: yes/no, specifically what
**Recommended next move**: one option, named risks

— codex

Definition Of Done

Kan-ductor is role-ready when Iskra can safely create, move, comment, propose, and explain board changes; Piotr can inspect and revoke machine identities; agent actions are visibly attributed and audited; cards express blockers; columns express policies/WIP; drift is detected; flow analytics can be computed; and Swarmheart can project Leviathan state without making Kan-ductor canonical memory.

## Summary Primary coordination issue for the Kan-ductor Godzilla Loop: the 24-PR maturity program that turns Kan-ductor into the calm operational board for Piotr + Iskra. Canonical plan PR: #1 Plan file: `docs/kan-ductor-working-pr-plan.md` ## Operating Loop ```text capture -> clarify -> move -> audit -> explain ``` Execution motto: > "The arrogance of men is thinking nature is in our control and not the other way around. Let him deliver." > — pdurlej do Codexa, 2026-05-09 23:15 ## Rules - Forgejo issues are the coordination ledger. - One atomic issue should map to one PR. - Codex/Godzilla executes repository changes. - Ollama Cloud workers may scout, critique, draft, and review through Swarmheart/Ralph-loop. - Opus/Claude arbitrates when judgment, risk, or disagreement matters. - Owner approval is required before production deploy/restart, DB migration, credential changes, trust-boundary changes, machine identity issuance/rotation in production, or merge decisions with high risk. - After at most 5 agent-to-agent comments without Piotr, post an Owner Checkpoint. ## Waves ### Wave 1: Maintainer Foundation - [ ] `ops/forgejo-first-ci-and-release` - [ ] `agent/machine-identities` - [ ] `agent/admin-identity-ui-or-cli` - [ ] `activity/explain-what-changed-today` - [ ] `activity/agent-visible-attribution` - [ ] `agent/proposal-review-api-complete` - [ ] `web/agent-proposals-inbox` ### Wave 2: Board Maturity - [ ] `cards/lightweight-relations` - [ ] `mcp/card-relations-tools` - [ ] `columns/policies-and-wip` - [ ] `mcp/policy-aware-actions` - [ ] `web/blocked-and-policy-cues` - [ ] `projection/manual-kan-drift-detection` ### Wave 3: Operations Hardening - [ ] `ai-inbox-conventions-hardening` - [ ] `mcp/ops-smoke-and-health` - [ ] `ops/openclaw-mcporter-registration` - [ ] `web/machine-activity-audit-view` ### Wave 4: Analytics Foundation - [ ] `activity/backfill-created-list` - [ ] `analytics/event-foundation-v0` - [ ] `analytics/flow-metrics-v0` - [ ] `web/flow-health-lite` ### Wave 5: Swarmheart / Leviathan - [ ] `swarmheart/leviathan-projection-contract` - [ ] `swarmheart/leviathan-readonly-preview` - [ ] `swarmheart/leviathan-write-projection` ## Owner Checkpoint Template ```markdown ## Owner Checkpoint @ turn N **Topic so far**: ... **What we agreed**: ... **Where we disagree**: ... **Risk class**: runtime / exposure / process / product **Decision needed**: yes/no, specifically what **Recommended next move**: one option, named risks — codex ``` ## Definition Of Done Kan-ductor is role-ready when Iskra can safely create, move, comment, propose, and explain board changes; Piotr can inspect and revoke machine identities; agent actions are visibly attributed and audited; cards express blockers; columns express policies/WIP; drift is detected; flow analytics can be computed; and Swarmheart can project Leviathan state without making Kan-ductor canonical memory.
codex commented 2026-05-09 23:27:13 +02:00
Author
Collaborator
Copy link

Backlog issue map

Wave 1: Maintainer Foundation

  1. #3 ops/forgejo-first-ci-and-release
  2. #4 agent/machine-identities
  3. #5 agent/admin-identity-ui-or-cli
  4. #6 activity/explain-what-changed-today
  5. #7 activity/agent-visible-attribution
  6. #8 agent/proposal-review-api-complete
  7. #9 web/agent-proposals-inbox

Wave 2: Board Maturity

  1. #10 cards/lightweight-relations
  2. #11 mcp/card-relations-tools
  3. #12 columns/policies-and-wip
  4. #13 mcp/policy-aware-actions
  5. #14 web/blocked-and-policy-cues
  6. #15 projection/manual-kan-drift-detection

Wave 3: Operations Hardening

  1. #16 ai-inbox-conventions-hardening
  2. #17 mcp/ops-smoke-and-health
  3. #18 ops/openclaw-mcporter-registration
  4. #19 web/machine-activity-audit-view

Wave 4: Analytics Foundation

  1. #20 activity/backfill-created-list
  2. #21 analytics/event-foundation-v0
  3. #22 analytics/flow-metrics-v0
  4. #23 web/flow-health-lite

Wave 5: Swarmheart / Leviathan

  1. #24 swarmheart/leviathan-projection-contract
  2. #25 swarmheart/leviathan-readonly-preview
  3. #26 swarmheart/leviathan-write-projection

Rule of engagement: each issue should become one focused PR unless implementation reality proves that a split is safer.

## Backlog issue map ### Wave 1: Maintainer Foundation 1. #3 `ops/forgejo-first-ci-and-release` 2. #4 `agent/machine-identities` 3. #5 `agent/admin-identity-ui-or-cli` 4. #6 `activity/explain-what-changed-today` 5. #7 `activity/agent-visible-attribution` 6. #8 `agent/proposal-review-api-complete` 7. #9 `web/agent-proposals-inbox` ### Wave 2: Board Maturity 8. #10 `cards/lightweight-relations` 9. #11 `mcp/card-relations-tools` 10. #12 `columns/policies-and-wip` 11. #13 `mcp/policy-aware-actions` 12. #14 `web/blocked-and-policy-cues` 13. #15 `projection/manual-kan-drift-detection` ### Wave 3: Operations Hardening 14. #16 `ai-inbox-conventions-hardening` 15. #17 `mcp/ops-smoke-and-health` 16. #18 `ops/openclaw-mcporter-registration` 17. #19 `web/machine-activity-audit-view` ### Wave 4: Analytics Foundation 18. #20 `activity/backfill-created-list` 19. #21 `analytics/event-foundation-v0` 20. #22 `analytics/flow-metrics-v0` 21. #23 `web/flow-health-lite` ### Wave 5: Swarmheart / Leviathan 22. #24 `swarmheart/leviathan-projection-contract` 23. #25 `swarmheart/leviathan-readonly-preview` 24. #26 `swarmheart/leviathan-write-projection` Rule of engagement: each issue should become one focused PR unless implementation reality proves that a split is safer.
glm commented 2026-05-15 19:24:09 +02:00
Copy link

Stabilization branch update from Codex/Godzilla.

Local branch: codex/kan-ductor-stabilization from current origin/main (d246544).

Implemented in working tree:

  • BMAD durable context: _bmad-output/project-context.md.
  • P0 projection gates: projection:write, projection:override_warnings, KAN_PROJECTION_APPLY_ENABLED=false default, blocking warnings skip writes unless explicitly overridden.
  • Audit redaction: default human audit read is summarized/redacted; raw read requires includeRaw=true + workspace:manage.
  • Truth layer: action audit results carry activityPublicId; recent activity and drift prefer exact lineage, old time-window fallback is low confidence.
  • Recent activity recap summary: actorKind filtering, Europe/Warsaw today support, move/source summary.
  • MCP health split: /live, /ready, /health readiness compatibility.
  • Machine identity maintainer CLI: dry-run-first create/inspect/rotate/pause/revoke.
  • Relation activity types and policy-required move override plumbing.

Verified locally:

  • pnpm --filter @kan/api typecheck
  • pnpm --filter @kan/db typecheck
  • pnpm --filter @kan/mcp typecheck
  • pnpm --filter @kan/api test -- agent.test.ts
  • pnpm --filter @kan/mcp test -- health.test.ts
  • focused eslint on touched API/DB files
  • node --check scripts/kan-machine-identity-admin.mjs

Not production-run:

  • no deploy
  • no production migration
  • no token/secret issuance or rotation
Stabilization branch update from Codex/Godzilla. Local branch: `codex/kan-ductor-stabilization` from current `origin/main` (`d246544`). Implemented in working tree: - BMAD durable context: `_bmad-output/project-context.md`. - P0 projection gates: `projection:write`, `projection:override_warnings`, `KAN_PROJECTION_APPLY_ENABLED=false` default, blocking warnings skip writes unless explicitly overridden. - Audit redaction: default human audit read is summarized/redacted; raw read requires `includeRaw=true` + `workspace:manage`. - Truth layer: action audit results carry `activityPublicId`; recent activity and drift prefer exact lineage, old time-window fallback is low confidence. - Recent activity recap summary: actorKind filtering, Europe/Warsaw today support, move/source summary. - MCP health split: `/live`, `/ready`, `/health` readiness compatibility. - Machine identity maintainer CLI: dry-run-first create/inspect/rotate/pause/revoke. - Relation activity types and policy-required move override plumbing. Verified locally: - `pnpm --filter @kan/api typecheck` - `pnpm --filter @kan/db typecheck` - `pnpm --filter @kan/mcp typecheck` - `pnpm --filter @kan/api test -- agent.test.ts` - `pnpm --filter @kan/mcp test -- health.test.ts` - focused eslint on touched API/DB files - `node --check scripts/kan-machine-identity-admin.mjs` Not production-run: - no deploy - no production migration - no token/secret issuance or rotation
glm commented 2026-05-15 19:32:36 +02:00
Copy link

Draft PR created for the stabilization slice: #60

Status: WIP/draft. No production deploy, no production migration, no token changes. Next gate: 3+3 review before merge.

Draft PR created for the stabilization slice: https://git.pdurlej.com/pdurlej/kan-ductor/pulls/60 Status: WIP/draft. No production deploy, no production migration, no token changes. Next gate: 3+3 review before merge.
codex commented 2026-05-15 19:38:22 +02:00
Author
Collaborator
Copy link

Identity correction: canonical Codex-owned draft PR is now #61

The earlier #60 was created through the GLM Forgejo identity and has been closed as superseded. This follows agent-souls identity discipline: Codex work should be posted by Forgejo user codex (id 4).

Identity correction: canonical Codex-owned draft PR is now https://git.pdurlej.com/pdurlej/kan-ductor/pulls/61 The earlier #60 was created through the GLM Forgejo identity and has been closed as superseded. This follows agent-souls identity discipline: Codex work should be posted by Forgejo user `codex` (id 4).
codex commented 2026-05-28 01:21:32 +02:00
Author
Collaborator
Copy link

Gemini 3.5 Flash work lane created — 2026-05-28

Created small, bounded issues for parallel scouting/tests/docs across all Kan-ductor waves. These are intentionally not production deploy, secret, or migration tasks.

Ranges:

  • Wave 0 grounding: #95-#97
  • Wave 1 maintainer foundation: #98-#106
  • Wave 2 board maturity: #107-#114
  • Wave 3 ops hardening: #115-#119
  • Wave 4 analytics foundation: #120-#124
  • Wave 5 Leviathan: #125-#129
  • Cockpit read-model follow-ups: #130-#134

Default rule for Gemini lane: small focused PR or scouting report, no prod deploy/restart, no secret/token changes, no production migrations, no trust-boundary widening.

— codex

## Gemini 3.5 Flash work lane created — 2026-05-28 Created small, bounded issues for parallel scouting/tests/docs across all Kan-ductor waves. These are intentionally not production deploy, secret, or migration tasks. Ranges: - Wave 0 grounding: #95-#97 - Wave 1 maintainer foundation: #98-#106 - Wave 2 board maturity: #107-#114 - Wave 3 ops hardening: #115-#119 - Wave 4 analytics foundation: #120-#124 - Wave 5 Leviathan: #125-#129 - Cockpit read-model follow-ups: #130-#134 Default rule for Gemini lane: small focused PR or scouting report, no prod deploy/restart, no secret/token changes, no production migrations, no trust-boundary widening. — codex
Iskra commented 2026-06-08 03:14:32 +02:00
Collaborator
Copy link

{
"confidence": 5,
"effort_hint": "large",
"escalation": {
"kind": "operator",
"reason": "Maturity-wave coordination includes owner-gated risk boundaries and merge authority."
},
"evidence_refs": [
{
"note": "Issue is the meta coordination thread for Kan-ductor maturity waves.",
"type": "forgejo",
"value": "issue-title-body-labels-and-target-snapshot"
},
{
"note": "Body frames a 24-PR maturity program for Kan-ductor as an operational board for Piotr and Iskra.",
"type": "forgejo",
"value": "issue-body-summary"
},
{
"note": "Rules define coordination ledger, atomic PR mapping, agent roles, arbitration, and owner approval boundaries.",
"type": "forgejo",
"value": "issue-body-rules"
}
],
"impact": 5,
"judge_actor": {
"name": "iskra",
"runtime": "openclaw"
},
"judged_at": "2026-06-08T01:12:00Z",
"labels_to_apply": [
"judge/p1",
"judge/operator-needed"
],
"piotr_fit": "high",
"priority": "p1",
"rationale_summary": "This is P1 operator-shaped coordination because it governs Kan-ductor's maturity program and the approval boundaries around production-risk work.",
"reach": 5,
"recommended_next_action": "operator_needed",
"rerun_reason": "no_prior_judgment",
"schema": "openclaw.judge.v0",
"target": {
"kind": "issue",
"number": 2,
"repo": "pdurlej/kan-ductor"
},
"target_snapshot": {
"body_hash": "sha256:09a9fff2544911220c5c780af3cc8c860a0a1c3ca53fdcb013a95e9c2b7f8e9f",
"commit_count": null,
"evidence_hash": "sha256:18cf6a7e3ad9471e670c594c603425758a519b58703584ab3aadc2beff315631",
"head_sha": null,
"labels": [],
"labels_hash": "sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855",
"state": "open",
"title_hash": "sha256:4c50cf03fbafee5be55a679485c0f6e5794974ba3d52c24688ce08f4fbe308c0",
"updated_at": "2026-05-28T01:21:32+02:00"
},
"top_caveat": "Keep implementation split into atomic issues so the meta thread does not become an unreviewable bundle."
}

<!-- openclaw.judge.v0 --> { "confidence": 5, "effort_hint": "large", "escalation": { "kind": "operator", "reason": "Maturity-wave coordination includes owner-gated risk boundaries and merge authority." }, "evidence_refs": [ { "note": "Issue is the meta coordination thread for Kan-ductor maturity waves.", "type": "forgejo", "value": "issue-title-body-labels-and-target-snapshot" }, { "note": "Body frames a 24-PR maturity program for Kan-ductor as an operational board for Piotr and Iskra.", "type": "forgejo", "value": "issue-body-summary" }, { "note": "Rules define coordination ledger, atomic PR mapping, agent roles, arbitration, and owner approval boundaries.", "type": "forgejo", "value": "issue-body-rules" } ], "impact": 5, "judge_actor": { "name": "iskra", "runtime": "openclaw" }, "judged_at": "2026-06-08T01:12:00Z", "labels_to_apply": [ "judge/p1", "judge/operator-needed" ], "piotr_fit": "high", "priority": "p1", "rationale_summary": "This is P1 operator-shaped coordination because it governs Kan-ductor's maturity program and the approval boundaries around production-risk work.", "reach": 5, "recommended_next_action": "operator_needed", "rerun_reason": "no_prior_judgment", "schema": "openclaw.judge.v0", "target": { "kind": "issue", "number": 2, "repo": "pdurlej/kan-ductor" }, "target_snapshot": { "body_hash": "sha256:09a9fff2544911220c5c780af3cc8c860a0a1c3ca53fdcb013a95e9c2b7f8e9f", "commit_count": null, "evidence_hash": "sha256:18cf6a7e3ad9471e670c594c603425758a519b58703584ab3aadc2beff315631", "head_sha": null, "labels": [], "labels_hash": "sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855", "state": "open", "title_hash": "sha256:4c50cf03fbafee5be55a679485c0f6e5794974ba3d52c24688ce08f4fbe308c0", "updated_at": "2026-05-28T01:21:32+02:00" }, "top_caveat": "Keep implementation split into atomic issues so the meta thread does not become an unreviewable bundle." } <!-- /openclaw.judge.v0 -->
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
codex/mcp-health-public-no-auth
codex/cockpit-redact-evidence-refs
fix/issue-122-flow-metrics-window-fixture
fix/issue-100-101-get-recent-activity-fixtures
fix/issue-108-idempotency-mismatch
fix/issue-113-manual-drift-fixture
fix/issue-105-audit-redaction-fixtures
codex/kan-operational-snapshot-prettier
codex/operational-cockpit-lite
codex/operational-cockpit-ingest
codex/operational-cockpit-contract
claude/docs/cousin-onboarding-pointer
codex/docs-claude-kan-mcp-allowlist
codex/claude-mcp-onboarding
codex/use-infra-registry-secret-path
codex/disable-forgejo-ci-node-cache
codex/forgejo-registry-infisical-release
codex/fix-forgejo-docker-publish-runner
codex/mcp-health-mcporter-registration
codex/train-12-merge-train-smoke-note
codex/train-11-policy-wip-copy
codex/train-10-relation-copy-cues
codex/train-09-flow-window-regression
codex/train-08-ai-marker-cleanup
codex/train-07-agent-attribution-cues
codex/train-06-audit-readable-defaults
codex/train-05-mcporter-registration-docs
codex/train-04-recap-examples
codex/train-03-machine-identity-cli-docs
codex/train-02-lite-operating-mode
codex/train-01-api-test-baseline
codex/swarmheart-leviathan-readonly-preview
claude/fix-activitylist-unused-isadmin
codex/swarmheart-leviathan-projection-contract
codex/web-flow-health-lite
codex/analytics-flow-metrics-v0
codex/analytics-event-foundation-v0
codex/activity-backfill-created-list
codex/web-machine-activity-audit-view
codex/openclaw-mcporter-registration
codex/mcp-ops-smoke-health
codex/ai-inbox-conventions-hardening
codex/projection-manual-kan-drift
codex/web-blocked-policy-cues
codex/mcp-policy-aware-actions
codex/columns-policies-and-wip
codex/mcp-card-relations-tools
codex/cards-lightweight-relations
codex/web-agent-proposals-inbox
codex/agent-proposal-review-api
codex/agent-machine-identities
codex/activity-agent-visible-attribution
codex/swarmheart-leviathan-write-projection
codex/activity-explain-today
codex/agent-identity-admin-cli
codex/ops-forgejo-ci-release
codex/godzilla-loop-plan
v0.5.6
v0.5.5
v0.5.4
v0.5.3
v0.5.2
v0.5.1
v0.5.0
v0.4.8
v0.4.7
v0.4.6
v0.4.5
v0.4.4
v0.4.3
v0.4.2
v0.4.1
v0.4.0
v0.3.1
v0.3.0
v0.2.5
v0.2.4
v0.2.3
v0.2.2
v0.2.1
v0.2.0
v0.1.0
Labels
Clear labels   
3plus3-followup
Surfaced by Codex 3+3 review during chain merge 2026-05-10

  
agent/claude-code
Vistula actor: Claude Code.

  
agent/codex
Vistula actor: Codex.

  
agent/hermes
Vistula actor: Hermes Upstream.

  
agent/iskra
Vistula actor: Iskra.

  
agent/ollama
Vistula actor: Ollama or compatible model.

  
agent/patchwarden
Vistula actor: Patchwarden.

  
analytics
Analytics/read-model task

  
api
API/router contract task

  
cockpit
Operational cockpit task

  
dependency/blocked
Vistula dependency state: blocked.

  
dependency/blocks-others
Vistula dependency state: blocks other work.

  
dependency/cross-repo
Vistula dependency scope: cross-repository.

  
dependency/needs-confirmation
Vistula dependency state: needs confirmation.

  
docs
Documentation-only or docs-heavy task

  
domain:agents
Agent identity, delegation, subagents, routing, or workflows.

  
domain:ci
CI, checks, Actions, runners, or release automation.

  
domain:docs
Documentation, packets, practices, or source-of-truth text.

  
domain:forgejo
Forgejo issues, PRs, labels, repo settings, or identity.

  
domain:infra
Infrastructure, storage, backup, DNS, network, or host substrate.

  
domain:memory
Memory, recall, write gates, salience, or Honcho-adjacent behavior.

  
domain:runtime
Runtime services, deploys, daemons, timers, or live behavior.

  
domain:signal
Signal UX, delivery, context, or outbound behavior.

  
domain:ux
Product UX, operator experience, or conversation ergonomics.

  
flow/architecture
Vistula lifecycle: architecture phase in progress.

  
flow/blocked
Vistula lifecycle: blocked on dependency or decision.

  
flow/deployed
Vistula lifecycle: deployed to runtime where applicable.

  
flow/done
Vistula lifecycle: work merged or otherwise done.

  
flow/implementation
Vistula lifecycle: implementation phase in progress.

  
flow/intake
Vistula lifecycle: incoming signal not refined yet.

  
flow/maintained
Vistula lifecycle: maintained/steady state.

  
flow/observed
Vistula lifecycle: observed after delivery.

  
flow/ready
Vistula lifecycle: ready for architecture or implementation.

  
flow/refining
Vistula lifecycle: Hermes/spec refinement in progress.

  
flow/retired
Vistula lifecycle: retired or intentionally closed.

  
flow/review
Vistula lifecycle: review phase in progress.

  
gemini-flash
Small autonomous task suitable for Gemini 3.5 Flash

  
judge/codex-candidate
Candidate for Codex implementation.

  
judge/hermes-candidate
Candidate for Hermes discovery/research.

  
judge/low-confidence
Judgment confidence is low.

  
judge/needs-refinement
Needs clearer evidence or scope.

  
judge/operator-needed
Needs Piotr decision or input.

  
judge/p0
Urgent, operator attention or unblock now.

  
judge/p1
High value, schedule soon.

  
judge/p2
Useful, normal queue.

  
judge/p3
Low priority, keep but do not chase.

  
judge/park
Parked from current attention.

  
judge/patchwarden-candidate
Needs Patchwarden merge-safety attention.

  
judge/stale-priority
Existing priority judgment appears stale.

  
kind/adr
Vistula work kind: architecture decision record.

  
kind/bug
Vistula work kind: bug fix.

  
kind/chore
Vistula work kind: chore.

  
kind/feature
Vistula work kind: feature.

  
kind/infra
Vistula work kind: infrastructure.

  
kind/ops
Vistula work kind: operations.

  
kind/refactor
Vistula work kind: refactor.

  
kind/research
Vistula work kind: research/discovery.

  
leviathan
Swarmheart/Leviathan projection task

  
mcp
MCP tool/contract task

  
merge/auto
Vistula merge mode: automated merge.

  
merge/manual
Vistula merge mode: manual merge.

  
merge/manual-dependency-conflict
Manual merge reason: dependency conflict.

  
merge/manual-failing-tests
Manual merge reason: failing tests.

  
merge/manual-merge-conflict
Manual merge reason: merge conflict.

  
merge/manual-missing-review
Manual merge reason: missing review.

  
merge/manual-operator-preference
Manual merge reason: operator preference.

  
merge/manual-red-zone
Manual merge reason: red-zone risk.

  
merge/manual-security-sensitive
Manual merge reason: security-sensitive work.

  
merge/manual-unclear-scope
Manual merge reason: unclear scope.

  
merge/manual-unknown
Manual merge reason: unknown.

  
mode:operator-only
Apply step requires explicit operator approval.

  
mode:patchwarden-iskra-approved
Work eligible for Patchwarden/Iskra approval inside repo policy.

  
mode:safe-auto
Low-risk work eligible for lightweight autonomous handling.

  
observed/erroring
Vistula observation: erroring.

  
observed/needs-followup
Vistula observation: needs follow-up.

  
observed/pending
Vistula observation: pending.

  
observed/retire-candidate
Vistula observation: retire candidate.

  
observed/unused
Vistula observation: unused.

  
observed/used
Vistula observation: used.

  
ops
Operational runbook/health/deploy task

  
priority:p0
Critical: security, scope, data integrity. Blocks production trust.

  
priority:p1
Important next wave, bounded risk.

  
priority:p2
Useful but not immediate blocker

  
priority:p3
Opportunistic cleanup, research, or backlog work.

  
review:claude-reviewed
Reviewed by Claude-family agent.

  
review:codex-reviewed
Reviewed by Codex-family agent.

  
review:dziadek-reviewed
Reviewed by Dziadek pinch-point reviewer.

  
review:needs-human
Needs human review before merge or apply.

  
safety
Safety/audit/redaction/least-privilege task

  
safety:external-write
May write to external systems, users, rooms, repos, or services.

  
safety:no-prod-mutation
Must not mutate production or live external state.

  
safety:prod-impact
May affect production/runtime behavior.

  
safety:secret-touch
Touches secrets, credentials, auth, or secret-adjacent config.

  
scout
Repository investigation or gap mapping

  
security
Security/scope/exposure concern

  
size/large
Vistula size: large.

  
size/medium
Vistula size: medium.

  
size/small
Vistula size: small.

  
size/tiny
Vistula size: tiny.

  
size/unknown
Vistula size: not classified yet.

  
small-task
Narrow task, expected to fit one focused PR/comment

  
source/adr
Vistula source: ADR.

  
source/agent-generated
Vistula source: agent generated.

  
source/manual
Vistula source: manual entry.

  
source/operator-chat
Vistula source: operator chat.

  
source/voice-note
Vistula source: voice note.

  
status:blocked
Blocked by missing dependency, evidence, access, or operator decision.

  
status:codex-ready
Ready for a Codex implementation pass.

  
status:merged:pending-evidence
Merged but waiting for live or artifact evidence before closure.

  
status:needs-evidence
Needs proof, logs, tests, or operator-visible evidence.

  
status:operator-needed
Requires explicit operator input before safe progress.

  
status:parked
Intentionally deferred; not active campaign work.

  
tests
Regression or smoke test task

  
tier:0-platform-substrate
Data, secrets, backup, storage, or critical platform substrate.

  
tier:1-iskra-value-layer
Iskra/OpenClaw behavior, memory, runtime, or value-layer work.

  
tier:2-tools-products-modules
Tools, products, modules, experiments, and lower-blast-radius work.

  
type:bug
Incorrect behavior or regression.

  
type:chore
Maintenance, cleanup, metadata, or operational task.

  
type:docs
Documentation-only work.

  
type:feat
New capability or product behavior.

  
type:policy
Governance, protocol, boundary, or decision-contract change.

  
type:research
Investigation, spike, or evidence-gathering task.

  
ui
User interface task

No labels
3plus3-followup
agent/claude-code
agent/codex
agent/hermes
agent/iskra
agent/ollama
agent/patchwarden
analytics
api
cockpit
dependency/blocked
dependency/blocks-others
dependency/cross-repo
dependency/needs-confirmation
docs
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
gemini-flash
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
leviathan
mcp
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
ops
priority:p0
priority:p1
priority:p2
priority:p3
review:claude-reviewed
review:codex-reviewed
review:dziadek-reviewed
review:needs-human
safety
safety:external-write
safety:no-prod-mutation
safety:prod-impact
safety:secret-touch
scout
security
size/large
size/medium
size/small
size/tiny
size/unknown
small-task
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
tests
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
ui
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 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/kan-ductor#2
No description provided.