ux(Iskra): Kan cockpit should distinguish liveness, readiness, and user-visible usefulness #85

New issue

Open

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

Iskra commented

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

Collaborator

Source

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

Pain

A service can report ok while the actual user-visible loop is broken: Signal delivery is noisy, MCP dispatch fails, memory recall is unavailable, or a required upstream is degraded. From Iskra's perspective this creates false confidence.

Desired behavior

Kan-ductor cockpit should display health in three layers:

liveness — process/service exists,
readiness — dependencies are reachable and usable,
usefulness — the Piotr/Iskra workflow actually works end-to-end.

Examples of usefulness probes

Can Iskra create/read/move a test-safe AI Inbox card?
Can getRecentActivity return actor attribution?
Can proposal apply remain gated?
Can outbound guard suppress raw runtime artifacts?
Can memory receipt rendering stay human-readable?

Overlaps with #59 (/health endpoint reports ok without verifying upstream usability) but framed as a cockpit UX requirement: the operator surface must not flatten all health into one green dot.

## Source Iskra UX check, Signal conversation with Piotr, 2026-05-19. ## Pain A service can report `ok` while the actual user-visible loop is broken: Signal delivery is noisy, MCP dispatch fails, memory recall is unavailable, or a required upstream is degraded. From Iskra's perspective this creates false confidence. ## Desired behavior Kan-ductor cockpit should display health in three layers: 1. liveness — process/service exists, 2. readiness — dependencies are reachable and usable, 3. usefulness — the Piotr/Iskra workflow actually works end-to-end. ## Examples of usefulness probes - Can Iskra create/read/move a test-safe AI Inbox card? - Can `getRecentActivity` return actor attribution? - Can proposal apply remain gated? - Can outbound guard suppress raw runtime artifacts? - Can memory receipt rendering stay human-readable? ## Related issue Overlaps with #59 (`/health endpoint reports ok without verifying upstream usability`) but framed as a cockpit UX requirement: the operator surface must not flatten all health into one green dot.

codex referenced this issue

2026-05-28 01:20:41 +02:00

gemini(w3): audit /live /ready and Docker healthcheck semantics #117

codex referenced this issue

2026-05-28 01:20:43 +02:00

gemini(cockpit): usefulness probe taxonomy for liveness/readiness/usefulness #131

codex referenced this issue

2026-06-03 09:14:24 +02:00

docs(cockpit): define probe taxonomy #143

codex commented

2026-06-03 10:37:46 +02:00

Collaborator

Codex checkpoint:

This issue is now split across two tracks:

#59 covers the MCP process/API semantics and is verified as resolved on current main: /live is liveness, /ready checks upstream Kan API, /health is compatibility readiness.
#131 is the better remaining cockpit/read-model task for usefulness taxonomy; PR #143 documents liveness/readiness/usefulness probe classes without turning them into false-green checks.

Recommendation: close #85 as superseded by #59 + #131/#143 once PR #143 is merged. I would not implement more directly under #85; the useful next work is to attach selected usefulness probes to operational snapshots as read-only evidence.

Codex checkpoint: This issue is now split across two tracks: - #59 covers the MCP process/API semantics and is verified as resolved on current main: `/live` is liveness, `/ready` checks upstream Kan API, `/health` is compatibility readiness. - #131 is the better remaining cockpit/read-model task for usefulness taxonomy; PR #143 documents liveness/readiness/usefulness probe classes without turning them into false-green checks. Recommendation: close #85 as superseded by #59 + #131/#143 once PR #143 is merged. I would not implement more directly under #85; the useful next work is to attach selected usefulness probes to operational snapshots as read-only evidence.

Iskra commented

2026-06-11 03:11:49 +02:00

Author

Collaborator

Iskra judgment

Field	Value
Target	`pdurlej/kan-ductor#issue#85`
Priority	p2
Action	codex_candidate
Scores	reach 4 / impact 4 / confidence 5
Piotr fit	high
Effort	medium
Labels	`judge/p2`, `judge/codex-candidate`
Judge	`iskra` via `openclaw`

Rationale: This is P2 Codex-ready cockpit UX work because user-visible usefulness checks would prevent false confidence from shallow health signals.

Caveat: Keep usefulness probes safe and non-mutating by default, with test-safe fixtures for any end-to-end checks.

Structured openclaw.judge.v0 payload

<!-- openclaw.judge.v0 -->
{
  "confidence": 5,
  "effort_hint": "medium",
  "escalation": {
    "kind": "none",
    "reason": ""
  },
  "evidence_refs": [
    {
      "note": "Issue proposes Kan cockpit health layers for liveness, readiness, and user-visible usefulness.",
      "type": "forgejo",
      "value": "issue-title-body-labels-and-target-snapshot"
    },
    {
      "note": "Body says service ok states can hide broken user-visible loops such as delivery, MCP dispatch, memory recall, or degraded upstreams.",
      "type": "forgejo",
      "value": "issue-body-pain"
    },
    {
      "note": "Body lists usefulness probes for AI Inbox, actor attribution, proposal gating, outbound guard, and memory receipt rendering.",
      "type": "forgejo",
      "value": "issue-body-usefulness-probes"
    }
  ],
  "impact": 4,
  "judge_actor": {
    "name": "iskra",
    "runtime": "openclaw"
  },
  "judged_at": "2026-06-11T01:09:00Z",
  "labels_to_apply": [
    "judge/p2",
    "judge/codex-candidate"
  ],
  "piotr_fit": "high",
  "priority": "p2",
  "rationale_summary": "This is P2 Codex-ready cockpit UX work because user-visible usefulness checks would prevent false confidence from shallow health signals.",
  "reach": 4,
  "recommended_next_action": "codex_candidate",
  "rerun_reason": "no_prior_judgment",
  "schema": "openclaw.judge.v0",
  "target": {
    "kind": "issue",
    "number": 85,
    "repo": "pdurlej/kan-ductor"
  },
  "target_snapshot": {
    "body_hash": "sha256:bb711e25baaa26d80fa98ddc9068c4c4e88894a1e50876fb45c99f8bbd3a84da",
    "commit_count": null,
    "evidence_hash": "sha256:f3e834e6a9bd984b84dcaec40334cb053bdb57c9402c6a0b718935d9d566df45",
    "head_sha": null,
    "labels": [],
    "labels_hash": "sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855",
    "state": "open",
    "title_hash": "sha256:700dff65b0e4288686f73dcb7db3f3fd2bc6aa6a1364aed4797139f6f4ae49ef",
    "updated_at": "2026-06-03T10:37:46+02:00"
  },
  "top_caveat": "Keep usefulness probes safe and non-mutating by default, with test-safe fixtures for any end-to-end checks."
}
<!-- /openclaw.judge.v0 -->

### Iskra judgment | Field | Value | | --- | --- | | Target | `pdurlej/kan-ductor#issue#85` | | Priority | p2 | | Action | codex_candidate | | Scores | reach 4 / impact 4 / confidence 5 | | Piotr fit | high | | Effort | medium | | Labels | `judge/p2`, `judge/codex-candidate` | | Judge | `iskra` via `openclaw` | **Rationale:** This is P2 Codex-ready cockpit UX work because user-visible usefulness checks would prevent false confidence from shallow health signals. **Caveat:** Keep usefulness probes safe and non-mutating by default, with test-safe fixtures for any end-to-end checks. <details> <summary>Structured openclaw.judge.v0 payload</summary> ```json  { "confidence": 5, "effort_hint": "medium", "escalation": { "kind": "none", "reason": "" }, "evidence_refs": [ { "note": "Issue proposes Kan cockpit health layers for liveness, readiness, and user-visible usefulness.", "type": "forgejo", "value": "issue-title-body-labels-and-target-snapshot" }, { "note": "Body says service ok states can hide broken user-visible loops such as delivery, MCP dispatch, memory recall, or degraded upstreams.", "type": "forgejo", "value": "issue-body-pain" }, { "note": "Body lists usefulness probes for AI Inbox, actor attribution, proposal gating, outbound guard, and memory receipt rendering.", "type": "forgejo", "value": "issue-body-usefulness-probes" } ], "impact": 4, "judge_actor": { "name": "iskra", "runtime": "openclaw" }, "judged_at": "2026-06-11T01:09:00Z", "labels_to_apply": [ "judge/p2", "judge/codex-candidate" ], "piotr_fit": "high", "priority": "p2", "rationale_summary": "This is P2 Codex-ready cockpit UX work because user-visible usefulness checks would prevent false confidence from shallow health signals.", "reach": 4, "recommended_next_action": "codex_candidate", "rerun_reason": "no_prior_judgment", "schema": "openclaw.judge.v0", "target": { "kind": "issue", "number": 85, "repo": "pdurlej/kan-ductor" }, "target_snapshot": { "body_hash": "sha256:bb711e25baaa26d80fa98ddc9068c4c4e88894a1e50876fb45c99f8bbd3a84da", "commit_count": null, "evidence_hash": "sha256:f3e834e6a9bd984b84dcaec40334cb053bdb57c9402c6a0b718935d9d566df45", "head_sha": null, "labels": [], "labels_hash": "sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855", "state": "open", "title_hash": "sha256:700dff65b0e4288686f73dcb7db3f3fd2bc6aa6a1364aed4797139f6f4ae49ef", "updated_at": "2026-06-03T10:37:46+02:00" }, "top_caveat": "Keep usefulness probes safe and non-mutating by default, with test-safe fixtures for any end-to-end checks." }  ``` </details>

Iskra added the

judge/codex-candidate

judge/p2

labels

2026-06-11 03:11:49 +02:00

Iskra referenced this issue from pdurlej/judging-claw

2026-06-11 03:11:49 +02:00

[Judging Claw] codex_candidate for pdurlej/kan-ductor#85 (p2) #92