Page actions
job / candidate
Evidence reconciliation — qualification
The distinct qualification record for Evidence reconciliation. This page is proposal-only.
Record status
- Record ID
- job:tilly:evidence-reconciliation
- Parent lifecycle
- candidate
- Page lane
- qualification
- 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.
Qualification status
- Result
- NOT RUN
- Disposition
- HELD
- Reviewer
- Not recorded
- Receipt
- Not recorded
This page defines proposed acceptance criteria for the qualification lane. It does not execute tests, establish compliance, qualify the subject, or authorize an effect.
Lane-specific instrument aids
Outcome definitions
- Verified
- All stated evidence and acceptance requirements passed for the exact reviewed revision; this still does not authorize deployment or an external effect.
- Failed
- One or more deterministic acceptance requirements failed with an inspectable reason.
- Needs review
- Evidence or interpretation is incomplete, conflicting, or awaits an identified human reviewer.
- Held
- Authority, required evidence, safe execution conditions, or a principal gate is absent.
The current record remains NOT RUN / HELD. These definitions describe candidate outcomes only.
Proposed deterministic acceptance tests
Route-resolution and distinct-content checks apply only to the admitted canonical routes in this record. Held source-proposed extensions are non-resolving proposals and are excluded.
- Deterministic qualification passes only when every material claim segment maps to an identified source receipt, all receipts have locators and provenance, no contradiction remains unresolved, chronology is compatible, authority is explicitly recorded, privacy boundaries pass, accessibility checks pass, and an independent reviewer disposition exists.
- A claim with no receipt, a receipt with a missing locator, or a mismatched SHA-256 fails source integrity and is Held from publication.
- A source that conflicts with another source produces a Contradiction result listing both record IDs, revisions, relevant text, and required resolution; the claim cannot pass while unresolved.
- A claim whose asserted date precedes its source date, or whose evidence revisions postdate the reviewed snapshot without rerunning, fails chronology.
- A source owned by another agent may be examined but cannot be changed by Tilly; attempted mutation is a failure and must create a held receipt.
- Tilly cannot set her own review decision to Approved; self-approval is rejected and routed to independent review.
- Private, restricted, or held records are excluded from public-claim evidence unless an explicit visibility authorization record exists; absence of authorization is a privacy failure.
- The form is keyboard navigable, has visible labels, programmatic error associations, non-color-only status indicators, logical heading order, and a text alternative for every status or receipt summary.
- Invalid dates, empty claim text, missing owner, duplicate evidence IDs, malformed locators, and oversized or unsupported file references produce actionable inline errors without discarding entered data.
- If a source, instrument, route, or approval surface is unavailable, the job records Held with the attempted action and next owner; it must not silently substitute an unverified provider or claim deployment.
- Acceptance does not assert that any provider, database, customer index, publication route, credential, or production feature is connected.
Negative and held-state tests
- A named native surface may be mistaken for a connected web feature; all external effects remain held.
- Tilly may accidentally become both evidence reviewer and approver.
- A citation may exist while failing to support the precise claim wording.
- Contradictory revisions may be hidden by using only the latest or easiest receipt.
- Private attachments or source metadata may leak into a public claim package.
- Missing dates can create false chronology confidence.
- Instrument output may be treated as authoritative evidence rather than an educational calculation.
- Accessibility failures may prevent reviewers from seeing held, failed, or contradictory states.
- A failed provider or unavailable route may be mistaken for a negative evidence result.
- Duplicate documentation could create doorway pages rather than distinct useful content.
Qualification claim boundary
Potentially allowed only after the stated evidence
- A proposal may state that the job is designed to reconcile claims against source-labelled receipts.
- A proposal may state that unresolved contradictions, missing authority, failed source checks, privacy failures, and absent independent approval remain Held.
- A proposal may identify the allowed instrument slugs as optional educational verification aids, with their limitations.
- A proposal may expose a review result only after an independent approval record explicitly authorizes that visibility.
Still held
- Any claim that Tilly has qualified evidence or approved a publication.
- Any claim that a source, provider, database, credential, customer index, or publication route is connected or authoritative in production.
- Any claim that an instrument result proves a real-world fact, authority, deployment, or customer outcome.
- Any external send, funding commitment, credential grant, source mutation, or final publication.
- Any unsupported statement that a native app route is a live connected web feature.
Sources and evidence
These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.
agents/index.html#tillysource_record:job:tilly:evidence-reconciliationOBSERVED_NATIVE_CONTRACT.recordsOBSERVED_NATIVE_CONTRACT.pointguardOBSERVED_NATIVE_CONTRACT.deadlinesAPP_ROUTES:/app/pointguard/APP_ROUTES:/app/notebook/approvals/APP_ROUTES:/app/notebook/field-guides/APP_ROUTES:/app/notebook/agent-logs/ALLOWED_INSTRUMENTS:checksum-verifierALLOWED_INSTRUMENTS:date-duration-calculator