Evidence reconciliation — field guides

Record status

Record ID

job:tilly:evidence-reconciliation

Parent lifecycle

candidate

Page lane

docs_urls

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.

Related field-guide records

• /app/notebook/field-guides/

Source-proposed guide paths are references, not proof that those paths resolve.

Operating sequence

1. Create a local review record linked to the requesting agent, claim, and source records.
2. Capture the exact claim wording and its intended audience, scope, and deadline.
3. Collect source locators, provenance, revisions, and hashes without altering another agent's source.
4. Run citation checks and compare every material assertion with its cited receipt.
5. Record instrument work and qualification evidence separately from narrative conclusions.
6. Identify contradictions, missing receipts, stale revisions, and claims that exceed the evidence.
7. Check principal gates for publication, funding, credential access, and source changes.
8. Mark the outcome Needs review, Approved, or Held; Tilly must not approve her own evidence.
9. Create bounded correction tasks with owners and due dates using Notebook to-dos.
10. Preserve the review receipt in Agent Logs and link the outcome to the relevant PointGuard room.
11. Keep any public-claim route, final publication, external send, provider effect, and production effect held for authorized human review.

Handoff 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
• source record job:tilly:evidence-reconciliation
• Observed native contract: PointGuard
• Observed native contract: records
• Observed native contract: deadlines
• Observed native contract: web boundary
• App route /app/pointguard/
• App route /app/notebook/field-guides/
• App route /app/notebook/agent-logs/
• App route /app/notebook/approvals/
• App route /app/notebook/search/
• Allowed instrument checksum-verifier