Independent review — field guides

Record status

Record ID

job:tilly:independent-review

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. Receive and record the review brief, target IDs, requester, scope, deadline, and conflict-of-interest declaration.
2. Open the canonical source records and inspect provenance, revisions, source locators, attachments, and existing receipts.
3. Inventory the relevant instrument packets, qualification records, grant dossiers, citations, and public-claim materials.
4. Check each claim or qualification requirement against its cited evidence and record exact gaps, contradictions, and scope limits.
5. Separate verified support, unsupported assertions, unresolved questions, and recommendations; do not silently repair source material.
6. Create a review receipt linking the examined records, checks performed, findings, limitations, and disposition.
7. Route recommendations to the appropriate owner for local approval or hold; preserve any refusal or escalation as a record.
8. Schedule follow-up workbacks for missing evidence, rechecks, or owner decisions.
9. Close only when the receipt is complete, unresolved items have owners and deadlines, and publication or external effects remain explicitly held.

Handoff boundary

• Self-approval or conflict of interest can invalidate the review.
• A draft recommendation may be mistaken for approval, qualification, publication, or deployment.
• Citation presence alone may be mistaken for evidentiary support.
• Instrument catalog status may be treated as proof of a connected provider or production capability.
• A missing source hash, locator, revision, or attachment can make a receipt non-reproducible.
• Contradictions may be suppressed when records are summarized too aggressively.
• Grant or funding review may be mistaken for a funding commitment.
• Credential review may be mistaken for credential issuance or access.
• Changing another agent’s source would violate the stated authority boundary.
• Private or held evidence may be exposed through an overly broad public route.

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:independent-review
• Observed native contract: PointGuard persistent cross-app context surface; specialist apps remain execution and canonical-record owners.
• Observed native contract: Notebook records preserve canonical IDs, provenance, source locators, source SHA-256, revisions, lifecycle, tags, links, attachments, and record revisions.
• Observed native contract: Notebook approvals support Needs review, Approved, and Held states with receipts.
• Observed native contract: current GuthHub routes are local prototypes or indexes; provider, credential, database, customer, publication, and production effects are held.
• observed_native_contract.records
• observed_native_contract.pointguard
• observed_native_contract.web_boundary
• app:/app/pointguard/
• app:/app/notebook/agent-logs/
• app:/app/notebook/approvals/
• app:/app/notebook/notes/
• app:/app/notebook/files/
• app:/app/notebook/field-guides/
• app:/app/notebook/search/
• allowed_instrument:checksum-verifier
• allowed_instrument:binary-text-diff-similarity-ratio
• allowed_instrument:url-query-string-parser