Page actions
field guide / candidate
iPadOS 27 — related jobs
The distinct related jobs record for iPadOS 27. This page is proposal-only.
Status: proposedLifecycle: 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 — Inspect the guide and persist local checkpoints. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held.
Related Agent job handoffs
Handoff record requirements
The guide may supply evidence, checkpoints, and failure context to a job. The receiving job retains ownership and must record its own decision, approval, and receipt.
- 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
Ownership boundary
The guide supports these jobs without importing their package descriptions, becoming the job owner, or gaining independent authority.
- 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-27agents/index.html#timsource record field-guide:ipados-27:planObserved native contract: project_and_field_guide_collectionsObserved native contract: deadlinesObserved native contract: recordsObserved native contract: pointguardApp 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/