Source: https://guthlabs.ai/docs/jobs/tilly-website-claim-review/qualification/ job / candidate # Website claim review โ€” qualification The distinct qualification record for Website claim review. This page is proposal-only. Status: **proposed**Lifecycle: **candidate** ## Record status **Record ID**: job:tilly:website-claim-review **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 No verified instrument is assigned to this qualification lane. ## 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. - A review cannot qualify unless claim_text, claim_owner, reviewer, source_record_id, source_locator, source_sha256, and review_requested_at are present. - A claim passes the source test only when every material factual clause maps to an inspectable source excerpt and locator. - A claim fails when its citation is missing, malformed, inaccessible, unrelated, or only a doorway page with no useful supporting content. - A claim fails the authority test when the source owner or publisher is absent, the source is outside the claimed authority, or Tilly is asked to approve her own evidence. - A claim fails the chronology test when relevant dates are missing, inconsistent, future-dated without explicit basis, or the source predates a time-sensitive claim without a valid update. - A claim fails the privacy test when it exposes personal, confidential, credential, protected-storage, or customer information beyond the declared audience; redact and hold instead. - A claim fails the accessibility test when its meaning depends on color, image-only evidence, inaccessible controls, missing labels, missing text alternatives, or an unreviewable document format. - A negative test with a removed citation must produce Needs review or Held, never Qualified. - A negative test with contradictory sources must preserve both source references, identify the contradiction, and produce Held until an independent authority resolves it. - A negative test with a changed source SHA-256 or revision must invalidate the prior qualification and require re-review. - A qualified result must state claim scope, evidence basis, limitations, reviewer, independent approver, and receipt IDs. - Qualification must not trigger publication, external sending, provider writes, database writes, customer indexing, funding commitments, credential access, or source mutation. - The record must be keyboard-operable in the intended interface, expose visible focus, use labelled fields, provide text status for every decision, and avoid relying on color alone. - All rejected or held cases must retain a failure reason, failing test, next action, owner, and dueAt value. ## Negative and held-state tests - A source locator may be mistaken for proof that a connected web feature exists. - A local prototype route may be mistaken for deployed publication or provider capability. - A citation may support only part of a compound claim. - Stale or contradictory evidence may be presented as current fact. - Tilly may be pressured to approve her own evidence despite the never-rule. - Private or customer information may leak into a public claim or search index. - Image-only or color-dependent evidence may exclude reviewers or readers. - A held result may be incorrectly converted into a public claim. - A source revision may invalidate an earlier qualification without triggering re-review. - An inaccessible or missing source may be replaced by an unsupported summary. ## Qualification claim boundary ### Potentially allowed only after the stated evidence - The website claim is proposed for review. - The claim has a recorded source locator and evidence excerpt, if those fields pass their tests. - The review is Needs review, Approved locally, or Held when that exact recorded state is supported by receipts. - The package defines reviewer boundaries and does not authorize publication. ### Still held - That the claim is true, current, published, deployed, indexed, or customer-visible. - That Tilly approved final publication or her own evidence. - That any provider, credential, database, customer index, or production effect is connected. - That a source proves more than its recorded excerpt and scope. - That qualification grants funding, credentials, authority, or permission to alter another agent's source. ## 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:website-claim-review` - `Observed native contract: Notebook records preserve canonical IDs, source locators, source SHA-256, provenance, revisions, lifecycle, tags, links, attachments, and record revisions.` - `Observed native contract: PointGuard is a persistent cross-app context surface; specialist apps remain execution and canonical-record owners.` - `Observed app route: /app/pointguard/` - `Observed app route: /app/notebook/approvals/` - `Observed app route: /app/notebook/agent-logs/` - `Observed app route: /app/notebook/files/` - `Observed app route: /app/notebook/field-guides/` - `Observed app route: /app/notebook/search/`