Source: https://guthlabs.ai/docs/jobs/tim-native-capability-qualification/forms/ job / candidate # Native capability qualification โ€” forms The distinct forms record for Native capability qualification. This page is proposal-only. Status: **proposed**Lifecycle: **candidate** ## Record status **Record ID**: job:tim:native-capability-qualification **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. ### Qualification brief Define the bounded capability question and intended product context. - job title - requestor - product or project record ID - capability question - user outcome - target platforms - target OS versions - requested decision date - priority - tags ### Source and evidence Bind every claim to supplied or later-approved evidence without implying live availability. - source title - source locator - source SHA-256 - source provenance - source revision - evidence excerpt - evidence type - known gaps - attachment references ### Platform capability matrix Compare proposed behavior across Apple platforms and identify qualification state. - capability name - iPhone behavior - iPad behavior - Mac behavior - required Apple framework - API or surface reference - availability state - minimum OS assumption - entitlement requirement - platform differences - fallback or held behavior - accessibility considerations ### Authority and risk review Prevent unsupported claims and route gated decisions to human approval. - claim classification - owner - allowed action - held action - entitlement impact - credential impact - store-submission impact - scope boundary - privacy or data consideration - failure state - approval record ID ### Qualification outputs Capture reusable conclusions and implementation handoff material. - qualification summary - supported proposal - unsupported or unavailable claim - implementation notes - test cases - open questions - recommended next owner - receipt links - lifecycle ### 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 identity and ownership Define the qualification request and preserve accountable ownership. - job title - job slug - owner agent - owner role - owner status - job summary - source reference - canonical record ID - lifecycle - reviewers ### Platform scope Record which Apple platform surfaces are being considered without assuming availability or connection. - platform targets: iPhone, iPad, Mac - Apple capability area - candidate capability name - requested user outcome - current evidence status - out-of-scope items - related product family ### Capability evidence Capture verifiable source material and distinguish observation from proposal. - source locator - source title - source SHA-256 - observation date - provenance note - API or framework name as written in source - availability claim status - evidence excerpt - record revision ### Gates and authority Make blocked actions and approval requirements explicit. - new entitlement required: yes/no/unknown - store submission involved: yes/no/unknown - production credential required: yes/no/unknown - authorized Apple files or scope - approval owner - approval status: Needs review, Approved, Held - reason for hold ### Qualification result Produce a bounded recommendation based only on recorded evidence. - qualification outcome: candidate, needs evidence, held, or rejected - supported platform scope - known limitations - implementation prerequisites - failure state - next human action - linked receipts - last reviewed revision ## Required or proposed record references No record existence is asserted by this documentation page. - Source-bound job record for native capability qualification - Capability qualification record with canonical ID, origin, source locator, source SHA-256, provenance, revision, lifecycle, tags, links, and attachments - Platform matrix record covering iPhone, iPad, and Mac proposals - Evidence or source-reference record for each capability claim - Field-guide record for the qualification procedure - Approval record for any entitlement, credential, submission, or scope decision - Agent log recording work, receipts, authority, held states, and failures - Job record with canonical ID, owner, lifecycle, source reference, revision, and provenance - Capability qualification record for each reviewed capability - Platform-scope record identifying iPhone, iPad, or Mac applicability - Evidence record containing source locator, source SHA-256, provenance, and revision - Approval record for new entitlements, store submission, production credentials, or scope exceptions - Agent log receipt describing authority, current state, and held actions - Optional field-guide record linking the ordered review procedure ## 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:native-capability-qualification` - `Observed native contract: project_and_field_guide_collections` - `Observed native contract: deadlines` - `Observed native contract: records` - `Observed native contract: pointguard` - `App route metadata for /app/pointguard/` - `App route metadata for /app/notebook/projects/` - `App route metadata for /app/notebook/field-guides/` - `App route metadata for /app/notebook/agent-logs/` - `App route metadata for /app/notebook/approvals/` - `App route metadata for /app/notebook/files/` - `App route metadata for /app/notebook/notes/` - `Observed native contract: records preserve canonical IDs, source locators, source SHA-256, provenance, revisions, lifecycle, tags, links, and attachments.` - `Observed native contract: PointGuard is a persistent cross-app context surface while specialist apps remain execution and canonical-record owners.` - `Observed native contract: current GuthHub routes are local prototypes or indexes and provider, credential, database, customer, publication, and production effects remain held.` - `Observed app route: /app/notebook/field-guides/` - `Observed app route: /app/notebook/approvals/` - `Observed app route: /app/notebook/agent-logs/` - `Observed app route: /app/notebook/projects/` - `Observed app route: /app/notebook/search/` - `Observed app route: /app/pointguard/`