Source: https://guthlabs.ai/docs/jobs/tim-cross-device-product-families/qualification/ job / candidate # Cross-device product families โ€” qualification The distinct qualification 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**: qualification **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. ## Qualification status **Result**: NOT RUN **Disposition**: HELD **Reviewer**: Not recorded **Receipt**: Not recorded This page defines proposed acceptance criteria for the qualification lane. It does not execute tests, establish compliance, qualify the subject, or authorize an effect. ### Lane-specific instrument aids No verified instrument is assigned to this qualification lane. ## Outcome definitions **Verified**: All stated evidence and acceptance requirements passed for the exact reviewed revision; this still does not authorize deployment or an external effect. **Failed**: One or more deterministic acceptance requirements failed with an inspectable reason. **Needs review**: Evidence or interpretation is incomplete, conflicting, or awaits an identified human reviewer. **Held**: Authority, required evidence, safe execution conditions, or a principal gate is absent. The current record remains NOT RUN / HELD. These definitions describe candidate outcomes only. ## Proposed deterministic acceptance tests Route-resolution and distinct-content checks apply only to the admitted canonical routes in this record. Held source-proposed extensions are non-resolving proposals and are excluded. - Identity: the record contains the exact supplied job ID, slug, title, owner agent Tim, owner role, and source reference agents/index.html#tim. - Scope: every claim names one or more of iPhone, iPad, or Mac, an OS version, the relevant Apple framework or surface, and an observable user outcome. - Source: every Pass has a source locator, source SHA-256, revision, provenance, capture date, and evidence excerpt; missing source metadata yields Held. - Native-surface boundary: naming Xcode, SwiftUI, App Intents, Core Spotlight, or Apple frameworks alone never yields Pass for implementation, connection, indexing, publication, or production state. - Positive capability: a claim passes only when the supplied evidence demonstrates the stated behavior on the stated platform and version, including its user-visible boundary. - Negative API: an unavailable, deprecated, inaccessible, or unverified API produces Fail or Held with the exact reason and no substitute claim. - Entitlement: any new entitlement requirement is recorded; without verified entitlement evidence, the claim is Held. - Chronology: the evidence date and platform version are compatible with the claim; anachronistic or undated evidence fails chronology qualification. - Cross-device coherence: the claim documents platform-specific behavior and does not assume identical controls, layout, input, or capability across iPhone, iPad, and Mac. - Privacy: the record identifies data collected, data indexed, visibility, local storage, sharing, retention, and user controls; unknown handling produces Held. - Privacy negative: no qualification passes if it implies customer indexing, provider connection, credential use, external database authority, or production effects not present in the supplied contract. - Accessibility: required interaction paths are operable without pointer precision, expose accessible names and roles, preserve logical focus order, support Dynamic Type, maintain readable contrast, and respect reduced-motion settings where motion exists. - Accessibility negative: a visually demonstrated feature without accessible labels, focus behavior, text scaling, or keyboard/switch path is Fail or Held, not Pass. - Authority: canonical specialist records remain owned by the Apple specialist application or designated specialist owner; PointGuard may carry context but does not become canonical. - Scope boundary: touching files outside authorized Apple files, racing another writer, claiming an unavailable API, or publishing/submitting without approval produces Fail and a held follow-up. - Failure state: every failed or held test has a reason, owner, next action, evidence requirement, and deadline. - Approval: final qualification requires a preserved human approval receipt; local approval is not store submission, publication, deployment, provider connection, credential authorization, or production release. ## Negative and held-state tests - Confusing a named native surface with a connected web or production feature. - Claiming APIs, OS capabilities, entitlements, or platform behavior without supplied evidence. - Collapsing iPhone, iPad, and Mac into one unsupported interaction model. - Treating Core Spotlight as proof of customer indexing or searchable production data. - Ignoring chronology when OS versions or framework availability change. - Collecting or indexing personal or customer data without an explicit privacy boundary. - Failing accessibility because visual layout was reviewed without assistive technology or alternate input paths. - Allowing local prototype routes to imply provider, database, credential, store, publication, or production state. - Writing outside authorized Apple files or creating competing records. - Publishing or submitting before human approval. ## Qualification claim boundary ### Potentially allowed only after the stated evidence - This is a proposal-only qualification package for the supplied cross-device Apple-platform job. - The package defines tests for source traceability, chronology, privacy, accessibility, authority, and failure states. - The supplied contract names Xcode, SwiftUI, App Intents, Core Spotlight, and Apple frameworks as existing tools or guides. - Observed Guth routes can hold local notes, deadlines, source labels, revisions, approvals, and receipts in prototype or indexed surfaces. ### Still held - That any Apple capability is implemented, connected, deployed, indexed for customers, or production-ready. - That an API is available for a particular OS version without supplied evidence. - That entitlements, credentials, store submission, publication, or production effects exist. - That a provider, database, customer record, or external service is connected. - That any qualification has passed or received approval. - That GuthHub, PointGuard, Notebook, or any listed route is a canonical Apple product owner. - That documentation URLs or web features are deployed or publicly published. ## 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` - `Observed native contract: project_and_field_guide_collections` - `Observed native contract: deadlines` - `Observed native contract: records` - `Observed native contract: pointguard` - `Observed app route: /app/notebook/field-guides/` - `Observed app route: /app/notebook/notes/` - `Observed app route: /app/notebook/approvals/` - `Observed app route: /app/notebook/agent-logs/`