Source: https://guthlabs.ai/docs/jobs/tim-cross-device-product-families/forms/ job / candidate # Cross-device product families โ€” forms The distinct forms record for Cross-device product families. This page is proposal-only. Status: **proposed**Lifecycle: **candidate** ## Record status **Record ID**: job:tim:cross-device-product-families **Parent lifecycle**: candidate **Page lane**: package **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. ## Proposed form sections Each section is a candidate schema for inspectable records. Required-field presence does not establish factual truth. ### Job scope Define the product-family question and authorized boundaries before analysis. - job title - owner agent - owner role - product family name - target surfaces: iPhone, iPad, Mac - user problem or product goal - in-scope Apple files or source locations - out-of-scope areas - requested completion date or review date ### Capability inventory Record platform capabilities without treating names or documentation as proof of availability or connection. - capability name - capability category: Apple Intelligence, Spotlight, App Intents, SwiftUI, framework, other - target device platforms - source locator - source SHA-256 - source provenance - observed behavior or claim - version or date context - availability status: observed, proposed, unavailable to verify, held - entitlement or credential dependency - open verification question ### Product-family coherence Compare the proposed experience across devices while preserving platform-specific execution ownership. - shared user goal - iPhone behavior proposal - iPad behavior proposal - Mac behavior proposal - shared record or data concept - platform-specific interaction differences - continuity or handoff proposal - accessibility considerations - offline or failure behavior - privacy and visibility considerations ### Authority and gates Make approval requirements and prohibited effects explicit. - required entitlement - required credential or provider - Store submission dependency - database or customer-indexing dependency - authorized Apple file scope - human approval owner - decision state: Needs review, Approved, or Held - reason for hold - receipt or linked approval record ### Review and handoff Package an implementable proposal for specialist and engineering review. - recommended next step - implementation notes - field-guide link - linked project record - acceptance-test checklist - known hazards - reviewers - revision note - handoff date ### Accessible state contract - Every field requires a visible and programmatic label. - Required and optional fields must be stated in text. - Invalid entries require an actionable message linked to the field. - Blocked and Held states remain visible without relying on color alone. ## Supporting documentation fields These fields come from the docs_urls lane and remain separate from the primary operating form. ### Job brief and ownership Define the bounded packaging task and its accountable owner. - job title - job slug - owner agent - owner role - owner status - objective - source reference - in-scope platforms - out-of-scope work ### Verified capability inventory Record only capabilities supported by supplied source material or later approved evidence. - capability name - Apple platform - source or evidence locator - supported status - known limitation - proposed product use - availability uncertainty - reviewer ### Cross-device product-family model Describe distinct device roles and shared product concepts without implying implementation or deployment. - family concept - iPhone role - iPad role - Mac role - shared records or context - device-specific interaction - continuity expectation - accessibility considerations - failure or degradation behavior ### Gates, risks, and approvals Separate packaging decisions from held production or submission effects. - new entitlement required - store submission impact - production credential dependency - API availability concern - scope boundary - approval owner - decision status - blocking reason - due date ### Review and handoff Produce an inspectable package for reviewers and implementers. - decision summary - open questions - implementation notes - evidence links - held claims - review checklist - handoff recipient - receipt identifier ## Required or proposed record references No record existence is asserted by this documentation page. - Canonical job record: job:tim:cross-device-product-families - Source-labelled platform capability notes for iPhone, iPad, and Mac - Capability evidence records with source locator, source SHA-256, provenance, revision, lifecycle, and links - Cross-device product-family project record - Reusable field guide for capability evaluation and family coherence review - Notebook to-dos for discovery, validation, review, and handoff - Approval record for each proposed entitlement, API, indexing, App Intent, or submission-related decision - Agent log entries containing authority boundaries, proposal state, and receipts - Linked file references for authorized Apple files or source material; no hidden upload - Canonical job record with owner_agent, owner_role, owner_status, source_ref, lifecycle, and revision history - Capability evidence record for each documented Apple platform capability - Cross-device product-family decision record - Approval record for entitlements, store submission, production credentials, and scope exceptions - Handoff receipt linking decisions to implementation and review state ## Sources and evidence These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment. - `agents/index.html#tim` - `source_record:job:tim:cross-device-product-families` - `job:tim:cross-device-product-families` - `Observed native contract: project_and_field_guide_collections` - `Observed native contract: deadlines` - `Observed native contract: records` - `Observed native contract: pointguard` - `Observed 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/`