Page actions
job / candidate
Cross-device product families — field guides
The distinct field guides record for Cross-device product families. This page is proposal-only.
Status: proposedLifecycle: candidate
Record status
- Record ID
- job:tim:cross-device-product-families
- Parent lifecycle
- candidate
- Page lane
- docs_urls
- Lane lifecycle
- proposed
- Owner
- Tim
- Owner role
- Apple platform specialist
- Owner status
- PACKAGING
- Qualification result
- NOT RUN · held for evidence and human review
Working browser surface: Agent jobs — builder overview — Inspect the package and stage a local project. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held.
Related field-guide records
- /app/notebook/field-guides/
Source-proposed guide paths are references, not proof that those paths resolve.
Operating sequence
- Create or update the canonical job record and declare the authorized Apple-file scope.
- Create a cross-device product-family project and link the job, source notes, capability records, and review to-dos.
- Capture source-labelled evidence for each proposed Apple capability, including locator, SHA-256, provenance, revision, and lifecycle.
- Separate observed native contract from proposed web or production behavior; mark unverified API availability and all external effects as held.
- Map the shared user goal across iPhone, iPad, and Mac, documenting platform-specific interaction, accessibility, continuity, and failure behavior.
- Identify entitlement, credential, Store submission, provider, database, customer-indexing, and publication gates.
- Draft a reusable field guide with prerequisites, bounded steps, expected receipts, and escalation conditions.
- Run deterministic acceptance tests against the records, links, authority boundaries, and held states.
- Submit the package to Notebook Approvals for human review; preserve the decision and receipt.
- Record the final proposal revision in Agent Logs and hand off only the approved local guidance.
Handoff boundary
- A capability name may be mistaken for a connected or currently available API.
- Apple platform versions, entitlements, and framework behavior may change; source revision and date context must remain visible.
- Cross-device parity can erase platform-specific interaction and accessibility needs.
- Spotlight indexing, App Intents, Apple Intelligence, provider access, credentials, databases, customer records, and Store submission are production-sensitive and held.
- Unauthorized Apple files or undocumented source material may exceed the job boundary.
- A proposed handoff may be mistaken for implementation, deployment, or qualification.
- Local prototype routes do not prove connected web behavior.
- Sensitive source files or credentials must not be uploaded or stored through this package without an explicitly authorized surface.
Sources and evidence
These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.
agents/index.html#timsource_record:job:tim:cross-device-product-familiesjob:tim:cross-device-product-familiesObserved native contract: project_and_field_guide_collectionsObserved native contract: deadlinesObserved native contract: recordsObserved native contract: pointguardObserved app routes: /app/notebook/projects/Observed app routes: /app/notebook/field-guides/Observed app routes: /app/notebook/approvals/Observed app routes: /app/notebook/agent-logs/Observed app routes: /app/pointguard/