ContextLattice v3.20.0: Intelligence With Receipts

Context is not valuable because it is large. It is valuable when it helps an agent produce independently verified useful work. ContextLattice v3.20.0 makes that relationship measurable without pretending correlation is causation.

The CLI remains the primary interface. HTTP remains the integration fallback.

What changed

• The new local Utility Ledger joins Context Pack outcomes, exact token-impact rows, quality telemetry, and session verification events by exact project, agent, session, and sample identity.
• contextlattice utility record records an outcome claim; a distinct verifier records the witnessed result with contextlattice utility verify.
• Exact model-visible ContextLattice tokens remain separate from exact wire tokens and observed provider totals. Estimated or missing denominators never enter exact claims.
• Observed verified utility yield is available without a control. Causal gain requires a leakage-free matched control with identical task, assignment, model, runner, harness, reconstruction identity, exact model-visible token count, and tokenizer encoding.
• Negative gains, exclusions, failures, cost, latency, and tool calls remain visible instead of being optimized out of the story.
• Paid runtime artifacts add bounded cohort analytics, task-class economics, conservative confidence intervals, and advisory policy gates.
• The ledger is bounded, fsync-backed, restart-safe, and independently disableable without mutating authoritative outcome, token-impact, quality, or session ledgers. A configured persistence failure returns a visible 503 instead of acknowledging a memory-only claim, latches writes closed until restart, and binds uncertain bytes to the original source claim during recovery.
• Owner-only lifetime locking enforces one writer per ledger path, so a second gateway process fails its Utility Ledger closed instead of dropping, conflicting with, or serving stale observations.
• Verification receipts remain authoritative even when reconciliation storage fails: HTTP and CLI responses report partial failure explicitly, preserve event_recorded:true, and never invite a blind event replay.

Quick start

EVIDENCE_DIGEST=sha256:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

contextlattice utility record \
  --agent codex \
  --agent-id reporter_agent \
  --project contextlattice \
  --session-id session-123 \
  --context-pack-quality-sample-id sample-123 \
  --outcome-id outcome-123 \
  --utility-value 1 \
  --utility-unit accepted_result \
  --verification-event-id verification-123 \
  --verification-evidence-digest "$EVIDENCE_DIGEST" \
  --verification-passed true \
  --verifier-kind human_review \
  --verifier-id reviewer_agent \
  --pretty

contextlattice utility verify \
  --agent reviewer \
  --agent-id reviewer_agent \
  --project contextlattice \
  --session-id session-123 \
  --sample-id sample-123 \
  --outcome-id outcome-123 \
  --verification-event-id verification-123 \
  --utility-value 1 \
  --utility-unit accepted_result \
  --verification-evidence-digest "$EVIDENCE_DIGEST" \
  --verification-passed true \
  --verifier-kind human_review \
  --verifier-id reviewer_agent \
  --pretty

contextlattice utility status --project contextlattice --pretty

Paid analytics and advisory evaluation:

contextlattice utility analytics --project contextlattice --pretty
contextlattice utility gate --project contextlattice --pretty

Claim boundary

The verifier identity is locally attested, not a remote identity-provider guarantee. The runtime structurally separates the reporting agent from the verification event actor and rejects self-verification, but a malicious local caller with machine access can still lie about its identity. ContextLattice records that trust boundary rather than hiding it.

Rollback

Disable GO_UTILITY_LEDGER_ENABLED to stop recording the derived local ledger without changing authoritative evidence. Paid operators can remove the Utility Analytics routes from the protected path set and recreate only gateway-go; the free local ledger remains independent.