Guth
NewsDocs
Page actions
View as Markdown ↗
Explore MCP tools ↗

field guide / candidate

Liquid Glass — forms

The distinct forms 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.

Proposed form sections

Each section is a candidate schema for inspectable records. Required-field presence does not establish factual truth.

Scope and source boundary

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

  • objective
  • in-scope related jobs
  • out-of-scope effects
  • source record ID
  • owner agent
  • source locator
  • source SHA-256
  • provenance note

Capability hypothesis

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

  • capability hypothesis
  • target Apple surface
  • Swift or SwiftUI touchpoint
  • cross-device consideration
  • App Intents or Spotlight consideration
  • expected user benefit
  • assumptions
  • unknowns

Evidence and observations

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

  • observation ID
  • device or environment label
  • OS or SDK label if known
  • reproduction steps
  • observed result
  • expected result
  • artifact reference
  • source locator
  • confidence
  • accessibility observation

Qualification decision

Record whether the capability is ready for a bounded prototype, needs more evidence, or remains held.

  • decision state
  • supporting evidence IDs
  • native ownership boundary
  • specialist app owner
  • PointGuard context
  • failure conditions
  • reviewer
  • review date
  • decision rationale

Workback and review

Create explicit human-review tasks and deadlines using Notebook's bounded todo contract.

  • task title
  • owner
  • priority
  • dueAt
  • dependency
  • recurrenceCandidate
  • completion state
  • review signal
  • blocked reason

Accessible state contract

  • Every field requires a visible and programmatic label.
  • Required and optional fields must be stated in text.
  • Invalid entries require an actionable message linked to the field.
  • Blocked and Held states remain visible without relying on color alone.

Supporting documentation fields

These fields come from the tools lane and remain separate from the primary operating form.

Scope and native surface

Define the Apple-platform capability being investigated without treating a named native surface as proof of a connected web feature.

  • target platform
  • target OS or SDK version
  • Swift or SwiftUI surface
  • capability under review
  • related job
  • owner agent
  • source locator
  • source SHA-256
  • provenance label
  • lifecycle

Evidence and implementation state

Capture reproducible local evidence and distinguish notes, prototypes, indexes, and held effects.

  • evidence description
  • local reproduction steps
  • record IDs
  • linked files
  • revision identifier
  • observed behavior
  • unsupported assumption to avoid
  • current state: proposed/indexed/prototype/held

Capability qualification

Review whether the native capability is useful, available, and bounded for the intended product family.

  • capability inputs
  • expected output
  • device or platform constraints
  • privacy considerations
  • offline behavior
  • failure state
  • human-review requirement
  • acceptance test result
  • qualification decision

Accessibility and interface review

Check visual and interaction requirements before local approval.

  • contrast inputs
  • text and control labels
  • Dynamic Type behavior
  • VoiceOver reading order
  • keyboard or switch navigation
  • reduced-transparency behavior
  • motion sensitivity considerations
  • focus and error states
  • reviewer receipt

Handoff and approval

Preserve ownership, deadlines, revisions, and explicit held states for follow-up work.

  • next action
  • record owner
  • reviewer
  • due date
  • priority
  • recurrence candidate
  • approval state
  • receipt link
  • blocker
  • handoff notes

Required or proposed record references

No record existence is asserted by this documentation page.

  • field-guide:liquid-glass
  • source-labelled notes for platform observations
  • source-labelled file references for captured artifacts
  • to-dos with dueAt and priority
  • approval record for any qualification decision
  • agent-log receipt for Tim's work
  • source-labelled implementation note
  • field-guide record
  • native capability qualification record
  • accessibility review record
  • approval record
  • agent-log receipt
  • linked local file references where applicable

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