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

fix(security): finish Bws/Infisical secrets injection — close 3-thread gap #237

New issue
Closed
opened 2026-05-12 07:59:20 +02:00 by pdurlej · 6 comments
pdurlej commented 2026-05-12 07:59:20 +02:00
Owner
Copy link

Why this matters (and how it helps Iskra)

Iskra's mail loop (#235), Phase 1.0 bundle (#236), and DR restore (#238) all need a clean secrets pipeline. Currently we have:

  • gateway secrets passed via env, not bws (commit 617b59fa, Apr 4)
  • 3 High findings unresolved per 44684022 Apr 5: curl -k, plaintext fallback, service token in plaintext
  • 3 uncommitted bws files on RS2000 sitting orphaned: docs/bws-setup.md, scripts/bws-preflight.sh, scripts/bws-run.sh

Per state/L3/OPEN_LOOPS.md: "each thread independently surfaces same gap" across 3 separate audits. We've been talking about this since April 5. It's a class/security-sensitive root-cause for downstream issues.

Context (from state/L3/OPEN_LOOPS.md — unresolved_active cluster "Bws/Infisical secrets injection")

3 audits, same gap, never closed:

Date Commit Finding
Apr 5 44684022 3 High findings: curl -k (TLS validation bypass), plaintext fallback in fetch path, service token stored as env var
Apr 4 617b59fa gateway secrets passed via env, not bws — i.e., the bws CLI is installed but the pipeline never connects to it
Apr 12 a931c692 same status confirmed — no progress between Apr 4 and Apr 12

On VPS-side: 3 niecommitowane pliki: docs/bws-setup.md, scripts/bws-preflight.sh, scripts/bws-run.sh — sit on RS2000 uncommitted. Either commit them or formally archive.

Adjacent: Infisical bridge on RS2000 — referenced as gate for canary-required.yml automation per DeepSeek 2026-05-11 review.

Acceptance criteria

  • Decision-PR first (operator + Codex joint): bws vs Infisical vs hybrid. Land an ADR if needed. Per OPEN_LOOPS deeper feedback: "mixed-signal architecture must allow cleanup later, not endless agony." Pick ONE primary secrets backend.
  • Recover uncommitted scripts: SSH to RS2000, capture current state of the 3 bws files. Either commit (after review) or formally archive in state/archive/ per ADR-0006.
  • Fix 3 High findings from Apr 5:
    • curl -k → use real TLS validation with pinned CA if needed
    • plaintext fallback → fail-closed, no plaintext path
    • service token in env → bws/Infisical-sourced, never inline
  • Wire gateway to chosen backend: at least one production secret (start with mail-infra dispatch token from #235) flows through bws/Infisical, not plain env.
  • Runbook: runbooks/secrets-pipeline.md covers rotation + emergency disconnect + bootstrap recovery.

Codex Packet

Scope: class/security-sensitive — smallest coherent PRs per AGENTS.md + REVIEW.md class/security-sensitive rules. Full canary 3+3 tier per ADR-0007.

Hard sequence (don't skip):

  1. Decision PR: ADR or operator-decision comment. Pick bws OR Infisical OR explicit hybrid pattern. Until this lands, NO downstream PRs.
  2. Recon + recovery PR: capture the 3 uncommitted RS2000 files. Read-only SSH, then file PR with their content + decision (commit vs archive).
  3. 3-fixes PR: address the Apr 5 High findings. Standalone, doesn't depend on backend choice.
  4. Wire-up PR: connect one production secret through chosen backend. Smallest possible: just the mail dispatch token from #235.
  5. Runbook PR: operational documentation.

Non-goals (DON'T do this)

  • ❌ "Migrate all secrets at once" — that's the endless-agony anti-pattern. One secret at a time, smallest PRs.
  • ❌ Bootstrap bws + Infisical both — pick ONE primary.
  • ❌ Touching policies/sacred-paths.yaml to "unlock" anything. Hard fail.
  • ❌ Storing secrets in module.yaml even temporarily for testing. Hard fail.
  • ❌ Forgejo repo secrets for production deploys (PR #234 already drew this line — respect it).

References

  • state/L3/OPEN_LOOPS.md — "Bws/Infisical secrets injection — never closed despite 3 threads"
  • Commits: 44684022 (Apr 5), 617b59fa (Apr 4), a931c692 (Apr 12)
  • AGENTS.md §security-sensitive class
  • REVIEW.md — class/security-sensitive triggers Full review tier
  • DeepSeek review 2026-05-11 — flagged Infisical bridge as RS2000 prerequisite

Filed by claude (Prof Kong intermezzo, 2026-05-12 morning).

## Why this matters (and how it helps Iskra) Iskra's mail loop (#235), Phase 1.0 bundle (#236), and DR restore (#238) all need a **clean secrets pipeline**. Currently we have: - gateway secrets passed via **env, not bws** (commit `617b59fa`, Apr 4) - 3 High findings unresolved per `44684022` Apr 5: `curl -k`, plaintext fallback, service token in plaintext - **3 uncommitted bws files on RS2000** sitting orphaned: `docs/bws-setup.md`, `scripts/bws-preflight.sh`, `scripts/bws-run.sh` Per `state/L3/OPEN_LOOPS.md`: *"each thread independently surfaces same gap"* across 3 separate audits. We've been talking about this since April 5. It's a class/security-sensitive root-cause for downstream issues. --- ## Context (from `state/L3/OPEN_LOOPS.md` — `unresolved_active` cluster "Bws/Infisical secrets injection") **3 audits, same gap, never closed:** | Date | Commit | Finding | |---|---|---| | Apr 5 | `44684022` | 3 High findings: `curl -k` (TLS validation bypass), plaintext fallback in fetch path, service token stored as env var | | Apr 4 | `617b59fa` | gateway secrets passed via env, not bws — i.e., the bws CLI is installed but the pipeline never connects to it | | Apr 12 | `a931c692` | same status confirmed — no progress between Apr 4 and Apr 12 | **On VPS-side**: 3 niecommitowane pliki: `docs/bws-setup.md`, `scripts/bws-preflight.sh`, `scripts/bws-run.sh` — sit on RS2000 uncommitted. Either commit them or formally archive. **Adjacent**: Infisical bridge on RS2000 — referenced as gate for `canary-required.yml` automation per DeepSeek 2026-05-11 review. --- ## Acceptance criteria - [ ] **Decision-PR first** (operator + Codex joint): bws vs Infisical vs hybrid. Land an ADR if needed. Per OPEN_LOOPS deeper feedback: *"mixed-signal architecture must allow cleanup later, not endless agony."* Pick ONE primary secrets backend. - [ ] **Recover uncommitted scripts**: SSH to RS2000, capture current state of the 3 bws files. Either commit (after review) or formally archive in `state/archive/` per ADR-0006. - [ ] **Fix 3 High findings from Apr 5**: - `curl -k` → use real TLS validation with pinned CA if needed - plaintext fallback → fail-closed, no plaintext path - service token in env → bws/Infisical-sourced, never inline - [ ] **Wire gateway to chosen backend**: at least one production secret (start with mail-infra dispatch token from #235) flows through bws/Infisical, not plain env. - [ ] **Runbook**: `runbooks/secrets-pipeline.md` covers rotation + emergency disconnect + bootstrap recovery. --- ## Codex Packet **Scope**: class/security-sensitive — smallest coherent PRs per AGENTS.md + REVIEW.md `class/security-sensitive` rules. Full canary 3+3 tier per ADR-0007. **Hard sequence** (don't skip): 1. **Decision PR**: ADR or operator-decision comment. Pick bws OR Infisical OR explicit hybrid pattern. Until this lands, NO downstream PRs. 2. **Recon + recovery PR**: capture the 3 uncommitted RS2000 files. Read-only SSH, then file PR with their content + decision (commit vs archive). 3. **3-fixes PR**: address the Apr 5 High findings. Standalone, doesn't depend on backend choice. 4. **Wire-up PR**: connect one production secret through chosen backend. Smallest possible: just the mail dispatch token from #235. 5. **Runbook PR**: operational documentation. --- ## Non-goals (DON'T do this) - ❌ "Migrate all secrets at once" — that's the endless-agony anti-pattern. One secret at a time, smallest PRs. - ❌ Bootstrap bws + Infisical both — pick ONE primary. - ❌ Touching `policies/sacred-paths.yaml` to "unlock" anything. Hard fail. - ❌ Storing secrets in `module.yaml` even temporarily for testing. Hard fail. - ❌ Forgejo repo secrets for production deploys (PR #234 already drew this line — respect it). --- ## References - `state/L3/OPEN_LOOPS.md` — "Bws/Infisical secrets injection — never closed despite 3 threads" - Commits: `44684022` (Apr 5), `617b59fa` (Apr 4), `a931c692` (Apr 12) - AGENTS.md §security-sensitive class - REVIEW.md — class/security-sensitive triggers Full review tier - DeepSeek review 2026-05-11 — flagged Infisical bridge as RS2000 prerequisite --- *Filed by claude (Prof Kong intermezzo, 2026-05-12 morning).*
pdurlej commented 2026-05-18 16:58:51 +02:00
Author
Owner
Copy link

Codex live audit: this is still the hard blocker — 2026-05-18 16:56 CEST

Verified on rs2000:

  • /data/platformctl/infisical-client-secret exists and is root:root 0600.
  • /data/platformctl/canary.env does not exist.
  • /data/platformctl/reports/canary-readiness-current.json is stale from 2026-05-10 and says ready=false, status=not_configured.
  • Missing canary env keys include PLATFORMCTL_CANARY_ENV_SCHEMA, PLATFORMCTL_CANARY_ENV_SOURCE, PLATFORMCTL_CANARY_ENV_SECRET_MAP_SHA256, PLATFORMCTL_ZAI_API_KEY.
  • direct Universal Auth smoke currently fails with 401 Invalid credentials.

So the secrets bridge is not operational for the canary path yet. This issue should remain open until the machine identity can generate the canary env file and the readiness report is green.

Non-negotiable constraint preserved: do not replace this with direct Forgejo repo secrets for ZAI/OpenAI/Anthropic/Claude/etc. The right fix is machine identity ↔ Infisical ↔ machine-local env file, plus non-secret metadata proving provenance.

<!-- codex-actions-audit-2026-05-18 --> ## Codex live audit: this is still the hard blocker — 2026-05-18 16:56 CEST Verified on rs2000: - `/data/platformctl/infisical-client-secret` exists and is `root:root 0600`. - `/data/platformctl/canary.env` does **not** exist. - `/data/platformctl/reports/canary-readiness-current.json` is stale from 2026-05-10 and says `ready=false`, `status=not_configured`. - Missing canary env keys include `PLATFORMCTL_CANARY_ENV_SCHEMA`, `PLATFORMCTL_CANARY_ENV_SOURCE`, `PLATFORMCTL_CANARY_ENV_SECRET_MAP_SHA256`, `PLATFORMCTL_ZAI_API_KEY`. - direct Universal Auth smoke currently fails with `401 Invalid credentials`. So the secrets bridge is not operational for the canary path yet. This issue should remain open until the machine identity can generate the canary env file and the readiness report is green. Non-negotiable constraint preserved: do not replace this with direct Forgejo repo secrets for ZAI/OpenAI/Anthropic/Claude/etc. The right fix is machine identity ↔ Infisical ↔ machine-local env file, plus non-secret metadata proving provenance.
codex commented 2026-05-24 19:27:33 +02:00
Collaborator
Copy link

W4c Slice 1 — Infisical primary decision PR opened — 2026-05-24

Role: executor
Intent: checkpoint
Needs owner: yes, via PR merge decision

Opened #438 as the #237 Decision PR slice.

What it decides

  • Infisical is the primary platform secrets backend.
  • BWS is legacy/recovery material unless a future ADR grants a narrow exception.
  • Generated runtime env files are allowed only as protected Infisical-rendered runtime artifacts.
  • No bulk migration; one consumer/secret class at a time.

What it does not do

  • No runtime mutation.
  • No secret migration.
  • No Vault sunset.
  • No BWS file recovery/archive yet.
  • No #124 Honcho Redis leak fix yet.

Next after merge

Proceed with W4c recovery/archive inventory for old BWS files, then narrow concrete leak fixes such as #124.

## W4c Slice 1 — Infisical primary decision PR opened — 2026-05-24 **Role:** executor **Intent:** checkpoint **Needs owner:** yes, via PR merge decision Opened #438 as the #237 Decision PR slice. ### What it decides - Infisical is the primary platform secrets backend. - BWS is legacy/recovery material unless a future ADR grants a narrow exception. - Generated runtime env files are allowed only as protected Infisical-rendered runtime artifacts. - No bulk migration; one consumer/secret class at a time. ### What it does not do - No runtime mutation. - No secret migration. - No Vault sunset. - No BWS file recovery/archive yet. - No #124 Honcho Redis leak fix yet. ### Next after merge Proceed with W4c recovery/archive inventory for old BWS files, then narrow concrete leak fixes such as #124.
codex commented 2026-05-24 19:49:13 +02:00
Collaborator
Copy link

W4c BWS recovery/archive recon — 2026-05-24

Role: executor
Intent: checkpoint
Needs owner: no, unless operator has an external backup/private copy of the old BWS files

Opened #440 as the BWS recovery/archive recon PR.

Result

The three historical BWS target files from #237 are not present in current checked locations:

  • current repo target file search: no matches
  • git history target file search: no matches
  • RS2000 targeted roots: no target files
  • RS2000 legacy git status for target files: no output
  • RS2000 wider read-only find across typical roots: no target files

No file contents were printed or copied. No runtime mutation.

Decision recorded in PR

No BWS content can be safely committed or archived from current RS2000 state. The archive result is metadata-only negative evidence. BWS remains legacy/recovery material per ADR-0024.

Remaining #237 work

  • fix Apr 5 high findings as narrow PRs;
  • wire one production secret through the chosen Infisical-backed path;
  • keep #124 as a separate concrete leak fix.
## W4c BWS recovery/archive recon — 2026-05-24 **Role:** executor **Intent:** checkpoint **Needs owner:** no, unless operator has an external backup/private copy of the old BWS files Opened #440 as the BWS recovery/archive recon PR. ### Result The three historical BWS target files from #237 are not present in current checked locations: - current repo target file search: no matches - git history target file search: no matches - RS2000 targeted roots: no target files - RS2000 legacy git status for target files: no output - RS2000 wider read-only find across typical roots: no target files No file contents were printed or copied. No runtime mutation. ### Decision recorded in PR No BWS content can be safely committed or archived from current RS2000 state. The archive result is metadata-only negative evidence. BWS remains legacy/recovery material per ADR-0024. ### Remaining #237 work - fix Apr 5 high findings as narrow PRs; - wire one production secret through the chosen Infisical-backed path; - keep #124 as a separate concrete leak fix.
codex commented 2026-05-24 19:56:49 +02:00
Collaborator
Copy link

W4d/W4e closeout prep opened — 2026-05-24

Role: executor
Intent: checkpoint
Needs owner: no immediate action beyond PR review

Opened #442 to prepare W4 closeout after the parallel W4 fork PRs merge.

It classifies W4 blockers vs follow-up milestones:

  • blockers only if unresolved: #237 residual slices, #124 handling, #56 current identity standard;
  • follow-up, not W4 blockers: #274 rotation, #132/#181 YubiKey, #64 Vault sunset, #131 VPS1000/OpenClaw config migration.

Runtime: none.

## W4d/W4e closeout prep opened — 2026-05-24 **Role:** executor **Intent:** checkpoint **Needs owner:** no immediate action beyond PR review Opened #442 to prepare W4 closeout after the parallel W4 fork PRs merge. It classifies W4 blockers vs follow-up milestones: - blockers only if unresolved: #237 residual slices, #124 handling, #56 current identity standard; - follow-up, not W4 blockers: #274 rotation, #132/#181 YubiKey, #64 Vault sunset, #131 VPS1000/OpenClaw config migration. Runtime: none.
codex commented 2026-05-24 20:19:55 +02:00
Collaborator
Copy link

W4c BWS/Infisical follow-up has been consolidated into #443. If #443 merges, the W4 backend ambiguity and stale BWS-file recovery item are resolved; residual concrete fixes should continue as narrow follow-ups, not broad backend debate.

W4c BWS/Infisical follow-up has been consolidated into #443. If #443 merges, the W4 backend ambiguity and stale BWS-file recovery item are resolved; residual concrete fixes should continue as narrow follow-ups, not broad backend debate.
codex commented 2026-05-29 16:49:43 +02:00
Collaborator
Copy link

Closing after M03 triage as the broad parent is now superseded/resolved.

Evidence:

  • ADR-0024 accepted Infisical as the primary platform secrets backend.
  • runbooks/secrets-pipeline.md now defines the operational contract.
  • state/reports/w4c-bws-recovery-archive-2026-05-24.md records the BWS recovery/archive recon: the historical three BWS files were not found in current repo or checked RS2000 roots.
  • #124 closed the concrete Honcho Redis argv leak evidence path.
  • #605 and #606 added the current canary/Ollama env aliasing, Infisical key map, and Agent SOS docs so agents stop guessing path names.

What this does not claim:

  • It does not say every future secret cutover is complete.
  • It does not sunset Vault.
  • It does not rotate #274.
  • It does not authorize issue/comment writers or runtime secret mutations.

Remaining work should be tracked as narrow, concrete issues when found. Keeping this broad April-era bucket open now creates more ambiguity than safety.

Closing after M03 triage as the broad parent is now superseded/resolved. Evidence: - ADR-0024 accepted Infisical as the primary platform secrets backend. - `runbooks/secrets-pipeline.md` now defines the operational contract. - `state/reports/w4c-bws-recovery-archive-2026-05-24.md` records the BWS recovery/archive recon: the historical three BWS files were not found in current repo or checked RS2000 roots. - #124 closed the concrete Honcho Redis argv leak evidence path. - #605 and #606 added the current canary/Ollama env aliasing, Infisical key map, and Agent SOS docs so agents stop guessing path names. What this does not claim: - It does not say every future secret cutover is complete. - It does not sunset Vault. - It does not rotate #274. - It does not authorize issue/comment writers or runtime secret mutations. Remaining work should be tracked as narrow, concrete issues when found. Keeping this broad April-era bucket open now creates more ambiguity than safety.
codex closed this issue 2026-05-29 16:49:44 +02:00
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
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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/platform#237
No description provided.