Liquid Glass — examples

The distinct examples record for Liquid Glass. This page is proposal-only.

Status: proposedLifecycle: candidate

Record status

Record ID: field-guide:liquid-glass
Parent lifecycle: candidate
Page lane: plan
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.

Hypothetical scenarios

A reviewer opens the Liquid Glass guide for bounded local rehearsals. Every fixture uses invented placeholders, performs no provider or external action, and remains held until source evidence and human review are recorded.

1. Guided inquiry fixture

A reviewer records a bounded question, links only supplied source references, and marks every unanswered point Needs review.

Fixture ID: liquid-glass-example-001
Evidence: Hypothetical source placeholders only
Decision: HELD · human review required
External effects: None

2. Source comparison fixture

A reviewer compares two hypothetical source locators, preserves disagreement, and holds any conclusion until provenance is supplied.

Fixture ID: liquid-glass-example-002
Evidence: Hypothetical source placeholders only
Decision: HELD · human review required
External effects: None

3. Uncertainty and pathway fixture

A reviewer constructs a local procedure or study pathway with checkpoints while labelling uncertainty and leaving external effects Held.

Fixture ID: liquid-glass-example-003
Evidence: Hypothetical source placeholders only
Decision: HELD · human review required
External effects: None

4. Potentially allowed claim fixture

A hypothetical claim may advance only when its exact evidence locator, scope, reviewer, and decision rationale are recorded; this fixture asserts no fact.

Fixture ID: liquid-glass-example-004
Evidence: Hypothetical source placeholders only
Decision: HELD · human review required
External effects: None

5. Held claim fixture

A hypothetical unsupported claim remains Held with missing evidence and human-review rationale visible; it is not published or indexed.

Fixture ID: liquid-glass-example-005
Evidence: Hypothetical source placeholders only
Decision: HELD · human review required
External effects: None

Filled example fields

Scope and source boundary fixture

Define what is being investigated while preventing unsupported claims about native or production behavior.

objective: Example value to be supplied and reviewed
in-scope related jobs: Example value to be supplied and reviewed
out-of-scope effects: Example value to be supplied and reviewed
source record ID: fixture-source-001 (hypothetical; no external claim)
owner agent: Named human or Agent owner required
source locator: fixture-source-001 (hypothetical; no external claim)

Capability hypothesis fixture

Describe the proposed Liquid Glass capability and the user-visible problem without treating the hypothesis as an existing feature.

capability hypothesis: Example value to be supplied and reviewed
target Apple surface: Example value to be supplied and reviewed
Swift or SwiftUI touchpoint: Example value to be supplied and reviewed
cross-device consideration: Example value to be supplied and reviewed
App Intents or Spotlight consideration: Example value to be supplied and reviewed
expected user benefit: Example value to be supplied and reviewed

Evidence and observations fixture

Capture reproducible observations and distinguish source facts from proposal and open questions.

observation ID: Example value to be supplied and reviewed
device or environment label: Example value to be supplied and reviewed
OS or SDK label if known: Example value to be supplied and reviewed
reproduction steps: Example value to be supplied and reviewed
observed result: Held — pending human review
expected result: Held — pending human review

Review questions

A source-labelled field-guide record exists with owner Tim, related jobs, provenance, revision, and lifecycle recorded.
The capability under review has a stated platform, scope, local reproduction, expected result, actual result, and failure state.
Every linked file is a local reference with inspectable type and size; no hidden upload or protected-storage claim is made.
At least one explicit accessibility review records contrast inputs, instrument output, text scaling, VoiceOver order, focus behavior, and fallback or reduced-transparency behavior.
The wcag-contrast-ratio-checker result is preserved with its inputs and is not represented as full accessibility approval.
A to-do exists with owner, due date, priority, workback checkpoint, and completion or held state.
Approval remains Needs review, Approved, or Held with a local receipt and reviewer identity.
Agent Logs identify authority boundaries and do not claim deployment, provider connection, database authority, customer indexing, publication, or qualification beyond recorded evidence.

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
App route: /app/notebook/field-guides/
App route: /app/pointguard/
App route: /app/notebook/notes/
App route: /app/notebook/files/
App route: /app/notebook/to-dos/
App route: /app/notebook/approvals/
App route: /app/notebook/agent-logs/
Allowed instrument directory: wcag-contrast-ratio-checker
Observed native contract: records preserve canonical IDs, provenance, revisions, lifecycle, tags, links, attachments, and record revisions
Observed native contract: PointGuard is a persistent cross-app context surface and specialist apps remain execution and canonical-record owners
Observed native contract: current GuthHub app routes are local prototypes or indexes and provider, credential, database, customer, publication, and production effects are held