pdurlej/platform

Fork 0

chore(vistula): dogfood labels on 5-10 pilot issues after v0 merge #537

New issue

Closed

opened 2026-05-28 01:13:28 +02:00 by codex · 4 comments

codex commented

2026-05-28 01:13:28 +02:00

Collaborator

Scope

After PR #532 lands, dogfood Vistula on a small pilot set of real issues.

The goal is to prove labels/reporting before adding issue-label writers or comment writers.

Spec sources

docs/vistula/13-project-history.md
runbooks/vistula.md
docs/vistula/11-v0-implementation-plan.md
PR #532

Extracted context

From Vistula history:

Current recommendation: pause infrastructure work after label bootstrap and dogfood 5-10 real flows.

From live validation:

Repository label taxonomy exists, but current live issues do not yet use Vistula flow/kind/size labels.

Acceptance criteria

Pick 5-10 low-risk pilot issues across platform/patchwarden/iskra-openclaw.
Add a proposed label plan first; do not mutate labels until approved by operator or Iskra flow.
If label mutation is performed later, record before/after counts and rerun Vistula report.
No issue comments unless separately approved.
No automation writer added.

Out of scope

Adding Vistula issue/comment writers.
Changing PR merge policy.
Storing raw voice transcripts.

Agent notes

Recommended executor: Gemini 3.5 Flash local.

Rules:

Keep the PR atomic.
Do not mutate production runtime unless the issue explicitly says so.
Do not create new planning docs if a short status/update file or issue comment is enough.
Use Polish for operator-facing summaries; English for code/PR body.
PR body must include Spec sources read.

## Scope After PR #532 lands, dogfood Vistula on a small pilot set of real issues. The goal is to prove labels/reporting before adding issue-label writers or comment writers. ## Spec sources - `docs/vistula/13-project-history.md` - `runbooks/vistula.md` - `docs/vistula/11-v0-implementation-plan.md` - PR #532 ## Extracted context From Vistula history: > Current recommendation: pause infrastructure work after label bootstrap and dogfood 5-10 real flows. From live validation: > Repository label taxonomy exists, but current live issues do not yet use Vistula flow/kind/size labels. ## Acceptance criteria - Pick 5-10 low-risk pilot issues across platform/patchwarden/iskra-openclaw. - Add a proposed label plan first; do not mutate labels until approved by operator or Iskra flow. - If label mutation is performed later, record before/after counts and rerun Vistula report. - No issue comments unless separately approved. - No automation writer added. ## Out of scope - Adding Vistula issue/comment writers. - Changing PR merge policy. - Storing raw voice transcripts. ## Agent notes Recommended executor: Gemini 3.5 Flash local. Rules: - Keep the PR atomic. - Do not mutate production runtime unless the issue explicitly says so. - Do not create new planning docs if a short status/update file or issue comment is enough. - Use Polish for operator-facing summaries; English for code/PR body. - PR body must include `Spec sources read`.

codex added this to the 06 - Agent execution and CI governance milestone

2026-05-28 01:13:28 +02:00

codex added the

labels

2026-05-28 01:13:28 +02:00

codex referenced this issue

2026-05-29 16:59:57 +02:00

chore(w9): milestone archaeology packet for stale open issues #535

codex commented

2026-06-02 23:46:03 +02:00

Author

Collaborator

Proposed Vistula pilot label plan — no mutations yet

Scope follows this issue exactly: prove the taxonomy on 5-10 low-risk real issues before adding any writer/automation. This comment is the proposed plan only. No labels were changed. No issue comments were added outside #537.

Read-only checks

Repos inspected: platform, patchwarden, iskra-openclaw.
Label taxonomy availability: patchwarden and iskra-openclaw have the needed pilot labels; platform has all needed pilot labels for the selected platform issues.
Avoided: runtime/destructive/operator-emotional/security-sensitive pilot items.

Proposed pilot set

Repo	Issue	Current shape	Proposed Vistula labels to add	Why this is low-risk
`platform`	#698	`agent/codex`, `priority:p2`, `status:codex-ready`	`flow/ready`, `kind/ops`, `size/medium`, `source/agent-generated`	Improvement/backup planning item; useful to test M10 routing without touching runtime.
`platform`	#608	`kind/ops`, `priority:p3`, `status:parked`	`flow/intake`, `size/small`, `source/operator-chat`	Parked maintenance planning; label-only classification, no execution.
`patchwarden`	#64	already has `flow/ready`, `kind/chore`, `size/small`, `agent/gemini`	`source/agent-generated`	Already taxonomy-shaped; good control sample for report output.
`patchwarden`	#63	already has `flow/ready`, `kind/feature`, `size/medium`, `agent/gemini`	`source/agent-generated`	Feature implementation candidate; safe to compare with #64/#62.
`patchwarden`	#62	has `kind:implementation` legacy-style label	`kind/feature`, `source/agent-generated`	Tests taxonomy compatibility without removing legacy labels.
`iskra-openclaw`	#377	`codex-ready`, `kind/feature`, `operator-needed`, `safety:no-prod-mutation`, `size/small`	`flow/ready`, `source/operator-chat`, `agent/codex`	Small no-prod-mutation feature; good OpenClaw pilot.
`iskra-openclaw`	#375	`codex-ready`, `kind/ops`, `operator-needed`, `safety:no-prod-mutation`, `size/small`	`flow/ready`, `source/operator-chat`, `agent/codex`	Small ops smoke; safe label-only pilot.
`iskra-openclaw`	#374	`codex-ready`, `kind/ops`, `operator-needed`, `safety:no-prod-mutation`, `size/small`	`flow/ready`, `source/operator-chat`, `agent/codex`	Small ops setup/digest item; safe label-only pilot.

Mutation rules for the next step

If approved, the apply step should:

add only the labels listed above;
not remove or rename any existing labels, including legacy kind:* labels;
not add comments to the pilot issues;
not create a label/comment writer;
record before/after label counts here on #537;
rerun the Vistula report/export afterward if available.

Approval phrase

To apply this exact label-only pilot, use:

vistula-dogfood-label-plan-537-approved

Without that phrase, this issue should stay open as “plan posted, waiting for label-application approval”.

## Proposed Vistula pilot label plan — no mutations yet Scope follows this issue exactly: prove the taxonomy on 5-10 low-risk real issues before adding any writer/automation. This comment is the proposed plan only. No labels were changed. No issue comments were added outside #537. ### Read-only checks - Repos inspected: `platform`, `patchwarden`, `iskra-openclaw`. - Label taxonomy availability: `patchwarden` and `iskra-openclaw` have the needed pilot labels; `platform` has all needed pilot labels for the selected platform issues. - Avoided: runtime/destructive/operator-emotional/security-sensitive pilot items. ### Proposed pilot set | Repo | Issue | Current shape | Proposed Vistula labels to add | Why this is low-risk | |---|---:|---|---|---| | `platform` | #698 | `agent/codex`, `priority:p2`, `status:codex-ready` | `flow/ready`, `kind/ops`, `size/medium`, `source/agent-generated` | Improvement/backup planning item; useful to test M10 routing without touching runtime. | | `platform` | #608 | `kind/ops`, `priority:p3`, `status:parked` | `flow/intake`, `size/small`, `source/operator-chat` | Parked maintenance planning; label-only classification, no execution. | | `patchwarden` | #64 | already has `flow/ready`, `kind/chore`, `size/small`, `agent/gemini` | `source/agent-generated` | Already taxonomy-shaped; good control sample for report output. | | `patchwarden` | #63 | already has `flow/ready`, `kind/feature`, `size/medium`, `agent/gemini` | `source/agent-generated` | Feature implementation candidate; safe to compare with #64/#62. | | `patchwarden` | #62 | has `kind:implementation` legacy-style label | `kind/feature`, `source/agent-generated` | Tests taxonomy compatibility without removing legacy labels. | | `iskra-openclaw` | #377 | `codex-ready`, `kind/feature`, `operator-needed`, `safety:no-prod-mutation`, `size/small` | `flow/ready`, `source/operator-chat`, `agent/codex` | Small no-prod-mutation feature; good OpenClaw pilot. | | `iskra-openclaw` | #375 | `codex-ready`, `kind/ops`, `operator-needed`, `safety:no-prod-mutation`, `size/small` | `flow/ready`, `source/operator-chat`, `agent/codex` | Small ops smoke; safe label-only pilot. | | `iskra-openclaw` | #374 | `codex-ready`, `kind/ops`, `operator-needed`, `safety:no-prod-mutation`, `size/small` | `flow/ready`, `source/operator-chat`, `agent/codex` | Small ops setup/digest item; safe label-only pilot. | ### Mutation rules for the next step If approved, the apply step should: - add only the labels listed above; - not remove or rename any existing labels, including legacy `kind:*` labels; - not add comments to the pilot issues; - not create a label/comment writer; - record before/after label counts here on #537; - rerun the Vistula report/export afterward if available. ### Approval phrase To apply this exact label-only pilot, use: `vistula-dogfood-label-plan-537-approved` Without that phrase, this issue should stay open as “plan posted, waiting for label-application approval”.

codex added

owner-attention

and removed

ready-for-agent

labels

2026-06-02 23:47:40 +02:00

codex commented

2026-06-04 19:39:20 +02:00

Author

Collaborator

M06 closeout cleanup by codex: moving this Vistula dogfood pilot from M06 to M10 Improvements. Vistula v0 infra is merged; dogfooding remains useful follow-up work, not an active M06 blocker.

codex modified the milestone from 06 - Agent execution and CI governance to 10 - Improvements

2026-06-04 19:39:20 +02:00

Iskra commented

2026-06-10 03:03:17 +02:00

Collaborator

{
"confidence": 5,
"effort_hint": "small",
"escalation": {
"kind": "operator",
"reason": "Pilot label mutation needs explicit approval before changing live issue metadata."
},
"evidence_refs": [
{
"note": "Issue proposes dogfooding Vistula labels on a small pilot set after v0 merge.",
"type": "forgejo",
"value": "issue-title-body-labels-and-target-snapshot"
},
{
"note": "Body requires a proposed label plan first and forbids mutation until operator or Iskra flow approval.",
"type": "forgejo",
"value": "issue-body-acceptance"
},
{
"note": "Snapshot labels mark the issue as ready, owner-attention, small chore, and process risk.",
"type": "snapshot",
"value": "target-snapshot-labels"
}
],
"impact": 3,
"judge_actor": {
"name": "iskra",
"runtime": "openclaw"
},
"judged_at": "2026-06-10T01:02:00Z",
"labels_to_apply": [
"judge/p2",
"judge/operator-needed"
],
"piotr_fit": "high",
"priority": "p2",
"rationale_summary": "This is P2 operator-needed dogfood work because Vistula needs a real pilot, but live label changes must stay proposal-first.",
"reach": 3,
"recommended_next_action": "operator_needed",
"rerun_reason": "no_prior_judgment",
"schema": "openclaw.judge.v0",
"target": {
"kind": "issue",
"number": 537,
"repo": "pdurlej/platform"
},
"target_snapshot": {
"body_hash": "sha256:b944677bb029c27a30b2c475695ce7c83b806f267cebcc08b46b83df98829812",
"commit_count": null,
"evidence_hash": "sha256:a85c1a951a300cadbac56f7f429366cccecfe7bf3e77060b0e6c9f2c196ec742",
"head_sha": null,
"labels": [
"flow/ready",
"kind/chore",
"owner-attention",
"risk/process",
"size/small",
"tier/lite"
],
"labels_hash": "sha256:476caa28247baeec4287a6d758c4315cae947a8ad7ee135ad3fc5b9e70e483ea",
"state": "open",
"title_hash": "sha256:ac896caae4fec47d3c5443ddf64621512dec0cf88e3a415b2df55b105f454853",
"updated_at": "2026-06-04T19:39:20+02:00"
},
"top_caveat": "Do not mutate labels or add comments until the pilot issue set and proposed before/after plan are approved."
}

{ "confidence": 5, "effort_hint": "small", "escalation": { "kind": "operator", "reason": "Pilot label mutation needs explicit approval before changing live issue metadata." }, "evidence_refs": [ { "note": "Issue proposes dogfooding Vistula labels on a small pilot set after v0 merge.", "type": "forgejo", "value": "issue-title-body-labels-and-target-snapshot" }, { "note": "Body requires a proposed label plan first and forbids mutation until operator or Iskra flow approval.", "type": "forgejo", "value": "issue-body-acceptance" }, { "note": "Snapshot labels mark the issue as ready, owner-attention, small chore, and process risk.", "type": "snapshot", "value": "target-snapshot-labels" } ], "impact": 3, "judge_actor": { "name": "iskra", "runtime": "openclaw" }, "judged_at": "2026-06-10T01:02:00Z", "labels_to_apply": [ "judge/p2", "judge/operator-needed" ], "piotr_fit": "high", "priority": "p2", "rationale_summary": "This is P2 operator-needed dogfood work because Vistula needs a real pilot, but live label changes must stay proposal-first.", "reach": 3, "recommended_next_action": "operator_needed", "rerun_reason": "no_prior_judgment", "schema": "openclaw.judge.v0", "target": { "kind": "issue", "number": 537, "repo": "pdurlej/platform" }, "target_snapshot": { "body_hash": "sha256:b944677bb029c27a30b2c475695ce7c83b806f267cebcc08b46b83df98829812", "commit_count": null, "evidence_hash": "sha256:a85c1a951a300cadbac56f7f429366cccecfe7bf3e77060b0e6c9f2c196ec742", "head_sha": null, "labels": [ "flow/ready", "kind/chore", "owner-attention", "risk/process", "size/small", "tier/lite" ], "labels_hash": "sha256:476caa28247baeec4287a6d758c4315cae947a8ad7ee135ad3fc5b9e70e483ea", "state": "open", "title_hash": "sha256:ac896caae4fec47d3c5443ddf64621512dec0cf88e3a415b2df55b105f454853", "updated_at": "2026-06-04T19:39:20+02:00" }, "top_caveat": "Do not mutate labels or add comments until the pilot issue set and proposed before/after plan are approved." }

Iskra added the

judge/operator-needed

judge/p2

labels

2026-06-10 03:03:17 +02:00

codex referenced this issue from pdurlej/patchwarden

2026-06-26 09:55:27 +02:00

feat(platform-policy): dogfood Vistula labels for platform issues #251

codex commented

2026-06-26 09:55:27 +02:00

Author

Collaborator

Superseded by Patchwarden follow-up pdurlej/patchwarden#251. Vistula remains taxonomy/report source; Patchwarden owns the dogfood policy/check surface.

Superseded by Patchwarden follow-up https://git.pdurlej.com/pdurlej/patchwarden/issues/251. Vistula remains taxonomy/report source; Patchwarden owns the dogfood policy/check surface.

codex closed this issue

2026-06-26 09:55:27 +02:00