iOS 27 — steps

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.

Ordered procedure

1. Create or open the field-guide record at /app/notebook/field-guides/ and preserve candidate_id field-guide:ios-27:plan.
2. Record the request as a proposal, including the exact capability being considered and the intended user outcome. Do not convert the title iOS 27 into a claim about platform behavior.
3. Link the supplied source record field-guide:ios-27 and source reference agents/index.html#tim. Preserve the source locator, provenance, revision, and source SHA-256 when those values are available in the record.
4. List the related jobs exactly as supplied: Swift and SwiftUI implementation; Apple platform discovery; App Intents and Spotlight; Cross-device product families; Native capability qualification.
5. Identify the specialist application that would own execution and the canonical record. Treat PointGuard only as a persistent cross-app context surface, not as proof of native execution or data authority.
6. Compare the request with the observed contract. Mark every statement about provider connection, credentials, databases, customers, publication, production effects, App Intents, Spotlight indexing, or deployment as unverified or held unless supported by a source record.
7. Create local todo records for evidence collection, implementation review, accessibility review, and human approval. Assign explicit dueAt values and owners; do not imply that a scheduled item performs work automatically.
8. Collect source-labelled evidence in Notebook Notes or Files. Each evidence item must identify its source locator, provenance, revision, and custody state. Do not use an unlabeled screenshot, external claim, or inferred production state as qualification evidence.
9. If a native surface or route is named, record it as a proposed inspection target only. A route or interface name does not establish a connected web feature or native operating-system integration.
10. If a candidate implementation is discussed, describe it as local prototype work owned by the relevant specialist app. Keep external writes, provider effects, protected storage, publication, and customer-facing effects held for human review.
11. Run the accessibility review against the proposed form and procedure: labeled controls, keyboard or assistive-technology reachability, visible focus, non-color-only status, readable error text, and a usable failure path. Record observations rather than claiming compliance without evidence.
12. Run deterministic acceptance tests for record binding, ownership, lifecycle, evidence traceability, deadline visibility, held effects, and failure-state handling.
13. Create an approval record at /app/notebook/approvals/ with status Needs review. Only a human reviewer may change it to Approved; otherwise keep the guide Held.
14. Write the bounded result into the field-guide record and link all evidence, todos, related jobs, and approval receipts. Completion means the review package is complete, not that iOS 27 support or deployment exists.

Deadline and chronology rules

• Set an evidence dueAt before the implementation review dueAt.
• Set an approval dueAt after evidence and accessibility review are complete.
• Every incomplete todo must have an owner, priority, and dueAt.
• If a deadline passes without required evidence, mark the related step Held or Needs review; do not mark it complete.
• Use recurrenceCandidate only for a deliberate repeat review; it must not be treated as hidden automation.
• Do not schedule or claim external writes, provider actions, publication, deployment, customer indexing, or production qualification.

Failure branches during execution

• 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