← Back to the dossier

SYSTEMS NOTES / AGENT RELIABILITY

Agent Reliability

What should stay deterministic?

As a model gains tools, a plausible answer becomes insufficient evidence of success. The work below examines approval, incomplete information, and receipts tied to a particular delivery.

Voice-intake prototype / Avorth

Approval must name the exact action

FAILURE TO GUARD AGAINST
Content changes after someone approves it.
EXPLICIT BOUNDARY
Store the payload and bind approval to its hash. Reject a stale or corrupted payload before execution.
WHAT THE EVIDENCE SUPPORTS
Inspected prototype behavior. Paging and alerts are simulated.

Read-only operational data / Avorth

A partial read must remain partial

FAILURE TO GUARD AGAINST
A valid API page is mistaken for a complete result.
EXPLICIT BOUNDARY
Expose whether pagination reached the end. Restrict accounting requests to GET in the adapter.
WHAT THE EVIDENCE SUPPORTS
Code inspection supports these boundaries, not production adoption or coverage of every API.

Offline coordination prototype / VALUN

A receipt must identify the work

FAILURE TO GUARD AGAINST
Signed evidence concerns a different delivery, or the checker covers too little.
EXPLICIT BOUNDARY
Bind checker receipts to the task and delivery hash; take trust roots from verifier configuration.
WHAT THE EVIDENCE SUPPORTS
Documented prototype, not an independent implementation audit. A signature cannot establish arbitrary correctness; mock settlement proves no real payment.
AVORTH / SYSTEM STUDYINSPECTED PROTOTYPE SOURCE

Approval is not delivery. Delivery is not acknowledgement.

What would actually count as a completed handoff?

  1. 01
    MODEL ASSISTANCE

    Collect intake

    Voice-model intake produces a durable call record

  2. 02
    SOFTWARE LOGIC

    Bind the payload

    Prepare stored content and check its hash

  3. 03
    HUMAN JUDGMENT

    Approve that version

    Reviewer approves the exact payload

  4. 04
    SOFTWARE LOGIC

    Attempt the handoff

    Local desk paging and alerts are simulated

    SIMULATED / MODELED
  5. 05
    SOFTWARE LOGIC

    Check acknowledgement

    Track acknowledgement by a named person

INSPECT THE FAILURE BOUNDARYThe payload changes, or nobody acknowledges the attempted handoff.
WHAT FOLLOWS

Stale or corrupted payloads are rejected. Silence can exhaust escalation without being labeled completion. These are inspected prototype behaviors; the suite was not rerun for this site.

This drawing covers the voice prototype. The separate accounting adapter is read-only; it does not create invoices. No live dispatch or autonomous business outcome is implied.

Approval, delivery, and acknowledgement ↗Read-only adapters and coverage state ↗
Inspect the offline coordination lifecycle
VALUN / SYSTEM STUDYPRIVATE DOCUMENTATION REVIEW

A signature needs a task, a delivery, and a trust boundary.

What is the checker actually entitled to certify?

  1. 01
    SOFTWARE LOGIC

    Post / claim

    An explicit work lifecycle identifies the task

  2. 02
    INFORMATION / ARTIFACT

    Submit delivery

    Acceptance evidence refers to a delivery hash

  3. 03
    SOFTWARE LOGIC

    Check the receipt

    Signed checker evidence and configured trust roots

  4. 04
    SOFTWARE LOGIC

    Accept / issue note

    Record the accepted transition in the event log

  5. 05
    INFORMATION / ARTIFACT

    Mock settlement

    Default local chain file; no real payment

    SIMULATED / MODELED
INSPECT THE FAILURE BOUNDARYA receipt is validly signed but concerns different work, or its checker has limited coverage.
WHAT FOLLOWS

The meaning of acceptance depends on the task/delivery binding and the configured checker. A signature is not proof of arbitrary correctness.

A simplified normal path from repository documentation. Review-lapse and dispute branches are omitted. The implementation and sandbox are not independently audited here.