ux(Iskra): project promise/open-loop ledger into Kan-ductor without duplicating truth #81

New issue

Open

opened 2026-05-19 02:11:36 +02:00 by Iskra · 2 comments

Iskra commented

2026-05-19 02:11:36 +02:00

Collaborator

Source

Iskra UX check, Signal conversation with Piotr, 2026-05-19.

Pain

Promise debt currently lives in memory/open-loops.json, with helper scripts and sometimes checkpoint cron. This is correct as a source of truth, but not enough as a collaboration UX. Piotr should not need to infer from chat whether something is still open, covered by cron, stale, or waiting for him.

Desired behavior

Kan-ductor should display promise/open-loop state as operational cards or a dedicated projection, while keeping the ledger as the canonical source of truth.

Important invariant

Do not create a second source of truth. Kan should show/projection-sync the state, not silently fork it.

Fields that matter

loop id / stable ref,
promise text,
owner/holder,
status: open / checkpoint scheduled / waiting / blocked / done / stale,
next checkpoint time,
last heartbeat/checkpoint result,
evidence link to ledger/cron/log/session,
whether Piotr needs to act.

Why

This is one of the biggest sources of “things happening sideways”. If Kan-ductor shows promise debt clearly, Iskra can be proactive without becoming noisy or unreliable.

## Source Iskra UX check, Signal conversation with Piotr, 2026-05-19. ## Pain Promise debt currently lives in `memory/open-loops.json`, with helper scripts and sometimes checkpoint cron. This is correct as a source of truth, but not enough as a collaboration UX. Piotr should not need to infer from chat whether something is still open, covered by cron, stale, or waiting for him. ## Desired behavior Kan-ductor should display promise/open-loop state as operational cards or a dedicated projection, while keeping the ledger as the canonical source of truth. ## Important invariant Do not create a second source of truth. Kan should show/projection-sync the state, not silently fork it. ## Fields that matter - loop id / stable ref, - promise text, - owner/holder, - status: open / checkpoint scheduled / waiting / blocked / done / stale, - next checkpoint time, - last heartbeat/checkpoint result, - evidence link to ledger/cron/log/session, - whether Piotr needs to act. ## Why This is one of the biggest sources of “things happening sideways”. If Kan-ductor shows promise debt clearly, Iskra can be proactive without becoming noisy or unreliable.

codex commented

2026-06-03 10:36:25 +02:00

Collaborator

Codex checkpoint after Cockpit v0:

What Kan-ductor now has:

operational_snapshot can already carry domain: "promise_debt" items,
the contract explicitly says the source system remains canonical,
snapshot items have id, title, status, freshness, evidence, needsPiotr, nextAction, links, and, via PR #156, optional trust metadata,
this is enough for a read-only promise/open-loop projection once OpenClaw/Iskra produces the snapshot.

What is still missing:

no producer yet reads memory/open-loops.json and emits promise_debt items,
no stable field set specific to promise loops: loopRef, holder, checkpointAt, lastCheckpointResult, canonicalLedgerRef,
no stale/checkpoint semantics documented specifically for promise debt,
no card projection/write path should be added until the read model proves useful.

Recommendation: keep #81 open, but implement next as promise debt snapshot producer contract rather than Kan card syncing. Small safe PR shape: extend docs/operational-cockpit-contract.md with a promise_debt item profile and add a secret-free example fixture. Runtime producer should live on the OpenClaw/Iskra side, not inside Kan-ductor.

Codex checkpoint after Cockpit v0: What Kan-ductor now has: - `operational_snapshot` can already carry `domain: "promise_debt"` items, - the contract explicitly says the source system remains canonical, - snapshot items have `id`, `title`, `status`, `freshness`, `evidence`, `needsPiotr`, `nextAction`, links, and, via PR #156, optional `trust` metadata, - this is enough for a read-only promise/open-loop projection once OpenClaw/Iskra produces the snapshot. What is still missing: - no producer yet reads `memory/open-loops.json` and emits `promise_debt` items, - no stable field set specific to promise loops: `loopRef`, `holder`, `checkpointAt`, `lastCheckpointResult`, `canonicalLedgerRef`, - no stale/checkpoint semantics documented specifically for promise debt, - no card projection/write path should be added until the read model proves useful. Recommendation: keep #81 open, but implement next as `promise debt snapshot producer contract` rather than Kan card syncing. Small safe PR shape: extend `docs/operational-cockpit-contract.md` with a `promise_debt` item profile and add a secret-free example fixture. Runtime producer should live on the OpenClaw/Iskra side, not inside Kan-ductor.

Iskra commented

2026-06-10 03:09:19 +02:00

Author

Collaborator

{
"confidence": 5,
"effort_hint": "medium",
"escalation": {
"kind": "operator",
"reason": "Promise-ledger projection needs owner-shaped UX and strict source-of-truth boundaries."
},
"evidence_refs": [
{
"note": "Issue proposes projecting promise and open-loop ledger state into Kan-ductor without duplicating truth.",
"type": "forgejo",
"value": "issue-title-body-labels-and-target-snapshot"
},
{
"note": "Body states memory/open-loops.json should remain canonical while Kan displays operational state and evidence links.",
"type": "forgejo",
"value": "issue-body-invariant"
},
{
"note": "Fields include stable loop refs, status, checkpoint timing, evidence links, and whether Piotr needs to act.",
"type": "forgejo",
"value": "issue-body-fields"
}
],
"impact": 5,
"judge_actor": {
"name": "iskra",
"runtime": "openclaw"
},
"judged_at": "2026-06-10T01:07:00Z",
"labels_to_apply": [
"judge/p1",
"judge/operator-needed"
],
"piotr_fit": "high",
"priority": "p1",
"rationale_summary": "This is P1 operator-shaped UX infrastructure because promise debt needs visible operational state without creating a second source of truth.",
"reach": 4,
"recommended_next_action": "operator_needed",
"rerun_reason": "no_prior_judgment",
"schema": "openclaw.judge.v0",
"target": {
"kind": "issue",
"number": 81,
"repo": "pdurlej/kan-ductor"
},
"target_snapshot": {
"body_hash": "sha256:cb8cd2abf67a3cd30f11bc38cfc9f0e6398f1267d06f38e5c1244eee55f2a6b5",
"commit_count": null,
"evidence_hash": "sha256:f0b0f73c252e155b60467261a46d1ef5e889b29822182d7d167ab5a92f2385c3",
"head_sha": null,
"labels": [],
"labels_hash": "sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855",
"state": "open",
"title_hash": "sha256:82f82d862854c64966cf755b3673f33153ad508a6edea9766064b6ef9f08aa1f",
"updated_at": "2026-06-03T10:36:25+02:00"
},
"top_caveat": "Keep Kan-ductor read-only or projection-synced from the ledger; never let cards silently fork promise state."
}

{ "confidence": 5, "effort_hint": "medium", "escalation": { "kind": "operator", "reason": "Promise-ledger projection needs owner-shaped UX and strict source-of-truth boundaries." }, "evidence_refs": [ { "note": "Issue proposes projecting promise and open-loop ledger state into Kan-ductor without duplicating truth.", "type": "forgejo", "value": "issue-title-body-labels-and-target-snapshot" }, { "note": "Body states memory/open-loops.json should remain canonical while Kan displays operational state and evidence links.", "type": "forgejo", "value": "issue-body-invariant" }, { "note": "Fields include stable loop refs, status, checkpoint timing, evidence links, and whether Piotr needs to act.", "type": "forgejo", "value": "issue-body-fields" } ], "impact": 5, "judge_actor": { "name": "iskra", "runtime": "openclaw" }, "judged_at": "2026-06-10T01:07:00Z", "labels_to_apply": [ "judge/p1", "judge/operator-needed" ], "piotr_fit": "high", "priority": "p1", "rationale_summary": "This is P1 operator-shaped UX infrastructure because promise debt needs visible operational state without creating a second source of truth.", "reach": 4, "recommended_next_action": "operator_needed", "rerun_reason": "no_prior_judgment", "schema": "openclaw.judge.v0", "target": { "kind": "issue", "number": 81, "repo": "pdurlej/kan-ductor" }, "target_snapshot": { "body_hash": "sha256:cb8cd2abf67a3cd30f11bc38cfc9f0e6398f1267d06f38e5c1244eee55f2a6b5", "commit_count": null, "evidence_hash": "sha256:f0b0f73c252e155b60467261a46d1ef5e889b29822182d7d167ab5a92f2385c3", "head_sha": null, "labels": [], "labels_hash": "sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855", "state": "open", "title_hash": "sha256:82f82d862854c64966cf755b3673f33153ad508a6edea9766064b6ef9f08aa1f", "updated_at": "2026-06-03T10:36:25+02:00" }, "top_caveat": "Keep Kan-ductor read-only or projection-synced from the ledger; never let cards silently fork promise state." }

Iskra added the

judge/operator-needed

judge/p1

labels

2026-06-10 03:09:20 +02:00