Source: https://guthlabs.ai/docs/jobs/tim-native-capability-qualification/qualification/ job / candidate # Native capability qualification — qualification The distinct qualification 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**: 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 [wcag-contrast-ratio-checkerrequired · Check recorded foreground/background contrast values for proposed interfaces; store inputs and outputs as evidence.]()[date-duration-calculatorrequired · Calculate evidence age, review windows, and explicit workback intervals without implying external calendar writes.]() ## 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. - A qualification record cannot be marked qualified unless scope, claim, platform matrix, evidence locator, evidence date, reviewer, and approval record are present. - A named framework, App Intent, Core Spotlight surface, Apple Intelligence reference, or other native surface is recorded as a claim or candidate only; it never alone satisfies qualification. - Each platform has an explicit status: qualified, held, rejected, unsupported, or not tested, with evidence and reviewer fields. - At least one positive test and one negative test are recorded for every claimed capability; missing tests force held. - Negative cases for unavailable API, missing entitlement, permission denial, provider dependency, unauthorized file scope, and Store or production action produce a held or rejected result, never a qualified result. - Accessibility review records keyboard/pointer or touch operation as applicable, text resizing, VoiceOver semantics and order, focus visibility, contrast evidence, reduced-motion behavior, and non-color status cues; any untested item forces held. - Privacy review records data categories, collection or indexing scope, visibility, credential handling, local custody, retention/deletion behavior, and customer-data boundaries; uncertainty forces held. - Every source-backed observation contains a source locator, SHA-256, provenance, revision, and lifecycle; missing or mismatched source metadata forces held. - Chronology test rejects evidence with no date, a conflicting revision, or a claim that exceeds the evidence date. - Authority test rejects work outside authorized Apple files and holds new entitlements, Store submission, production credentials, provider effects, customer indexing, publication, or external writes. - Failure-state test verifies that blocked, denied, unavailable, stale, conflicting, and incomplete states show a reason, owner, next action, deadline, and receipt. - Approval test verifies that final disposition remains proposed or held until a human approval record exists. - Public-claims test verifies that only evidence-bounded statements are allowed and that deployment, availability, provider connection, indexing, publication, qualification, or production claims remain held unless separately verified. ## Negative and held-state tests - Treating a native API or named surface as proof of a connected web feature. - Claiming an unavailable API, unsupported platform/version, entitlement, provider, credential, database, customer index, publication, or production effect. - Testing or describing behavior outside Tim's authorized Apple-file scope. - Using stale, undated, conflicting, or unverifiable source material. - Failing to distinguish local prototype or index behavior from canonical specialist-app execution. - Indexing private, protected, customer, credential, or unrelated records. - Relying on color, motion, touch-only controls, or unlabeled controls that exclude users. - Silently retrying blocked work or converting a failure into an approval. - Publishing doorway documentation or duplicating URLs without distinct useful content. - Sending messages, writing calendars, submitting to a Store, or changing external systems without approval. ## Qualification claim boundary ### Potentially allowed only after the stated evidence - This is a proposal-only qualification procedure. - The package defines evidence, negative, accessibility, privacy, chronology, source, authority, and failure-state tests. - The supplied native contract identifies local prototype, indexed, or held surfaces and preserves authority boundaries. - A capability may be described as a candidate or held pending evidence and approval. ### Still held - That any Apple API or framework is currently available, connected, or production-ready. - That Apple Intelligence, Spotlight indexing, App Intents, or any other native surface is deployed or connected to a web feature. - That any entitlement has been granted or any Store submission has occurred. - That provider credentials, databases, customer records, production systems, or external calendar/message effects are connected. - That customer indexing, publication, or public documentation has occurred. - That the capability has passed qualification before deterministic tests and human approval are complete. ## 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` - `job:tim:native-capability-qualification` - `observed_native_contract.records` - `observed_native_contract.pointguard` - `observed_native_contract.web_boundary` - `app_routes:/app/notebook/field-guides/` - `app_routes:/app/notebook/approvals/` - `app_routes:/app/notebook/agent-logs/` - `allowed_instrument:wcag-contrast-ratio-checker` - `allowed_instrument:date-duration-calculator`