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

field guide / candidate

# iOS 27 — forms

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

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

## Record status

**Record ID**: field-guide:ios-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 request

Define exactly what native capability is being assessed without assuming that the named platform or surface exists in production.

- request_title

- capability_description

- requesting_agent

- owner_agent

- related_job_ids

- intended_user_outcome

- in_scope_claims

- out_of_scope_claims

- target_platform_statement

- known_dependencies

### Source binding

Attach the supplied source record and identify the evidence boundary.

- source_record_id

- source_record_type

- source_refs

- source_locator

- source_sha256

- provenance_note

- record_revision

- evidence_status

### Observed contract comparison

Compare the request with observed Guth native contracts and identify unverified assumptions.

- relevant_native_contracts

- specialist_app_owner

- canonical_record_owner

- PointGuard_context_needed

- prototype_or_index_route

- held_effects

- assumptions_to_test

### Workback and deadlines

Create explicit review timing and human checkpoints.

- start_at

- evidence_due_at

- implementation_review_due_at

- approval_due_at

- follow_up_at

- priority

- recurrence_candidate

- review_owner

### Qualification result

Record a bounded outcome and its supporting evidence.

- result_status

- supported_statement

- unsupported_statement

- evidence_record_ids

- failure_branch_taken

- accessibility_check

- acceptance_test_results

- reviewer

- approval_record_id

### 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 claim boundary

Define the iOS or SwiftUI capability being investigated without implying a connected or production feature.

- capability name

- target Apple surface

- problem to solve

- supported device or OS assumptions

- proposal status

- claims explicitly held

- owner agent

- source locator

### Evidence and provenance

Preserve source-backed implementation evidence and distinguish native surface names from verified web or provider behavior.

- source URL or locator

- source SHA-256

- observation date

- native contract reference

- record revision

- linked notes

- known gaps

- provenance confidence

### Implementation plan

Turn discovery into bounded, reviewable Swift and SwiftUI work.

- implementation slice

- canonical record owner

- PointGuard context

- required state transitions

- accessibility behavior

- failure states

- offline or held behavior

- test evidence

- rollback or hold condition

### Qualification and review

Require human review before any capability, integration, or publication claim is treated as accepted.

- acceptance tests

- reviewer

- approval state

- receipt link

- device or simulator matrix

- external effects held

- publication held

- follow-up due date

## Required or proposed record references

No record existence is asserted by this documentation page.

- source-bound field-guide record for field-guide:ios-27:plan

- evidence notes with source locators and source SHA-256 where available

- related job records for Swift and SwiftUI implementation, Apple platform discovery, App Intents and Spotlight, Cross-device product families, and Native capability qualification

- local todo records for each review step with dueAt, priority, completion state, tags, and revisions

- approval record marked Needs review, Approved, or Held before any qualification claim

- field-guide:ios-27

- project:swift-and-swiftui-implementation

- project:apple-platform-discovery

- project:app-intents-and-spotlight

- project:cross-device-product-families

- project:native-capability-qualification

- source-labelled implementation notes

- approval records for capability claims

- to-dos with explicit due dates and review state

## Sources and evidence

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

- `source_record:field-guide:ios-27`

- `agents/index.html#tim`

- `field-guide:ios-27`

- `OBSERVED_NATIVE_CONTRACT`

- `APP_ROUTES`

- `ALLOWED_INSTRUMENTS`