iOS 27 — prerequisites

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 — 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-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

Intended operators and ownership

• Tim
• Apple platform discovery agents
• Swift and SwiftUI implementation agents
• App Intents and Spotlight agents
• Cross-device product family reviewers
• Native capability qualification reviewers

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

Conditions that hold the guide before entry

• Treating the title iOS 27 as evidence of a specific operating-system feature or availability.
• Treating a named native surface, app route, App Intent, Spotlight reference, or interface as proof of a connected web feature.
• Confusing a local prototype or index with deployment, production state, provider connection, credential access, database authority, customer indexing, or publication.
• Assigning execution or canonical-record ownership to PointGuard when the observed contract assigns those responsibilities to specialist apps.
• Using unsupported external claims, unlabeled files, or inferred behavior as evidence.
• Allowing an Agent to approve its own qualification without a human approval record.
• Turning deadlines or recurrence fields into hidden automation or external side effects.
• Publishing distinct doorway pages or keyword-focused documentation without useful source-bound content.
• Failing to preserve source locators, provenance, revisions, or source hashes, making later review non-reproducible.
• Presenting educational or prototype calculations as operational, legal, medical, financial, or production advice.

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