Evidence reconciliation — tools

The distinct tools record for Evidence reconciliation. This page is proposal-only.

Status: proposedLifecycle: candidate

Record status

Record ID: job:tilly:evidence-reconciliation
Parent lifecycle: candidate
Page lane: package
Lane lifecycle: proposed
Owner: Tilly
Owner role: Pointguard and independent reviewer
Owner status: WORKING
Qualification result: NOT RUN · held for evidence and human review

Working browser surface: Agent jobs — builder overview — Inspect the package and stage a local project. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held.

Authoritative package lane tools and interfaces

Canonical tools-page assignments

PointGuard (interface · required) — Provides the persistent cross-app context room for the review while specialist apps remain canonical owners.
Instrument catalog (interface · required) — Provides the bounded catalog of available verified instruments; selection must remain limited to exact approved slugs.
Claim examiner (interface · required) — Supports comparison of claim wording against evidence and exposes where a claim outruns its receipts.
Citation checks (skill · required) — Checks source locators, provenance, revisions, and citation completeness without implying publication authority.
Agent Logs (record · required) — Preserves work state, receipts, authority boundaries, and review history.
Approvals (interface · required) — Records local proposal decisions as Needs review, Approved, or Held while external effects remain held.
Field Guides (interface · required) — Opens the existing Instrument packets, Qualification records, Grant dossiers, and Public-claim routes procedures.

Only the page's admitted lane is rendered as an assignment. Other lane inventories remain source records but are not merged here. Tool kind and required/optional status are preserved.

Authoritative lane instrument assignments

Canonical tools-page assignments

checksum-verifieroptional · Verify supplied source hashes or file checksums when a checksum value is available; record the result as evidence, not as publication approval.binary-text-diff-similarity-ratiooptional · Compare supplied text revisions or claim drafts for material differences; preserve inputs and treat similarity as a review aid, not proof of correctness.

An instrument listed only for another lane does not become a tools-page assignment.

Use boundary

A citation or checksum may verify identity or presence without proving the claim is true.
A draft, local approval, or indexed route may be mistaken for publication or production authority.
Tilly may be pressured to approve her own instrument work or evidence.
Contradictions may be hidden by summarization, revision loss, or selective source linking.
A stale source revision may be treated as current without recording provenance and hash state.
Qualification, grant, credential, or funding language may imply authorization not present in the records.
Instrument outputs may be overinterpreted beyond their stated educational or estimator limitations.
Private evidence may leak into public-claim preparation or customer-facing surfaces.
Missing deadlines may cause silent drift or unreviewed publication pressure.
Provider, database, credential, customer, upload, send, and production effects are not established by the available routes.

Sources and evidence

These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.

agents/index.html#tilly
source_record:job:tilly:evidence-reconciliation
job:tilly:evidence-reconciliation
Observed native contract: Notebook records, deadlines, PointGuard, lifecycle, provenance, and held web boundary
App routes: /app/pointguard/, /app/notebook/agent-logs/, /app/notebook/approvals/, /app/notebook/field-guides/, /app/notebook/search/
Allowed instruments: checksum-verifier
Allowed instruments: binary-text-diff-similarity-ratio