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

field guide / candidate

# iPadOS 27 — prerequisites

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

## Entry evidence and required records

Before the procedure starts, an operator must identify the source, owner, scope, and required records below. Missing evidence holds the guide.

- 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

## Intended operators and ownership

- Tim

- Apple platform discovery owners

- Swift and SwiftUI implementation owners

- App Intents and Spotlight owners

- Cross-device product family owners

- Native capability qualification reviewers

Being listed as an intended operator does not grant execution or publication authority.

## Conditions that hold the guide before entry

- Confusing the iPadOS 27 title or related job names with verified platform behavior.

- Treating a named native surface as evidence that a connected web feature exists.

- Inferring SwiftUI, App Intents, Spotlight, or cross-device behavior not present in the supplied source record.

- Assigning canonical ownership to PointGuard instead of the specialist app.

- Creating doorway documentation URLs with no distinct useful content.

- Losing source locators, hashes, provenance, or revisions when copying evidence.

- Scheduling external writes, provider actions, publication, customer indexing, or deployment as if they were available.

- Using unsupported claims as acceptance evidence.

- Skipping accessibility or failing to provide a non-gesture or non-color equivalent.

- Allowing an Agent proposal to bypass human review or approval receipts.

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