Skip to content

L08-07 — Qualify two clients, decision receipts, and the inspector #67

Open

Description

@mberrys

Outcome

Prove that Editor and PdfTool clients see the same observation identity, abstention, fallback, and provenance after restart. Ship the decision inspector and trace modeled on jev's inspector: the indexed table, every head's distribution, the selected head, reason codes, latency and token usage, and a pause before handoff that lets the operator stop or choose manually.

Parent and boundary

Parent: #9. Owner: proposed Decision module. This issue owns one bounded slice of Bounded Decision Worker; consume accepted upstream contracts and keep PDF/verdict/publication authority with Core.

Acceptance

  • The receipt stores the full request, all raw head answers, the validated selection, provider/model identity, budget use, and timing. Replay reads the receipt; it does not re-ask the model.
  • Recorded decision replay is stable even if a stochastic model rerun differs.
  • The inspector and the PdfTool trace render the same receipt.
  • Failure case: a client-specific cache, a missing receipt, or an inspector that recomputes probabilities cannot count as parity.

Required proof

Two-client installed test, restart, inspector/trace parity fixture, and target-hardware cost report (per-decision latency, decisions per task, tokens). Record the exact source SHA, test command or hosted run, fixture/artifact identity, and any skipped or unavailable lane. Run the repository's mapped proof and check-change gate for a PR.

Handoff

Record changed files, observed result, remaining risk, and a 1–3 sentence anti-slop review. Completion means acceptance evidence, not merely a merged implementation.

Sources

Approved master roadmap · North Star: jev-ultrafast@1231850a; see the translation table in #9.


Generated by Claude Code

Activity

  1. changed the title [-]L08-07 — Qualify two clients and restart receipts[/-] [+]L08-07 — Qualify two clients, decision receipts, and the inspector[/+] on Oct 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions