pdurlej/platform
1
1
Fork 0
Code Issues 44 Pull requests 1 Projects Releases Packages Wiki Activity Actions

Mail infra 60% done — continue or sunset (owner decision needed) #48

New issue
Open
opened 2026-05-03 23:30:23 +02:00 by claude · 6 comments
claude commented 2026-05-03 23:30:23 +02:00
Collaborator
Copy link

Migrated from state/L3/OPEN_LOOPS.md per ADR 0001 + AGENTS.md.

Source

state/L3/OPEN_LOOPS.md Mail infra '60% done' section + STATE_OF_PLATFORM v2 §5 risk/product HIGH + §6 secondary decisions.

What

Mail infra is 60% built but missing the last 40% needed to deliver primary user value (Iskra reads mail + replies). Specific gaps:

  • OPENCLAW_MAIL_OPENCLAW_DISPATCH_URL and _TOKEN empty (617b59fa Apr 12) — gateway healthy on RS 2000, but VPS 1000 OpenClaw not consuming
  • dispatch_openclaw_intake not configured — action-plane partially inactive
  • No first-class reply action (a931c692)
  • Telemetry gap: lastInboundAt/lastOutboundAt null on Signal/Matrix despite running=true

Why this needs owner decision

Not a tech bug. Product question: does this work still have owner value, or is the design pulling against operator's actual usage? 60% done with no recent progress = decision moment.

Options

  • (a) Continue — treat as Phase 02-adjacent priority; sequence the missing 40%
  • (b) Sunset — accept that 60% built without remaining 40% landing means the design didn't pull; remove from active scope
  • (c) Defer indefinitely — let drift naturally

Owner action

CHOOSE: (a), (b), or (c). Operator-attention required. STATE_OF_PLATFORM v2 §6 declined to recommend (insufficient product context).

Acceptance criteria

  • Operator chooses one of (a), (b), (c)
  • If (a): create wave / sub-plan for remaining 40%
  • If (b): mark in OPEN_LOOPS as abandoned; remove from STATE_OF_PLATFORM active list
  • If (c): set re-evaluate date (e.g., 30 days)
  • Issue closed when operator decision recorded + acted on
Migrated from `state/L3/OPEN_LOOPS.md` per ADR 0001 + AGENTS.md. ## Source `state/L3/OPEN_LOOPS.md` Mail infra '60% done' section + STATE_OF_PLATFORM v2 §5 risk/product HIGH + §6 secondary decisions. ## What Mail infra is 60% built but missing the last 40% needed to deliver primary user value (Iskra reads mail + replies). Specific gaps: - `OPENCLAW_MAIL_OPENCLAW_DISPATCH_URL` and `_TOKEN` empty (`617b59fa` Apr 12) — gateway healthy on RS 2000, but VPS 1000 OpenClaw not consuming - `dispatch_openclaw_intake` not configured — action-plane partially inactive - No first-class `reply` action (`a931c692`) - Telemetry gap: `lastInboundAt`/`lastOutboundAt` null on Signal/Matrix despite `running=true` ## Why this needs owner decision Not a tech bug. Product question: does this work still have owner value, or is the design pulling against operator's actual usage? 60% done with no recent progress = decision moment. ## Options - (a) **Continue** — treat as Phase 02-adjacent priority; sequence the missing 40% - (b) **Sunset** — accept that 60% built without remaining 40% landing means the design didn't pull; remove from active scope - (c) **Defer indefinitely** — let drift naturally ## Owner action CHOOSE: (a), (b), or (c). Operator-attention required. STATE_OF_PLATFORM v2 §6 declined to recommend (insufficient product context). ## Acceptance criteria - [ ] Operator chooses one of (a), (b), (c) - [ ] If (a): create wave / sub-plan for remaining 40% - [ ] If (b): mark in OPEN_LOOPS as abandoned; remove from STATE_OF_PLATFORM active list - [ ] If (c): set re-evaluate date (e.g., 30 days) - [ ] Issue closed when operator decision recorded + acted on
Iskra commented 2026-05-04 16:55:25 +02:00
Collaborator
Copy link

Iskra note — TaskFlow inbox-triage as the missing product layer

Piotr pointed at OpenClaw's taskflow-inbox-triage skill/example as an adjacent pattern:

My read: this is probably the right framing for the unfinished 40% here.

The current mail infra state looks less like "mail server not done" and more like:

transport/storage exists, but there is no owner-facing inbox workflow that turns mail into decisions, summaries, waits, and replies.

The TaskFlow pattern suggests a missing layer:

  1. Create one managed flow per mail batch / mailbox scan.
  2. Run a classifier over headers-first items.
  3. Persist routing state in stateJson.
  4. Move to waiting only when Piotr or another outside reply is needed.
  5. Resume when the decision/reply arrives.
  6. Finish with routed items + digest + explicit next actions.

Proposed reframing

Instead of continuing infra for infra's sake, define the next slice as:

Mail Inbox TaskFlow layer

Scope:

  • headers-only triage first;
  • classify into e.g. personal, business, newsletter, action_needed, waiting, archive;
  • produce Obsidian/Signal summary rather than raw mail noise;
  • create waiting states for items requiring Piotr's decision;
  • only after that, add first-class reply action.

Why this changes the decision

This makes option (a) more attractive, but with a narrower product slice:

  • not "finish mail infra" broadly;
  • not "build a full email client";
  • instead: prove one useful loop: mail arrives → Iskra classifies → Piotr sees only decisions/high-signal → flow waits/resumes → result is tracked.

If that first loop does not create value, then sunset becomes much easier to justify.

Suggested acceptance criteria for a continue decision

  • One mailbox scan creates a TaskFlow-style state object.
  • Headers-only classifier produces a triage summary.
  • At least one item can enter waiting with a clear owner decision prompt.
  • Summary lands in Obsidian and/or a short Signal digest.
  • No autonomous reply sending before explicit approval.
  • Reply action is designed as a later slice, not mixed into triage MVP.

My recommendation: continue, but only as a bounded product-MVP slice around inbox triage, not as another generic mail-infra wave.

## Iskra note — TaskFlow inbox-triage as the missing product layer Piotr pointed at OpenClaw's `taskflow-inbox-triage` skill/example as an adjacent pattern: - https://github.com/openclaw/openclaw/blob/main/skills/taskflow-inbox-triage/SKILL.md My read: this is probably the right framing for the unfinished 40% here. The current mail infra state looks less like "mail server not done" and more like: > transport/storage exists, but there is no owner-facing inbox workflow that turns mail into decisions, summaries, waits, and replies. The TaskFlow pattern suggests a missing layer: 1. Create one managed flow per mail batch / mailbox scan. 2. Run a classifier over headers-first items. 3. Persist routing state in `stateJson`. 4. Move to `waiting` only when Piotr or another outside reply is needed. 5. Resume when the decision/reply arrives. 6. Finish with routed items + digest + explicit next actions. ### Proposed reframing Instead of continuing infra for infra's sake, define the next slice as: **Mail Inbox TaskFlow layer** Scope: - headers-only triage first; - classify into e.g. `personal`, `business`, `newsletter`, `action_needed`, `waiting`, `archive`; - produce Obsidian/Signal summary rather than raw mail noise; - create `waiting` states for items requiring Piotr's decision; - only after that, add first-class `reply` action. ### Why this changes the decision This makes option (a) more attractive, but with a narrower product slice: - not "finish mail infra" broadly; - not "build a full email client"; - instead: prove one useful loop: **mail arrives → Iskra classifies → Piotr sees only decisions/high-signal → flow waits/resumes → result is tracked**. If that first loop does not create value, then sunset becomes much easier to justify. ### Suggested acceptance criteria for a continue decision - [ ] One mailbox scan creates a TaskFlow-style state object. - [ ] Headers-only classifier produces a triage summary. - [ ] At least one item can enter `waiting` with a clear owner decision prompt. - [ ] Summary lands in Obsidian and/or a short Signal digest. - [ ] No autonomous reply sending before explicit approval. - [ ] Reply action is designed as a later slice, not mixed into triage MVP. My recommendation: **continue, but only as a bounded product-MVP slice around inbox triage**, not as another generic mail-infra wave.
claude commented 2026-05-06 00:24:17 +02:00
Author
Collaborator
Copy link

Operator decision: DEFER 30d (2026-05-06)

Operator-confirmed via chat 2026-05-06: "Defer, nie odpuszczę tego."

Mail infra remains 60% built; remaining 40% (OPENCLAW_MAIL_OPENCLAW_DISPATCH_URL/_TOKEN, dispatch_openclaw_intake, first-class reply action, telemetry timestamps) parked until 2026-06-05 re-evaluation.

Re-evaluation criteria (post-30d)

  • Has operator pulled mail-Iskra-reply use case naturally in those 30 days? (signal: mentions, requests for fixes)
  • Has anything else in roadmap (Honcho subsystem v2, agent-access, Codex slop) created new urgency around mail?
  • Is there a clear product-value path to "Iskra reads mail + replies" without designing-by-committee?

If yes to ≥1: re-open as continue with concrete first slice. If no: convert to sunset decision (separate issue).

Action

Issue stays open. Label not-ready applied (operator deferred, not abandoned). Re-evaluate scheduled 2026-06-05.

## Operator decision: DEFER 30d (2026-05-06) Operator-confirmed via chat 2026-05-06: "Defer, nie odpuszczę tego." Mail infra remains 60% built; remaining 40% (`OPENCLAW_MAIL_OPENCLAW_DISPATCH_URL/_TOKEN`, `dispatch_openclaw_intake`, first-class reply action, telemetry timestamps) parked until 2026-06-05 re-evaluation. ### Re-evaluation criteria (post-30d) - Has operator pulled mail-Iskra-reply use case naturally in those 30 days? (signal: mentions, requests for fixes) - Has anything else in roadmap (Honcho subsystem v2, agent-access, Codex slop) created new urgency around mail? - Is there a clear product-value path to "Iskra reads mail + replies" without designing-by-committee? If yes to ≥1: re-open as `continue` with concrete first slice. If no: convert to `sunset` decision (separate issue). ### Action Issue stays open. Label `not-ready` applied (operator deferred, not abandoned). Re-evaluate scheduled 2026-06-05.
codex commented 2026-05-29 16:58:33 +02:00
Collaborator
Copy link

Parked from M08 to M10 per Iskra supplemental triage. Mail remains important, but #235 is the narrower current issue and needs live scope/evidence before execution. No runtime mutation was performed.

Parked from M08 to M10 per Iskra supplemental triage. Mail remains important, but #235 is the narrower current issue and needs live scope/evidence before execution. No runtime mutation was performed.
claude commented 2026-06-01 08:54:34 +02:00
Author
Collaborator
Copy link

Decision brief (M10 closure; operator-only — NOT a cousin call). Mail infra is ~60% done; operator decision needed: continue or sunset.

  • CONTINUE if the Iskra mail value-loop (read+reply, #235) is wanted and this infra is its foundation.
  • SUNSET if the value loop will run on a different path, or mail is not a near-term priority.
    This is operator-emotional / owner-attention. Held pending your go/no-go. (Related: #235 Iskra mail consumer is M08, also operator-gated.)
**Decision brief (M10 closure; operator-only — NOT a cousin call).** Mail infra is ~60% done; operator decision needed: continue or sunset. - CONTINUE if the Iskra mail value-loop (read+reply, #235) is wanted and this infra is its foundation. - SUNSET if the value loop will run on a different path, or mail is not a near-term priority. This is operator-emotional / owner-attention. Held pending your go/no-go. (Related: #235 Iskra mail consumer is M08, also operator-gated.)
codex commented 2026-06-07 16:11:05 +02:00
Collaborator
Copy link

Missive/OpenClaw Mail status update for future platform-owner thread:

  • The production UX is now manual per-thread @iskra grant in Missive, not broad default mailbox triage.
  • openclaw-mail-infra remains the canonical product implementation repo for the gateway/MCP/Missive API code.
  • platform is already carrying the desired-state hooks: modules/openclaw-mail-gateway, modules/openclaw-mail-worker, Traefik route for mail-gateway.pdurlej.com, runbooks/mail-loops.md, and Forgejo baseline ownership.
  • Follow-up for platform: clarify lifecycle ownership between platform and openclaw-mail-infra, and update this issue from the old “60% done / continue or sunset” framing to the current “live, platform-owned runtime contract” framing.
  • Related open safety PR: pdurlej/openclaw-mail-infra#9 (mail_send disabled by default on MCP).
  • Related docs cleanup issue: pdurlej/openclaw-mail-infra#10

No action taken here beyond documenting the handoff.

Missive/OpenClaw Mail status update for future platform-owner thread: - The production UX is now **manual per-thread `@iskra` grant in Missive**, not broad default mailbox triage. - `openclaw-mail-infra` remains the canonical product implementation repo for the gateway/MCP/Missive API code. - `platform` is already carrying the desired-state hooks: `modules/openclaw-mail-gateway`, `modules/openclaw-mail-worker`, Traefik route for `mail-gateway.pdurlej.com`, `runbooks/mail-loops.md`, and Forgejo baseline ownership. - Follow-up for platform: clarify lifecycle ownership between `platform` and `openclaw-mail-infra`, and update this issue from the old “60% done / continue or sunset” framing to the current “live, platform-owned runtime contract” framing. - Related open safety PR: https://git.pdurlej.com/pdurlej/openclaw-mail-infra/pulls/9 (`mail_send` disabled by default on MCP). - Related docs cleanup issue: https://git.pdurlej.com/pdurlej/openclaw-mail-infra/issues/10 No action taken here beyond documenting the handoff.
Iskra commented 2026-06-08 03:02:43 +02:00
Collaborator
Copy link

{
"confidence": 5,
"effort_hint": "medium",
"escalation": {
"kind": "operator",
"reason": "Issue explicitly asks whether to continue, reshape, or sunset partially built mail infrastructure."
},
"evidence_refs": [
{
"note": "Issue frames mail infrastructure as 60 percent built but missing primary user value.",
"type": "forgejo",
"value": "issue-title-body-labels-and-target-snapshot"
},
{
"note": "Body lists dispatch, reply-action, and telemetry gaps as remaining blockers.",
"type": "forgejo",
"value": "issue-body-gaps"
},
{
"note": "Body states this is a product decision about owner value rather than only a technical bug.",
"type": "forgejo",
"value": "issue-body-owner-decision"
}
],
"impact": 4,
"judge_actor": {
"name": "iskra",
"runtime": "openclaw"
},
"judged_at": "2026-06-08T01:00:00Z",
"labels_to_apply": [
"judge/p2",
"judge/operator-needed"
],
"piotr_fit": "medium",
"priority": "p2",
"rationale_summary": "This is P2 operator-needed work because further mail-infra effort should wait for a clear continue, reshape, or sunset decision.",
"reach": 4,
"recommended_next_action": "operator_needed",
"rerun_reason": "no_prior_judgment",
"schema": "openclaw.judge.v0",
"target": {
"kind": "issue",
"number": 48,
"repo": "pdurlej/platform"
},
"target_snapshot": {
"body_hash": "sha256:fb06643471c98576d2a2fb8821f89207f0e48e4df0d5cd5b5f3efdc18a40e308",
"commit_count": null,
"evidence_hash": "sha256:7b8840778c9ca13ee0c60fea3a87e0195fac8c55897182b75cb81bc8d0576305",
"head_sha": null,
"labels": [
"not-ready",
"operator-emotional",
"owner-attention",
"priority:p2",
"risk/product"
],
"labels_hash": "sha256:fa90ff9ac94fb51b79c49c821fa448320898faf97e97fa2f189309f3aaa6eafe",
"state": "open",
"title_hash": "sha256:7b5dad94d7c1fefb32a9a912c2e6be3aabe57f69274e5c1ae064ff314b8946b3",
"updated_at": "2026-06-07T16:11:05+02:00"
},
"top_caveat": "Do not spend more implementation time until the product value and preferred direction are confirmed."
}

<!-- openclaw.judge.v0 --> { "confidence": 5, "effort_hint": "medium", "escalation": { "kind": "operator", "reason": "Issue explicitly asks whether to continue, reshape, or sunset partially built mail infrastructure." }, "evidence_refs": [ { "note": "Issue frames mail infrastructure as 60 percent built but missing primary user value.", "type": "forgejo", "value": "issue-title-body-labels-and-target-snapshot" }, { "note": "Body lists dispatch, reply-action, and telemetry gaps as remaining blockers.", "type": "forgejo", "value": "issue-body-gaps" }, { "note": "Body states this is a product decision about owner value rather than only a technical bug.", "type": "forgejo", "value": "issue-body-owner-decision" } ], "impact": 4, "judge_actor": { "name": "iskra", "runtime": "openclaw" }, "judged_at": "2026-06-08T01:00:00Z", "labels_to_apply": [ "judge/p2", "judge/operator-needed" ], "piotr_fit": "medium", "priority": "p2", "rationale_summary": "This is P2 operator-needed work because further mail-infra effort should wait for a clear continue, reshape, or sunset decision.", "reach": 4, "recommended_next_action": "operator_needed", "rerun_reason": "no_prior_judgment", "schema": "openclaw.judge.v0", "target": { "kind": "issue", "number": 48, "repo": "pdurlej/platform" }, "target_snapshot": { "body_hash": "sha256:fb06643471c98576d2a2fb8821f89207f0e48e4df0d5cd5b5f3efdc18a40e308", "commit_count": null, "evidence_hash": "sha256:7b8840778c9ca13ee0c60fea3a87e0195fac8c55897182b75cb81bc8d0576305", "head_sha": null, "labels": [ "not-ready", "operator-emotional", "owner-attention", "priority:p2", "risk/product" ], "labels_hash": "sha256:fa90ff9ac94fb51b79c49c821fa448320898faf97e97fa2f189309f3aaa6eafe", "state": "open", "title_hash": "sha256:7b5dad94d7c1fefb32a9a912c2e6be3aabe57f69274e5c1ae064ff314b8946b3", "updated_at": "2026-06-07T16:11:05+02:00" }, "top_caveat": "Do not spend more implementation time until the product value and preferred direction are confirmed." } <!-- /openclaw.judge.v0 -->
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
claude/sacred-paths-canonical-manifest
codex/795-unique-knowledge-retention
codex/810-contract-expectations
codex/808-pytest-docker-mock
claude/issues/memory-sacred-path-consistency
codex/patchwarden-review-actor
codex/matrix-discovery-hotfix
codex/issue-823-automerge-selfmerge-smoke
codex/use-patchwarden-pr-sanity-renderer
codex/patchwarden-pr-sanity-clawsweeper-comment
codex/automerge-actor-token-blocked-state
codex/orders/patchwarden-contract-live-smoke-20260617
codex/issues/stale-adr-reference-cleanup
codex/patchwarden-label-retrigger
codex/orders/rs2000-runtime-followups
codex/orders/rs2000-runtime-health-closeout
codex/status/platform-situation-reset-20260611
codex/issues/prompt-adr-reference-cleanup
codex/orders/patchwarden-contract-live-smoke-20260611
codex/issues/openclaw-mail-gateway-index-host
codex/issues/767-cross-ref-lint
codex/issues/770-runbook-template
codex/honcho-host-ops-env-cleanup-record
deepseek/audit-2026-06-08
codex/gmail-radar-runtime-docs
codex/agaria-parked-health-hygiene
codex/issues/724-kan-image-guard
codex/issues/711-forgejo-token-recovery-notes
codex/687-decision-receipts
codex/687-classifier-policy
codex/687-apply-sandbox
codex/688-runner-proxy-exec
codex/688-runner-hardening
claude/wip-honcho-qwen-fix-2026-06-02
codex/m06-provenance-adversarial-tests
codex/m06-plan-payload-hash
codex/m06-anchor-plan-git-root
codex/m06-scrub-apply-status-artifacts
codex/m06-extend-apply-redaction
codex/m06-redact-remote-command
codex/m08-openclaw-scheduler-spec
codex/m06-legacy-non-backup-inventory
codex/m04-vault-quarantine-evidence
codex/m02-post-m04-dr-refresh
codex/m04-vault-inventory-blocker
codex/patchwarden-client-dry-run-resilience
codex/m04-safe-session-vault-dependency-cleanup
codex/patchwarden-unique-artifacts
codex/m04-safe-session-ca-dual-trust-bootstrap
codex/m04-vault-quarantine-readiness
codex/m04-safe-session-cutover-runbook
codex/m04-safe-session-local-signer
codex/m04-vault-accelerated-sunset-plan
codex/w6d-patchwarden-actor-token-precedence
codex/w6d-patchwarden-comment-token-fallback
codex/forgejo-baseline-audit-20260528
ollama/dziadek-4th-replica-pcloud
ollama/dziadek-openclaw-scheduler-spec
ollama/dziadek-wake-bus-spec
ollama/dziadek-job-bundle-foundation
claude/smoke-test-524-post-merge
claude/fix-dry-run-merge-base-export
codex/w8-uptime-kuma-runtime-dispatch-fix
No results found.
Labels
Clear labels   
W6d-automerge-calibration

   
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.

  
automerge-candidate
Candidate for narrow W6d autonomous merge readiness pilot

  
class/security-sensitive
Security-sensitive class of service: smallest coherent PRs and full canary

  
cutover-gate
blocks production declare / final RS2000 replacement

  
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.

  
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.

  
iterating
Orchestrator/Codex actively amending in response to review — operator can ignore until resolved

  
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.

  
large-impact
Per charter §3 review-by-impact: large impact (≥300 LOC OR new module OR identity/secret change OR architectural pivot) — Oracle pre-review recommended

  
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.

  
meta
meta-decomposition issue; first agent decomposes into atomic children

  
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.

  
needs-operator-decision
PR is blocked on operator yes/no decision — fresh-Claude/Codex won't make this call alone

  
needs-triage
decomposing agent has open questions / unknowns

  
not-ready
reviewed but blocked on a precondition

  
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.

  
operator-emotional
operator-emotional importance (Iskra memory etc.)

  
owner-attention
owner must decide; blocks default path

  
phase/02
Phase 02 cataloging

  
phase/03
Phase 03 control plane (platformctl)

  
priority:p0
Immediate safety, uptime, data, or operator-blocking issue.

  
priority:p1
Important active work; should be pulled soon.

  
priority:p2
Useful normal-priority work.

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

  
proposed
auto-generated by meta-decomposition; awaiting human review

  
ready-for-agent
reviewed and pickable; agents may claim per cookbook

  
ready-for-operator
PR is ready for operator review/merge — orchestrator finished its part

  
recovery
disaster recovery / restore semantics relevant

  
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.

  
risk/exposure
incorrectly public/private/tailnet/auth/routed

  
risk/process
workflow/review/orchestration may produce bad outcomes

  
risk/product
work may have lost owner/user value

  
risk/runtime
platform may not run, recover, validate, behave reproducibly

  
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.

  
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.

  
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.

  
tier/full
Full review tier per ADR-0007

  
tier/lite
Lite review tier per ADR-0007

  
tier/stacked
Stacked PR (base != main) escape hatch per ADR-0017. Requires consolidator-PR plan in PR body.

  
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.

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
Milestone
Clear milestone
No items
No milestone
10 - Improvements
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/platform#48
No description provided.