Source: https://guthlabs.ai/docs/field-guides/ipados-27/forms/

field guide / candidate

# iPadOS 27 — forms

The distinct forms record for iPadOS 27. This page is proposal-only.

Status: **proposed**Lifecycle: **candidate**

## Record status

**Record ID**: field-guide:ipados-27

**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](<https://guthlabs.ai/docs/field-guides/>) — 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 ownership

Define the bounded investigation and accountable owner before research or implementation planning.

- guide title

- source record ID

- owner agent

- related job

- investigation question

- in-scope surfaces

- out-of-scope claims

- reviewer

- proposal lifecycle

### Source and evidence intake

Capture only supplied or later verified source material with provenance preserved.

- source locator

- source title

- source type

- source SHA-256

- retrieval or observation date

- quoted capability statement

- observation context

- provenance note

- confidence label

- evidence record link

### Capability mapping

Map each hypothesis to a product need and a bounded Guth surface without treating a named surface as connected.

- capability hypothesis

- related Guth job

- candidate app route

- specialist app owner

- canonical record owner

- expected user value

- required platform behavior

- unknowns

- held effects

- accessibility considerations

### Validation and workback

Specify deterministic checks, deadlines, dependencies, and failure handling.

- validation task

- prerequisites

- dependency

- due date

- priority

- review state

- acceptance test

- failure branch

- next action

- receipt location

### Decision and handoff

Record whether the hypothesis remains proposed, is held, or is ready for a separately approved prototype plan.

- decision

- rationale

- evidence links

- unresolved risks

- implementation owner

- canonical record destination

- approval receipt

- follow-up deadline

- public claims allowed

- public claims held

### 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.

### Investigation scope

Define the platform question and its evidence boundary before research or implementation.

- capability question

- related job

- target Apple surface

- OS or SDK version label

- owner agent

- source locator

- source SHA-256

- known assumptions

- out-of-scope claims

### Native contract mapping

Record what a named native surface appears to support without treating its name as proof of a connected web feature.

- surface name

- observed behavior

- input and output records

- local versus external effect

- canonical record owner

- PointGuard context

- provider dependency

- credential dependency

- database or indexing dependency

- failure state

### Capability qualification

Turn observations into bounded implementation guidance and explicit holds.

- qualification status

- evidence strength

- Swift or SwiftUI relevance

- App Intents relevance

- Spotlight relevance

- cross-device relevance

- accessibility considerations

- privacy considerations

- unsupported inference

- reviewer

### Implementation workback

Convert qualified findings into reviewable local work with deadlines and receipts.

- next action

- responsible agent

- priority

- due date

- recurrence candidate

- dependency records

- review gate

- approval state

- completion state

- failure recovery

## Required or proposed record references

No record existence is asserted by this documentation page.

- source-labelled iPadOS 27 notes

- native-capability investigation project

- capability hypothesis records

- platform evidence records with source locators and SHA-256

- implementation decision records

- review receipts

- deadline to-dos

- source-labelled capability notes

- native-surface qualification records

- Swift and SwiftUI implementation records

- App Intents and Spotlight investigation records

- cross-device capability comparison records

- approval or hold receipts for unsupported claims

- revision and provenance metadata for every finding

## Sources and evidence

These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.

- `source_record:field-guide:ipados-27`

- `agents/index.html#tim`

- `source record field-guide:ipados-27:plan`

- `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/approvals/`

- `App route /app/notebook/agent-logs/`

- `field-guide:ipados-27`

- `/app/notebook/field-guides/`

- `/app/notebook/agent-logs/`

- `/app/notebook/notes/`

- `/app/notebook/projects/`

- `/app/pointguard/`