Source: https://guthlabs.ai/docs/field-guides/liquid-glass/qualification/ field guide / candidate # Liquid Glass โ€” qualification The distinct qualification record for Liquid Glass. This page is proposal-only. Status: **proposed**Lifecycle: **candidate** ## Record status **Record ID**: field-guide:liquid-glass **Parent lifecycle**: candidate **Page lane**: docs_urls **Lane lifecycle**: proposed **Owner**: Tim **Owner role**: Not separately recorded **Owner status**: Not separately recorded **Qualification result**: NOT RUN ยท held for evidence and human review **Working browser surface:** [Field guides โ€” documentation]() โ€” Inspect the guide and persist local checkpoints. 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 docs_urls 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. - The overview route states that the guide is proposed and distinguishes observations from verified capability claims. - Each listed documentation route has a unique title, search intent, and substantive content; no route is a doorway or keyword variant. - The steps page presents an ordered workback with prerequisites, dependencies, failure states, and review points. - The tools page names only supplied native surfaces or the supplied source owner and does not claim connection or deployment. - The forms page includes scope, provenance, qualification, implementation, and publication fields with accessible labels and explicit required-state handling. - The examples page contains bounded hypothetical examples labelled as examples, not production evidence or customer results. - The qualification page provides separate states for verified, failed, needs review, and held; it never equates a named native surface with a connected web feature. - The related-jobs page links only to the five supplied related jobs and explains the distinct documentation value of each. - Private, prototype, indexed, and held boundaries are visible in record metadata and page copy. - A keyboard-only user can reach every form control, route link, status label, and failure message in logical order. - Validation prevents publication or qualification when required provenance, lifecycle, owner, or review fields are absent. - Acceptance checks preserve canonical IDs, source locators, revisions, lifecycle, and record ownership. - No page claims deployment, provider connection, credential use, database authority, customer indexing, publication, or native capability approval. ## Negative and held-state tests - A native surface name may be mistaken for an implemented or connected web feature. - Apple platform behavior, availability, and APIs may vary; unsupported assumptions can become misleading documentation. - App Intents and Spotlight descriptions can imply system indexing or execution when only a design proposal exists. - Cross-device language can conceal device-specific constraints, synchronization assumptions, or unclear record ownership. - Liquid Glass styling can become visual-only guidance without an accessible interaction model or fallback states. - Prototype routes may be mistaken for production routes or public documentation. - Unverified examples may be read as customer evidence or deployment proof. - Missing provenance, revision, or source locators can make qualification irreproducible. - External sends, provider writes, uploads, protected storage, and database effects remain held by the observed contract. - Medical, financial, legal, safety, or production engineering decisions must not be inferred from this product guide. ## Qualification claim boundary ### Potentially allowed only after the stated evidence - This is a proposed field guide for documenting and qualifying Liquid Glass-related work. - The guide covers supplied related jobs: Swift and SwiftUI implementation, Apple platform discovery, App Intents and Spotlight, cross-device product families, and native capability qualification. - The guide can define crawlable documentation routes with distinct purposes and lifecycle labels. - The observed contract includes Notebook field-guide collections, source-labelled records, deadline fields, PointGuard context, and prototype or indexed app surfaces. - The supplied verified-instrument directory contains tools, although none is required for this guide. ### Still held - Liquid Glass implementation is deployed or production-ready. - Any Apple platform, App Intents, Spotlight, or cross-device capability is connected, approved, indexed, or available to customers. - A provider, credential, database, customer record, publication system, or external service is connected. - The named agent Tim has execution authority beyond the supplied source ownership reference. - Any example represents measured production behavior, customer outcome, or completed qualification. - Any prototype or indexed app route is a live public web feature. - The guide provides authoritative Apple platform guidance without a verified source record for each claim. ## Sources and evidence These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment. - `source_record:field-guide:liquid-glass` - `agents/index.html#tim` - `field-guide:liquid-glass` - `Observed native contract: project_and_field_guide_collections` - `Observed native contract: deadlines` - `Observed native contract: records` - `Observed native contract: pointguard` - `Observed native contract: web_boundary`