App Intents — qualification

Record status

Record ID

tool:app-intents

Parent lifecycle

candidate

Page lane

docs_qualification

Lane lifecycle

proposed

Owner

Tim

Owner role

Apple platform specialist

Owner status

Not separately recorded

Qualification result

NOT RUN · held for evidence and human review

Working browser surface: Tools — overview — Inspect the tool contract, usage, boundaries, and proposed qualification checks. 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 docs_qualification lane. It does not execute tests, establish compliance, qualify the subject, or authorize an effect.

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.

Catalog-observed source metadata

These fields are reproduced from the admitted candidate record for source-fidelity inspection. Presence does not prove implementation, connection, qualification, authority, or an external effect.

tool_id

tool:app-intents

slug

app-intents

title

App Intents

owner_agents

Tim

owner_roles

Apple platform specialist

related_jobs

Swift and SwiftUI implementation; Apple platform discovery; App Intents and Spotlight; Cross-device product families; Native capability qualification

related_field_guides

iOS 27; iPadOS 27; macOS 27; Liquid Glass; Apple capability index

principal_gates

New entitlements; Store submission; Production credentials; Scope outside authorized Apple files

never_rules

Race another writer; Claim an unavailable API; Publish or submit without approval

lifecycle

candidate

source_refs

agents/index.html#tim

Proposed deterministic qualification tests

• AT-01 Source integrity: every page displays tool_id tool:app-intents, slug app-intents, owner Tim, and source reference agents/index.html#tim.
• AT-02 Unknown handling: absent implementation, connection, qualification, deployment, entitlement, credential, API, or authority evidence is rendered as unknown, never as verified or available.
• AT-03 Platform specificity: a qualification record cannot pass unless the target platform and the exact requested capability are stated.
• AT-04 Entitlement gate: any request involving a new entitlement is automatically held pending explicit approval evidence.
• AT-05 Submission gate: any store-submission or production-credential requirement is automatically held; the system cannot mark it approved.
• AT-06 Scope gate: a file outside authorized Apple files fails scope review and forces held status.
• AT-07 Never-rule protection: the workflow rejects race instructions, unavailable-API claims, unapproved publishing, and unapproved submission.
• AT-08 Accessibility: every proposed interactive flow has a keyboard path where applicable, VoiceOver labels and order, Dynamic Type review, visible focus, contrast review, and reduced-motion review; missing evidence fails accessibility qualification.
• AT-09 Privacy: each input, output, persistence location, log destination, and data-sharing purpose is recorded; unknown data handling fails privacy qualification.
• AT-10 Abuse resistance: malformed parameters, oversized input, repeated invocation, unauthorized action requests, ambiguous intent, and failure recovery are tested with deterministic expected outcomes.
• AT-11 Source traceability: every normative or capability claim links to a supplied source record or owner-provided evidence; unsupported claims are labeled proposed or held.
• AT-12 Distinctness: each documentation route contains a unique scope, evidence requirement, and acceptance criterion; duplicate placeholder pages are rejected.
• AT-13 Publication safety: proposal pages may be published only after owner approval and must state that implementation, deployment, and authority are unproven.
• AT-14 Cross-device separation: iOS, iPadOS, and macOS results are recorded separately; passing one platform does not imply passing another.
• AT-15 Decision determinism: pass requires all applicable gates passed, fail requires a failed mandatory test, and held applies to unresolved unknowns or principal gates.

Negative and abuse cases

• The tool name and catalog record do not prove an implementation or working connection.
• Apple platform versions and field-guide labels are supplied context, not proof that a particular API exists or is available.
• App Intents, Spotlight, SwiftUI, Liquid Glass, and cross-device behavior must not be described as implemented or supported without evidence.
• New entitlements may create security, privacy, and review obligations.
• Store submission and production credentials are outside the proven authority boundary.
• Scope outside authorized Apple files can cause unauthorized changes or misleading documentation.
• Accessibility failures may block use by people relying on VoiceOver, keyboard navigation, Dynamic Type, focus indicators, contrast, or reduced-motion settings.
• Intent inputs or outputs may expose private data through persistence, indexing, logs, screenshots, or cross-device synchronization.
• Malformed or adversarial intent parameters may trigger unsafe actions, excessive resource use, or misleading results.
• Repeated invocation or oversized input may create denial-of-service or performance risk.
• Cross-device assumptions can produce inconsistent behavior or unsupported claims.
• Source-only documentation can be mistaken for evidence of deployment or production readiness.

Qualification claim boundary

Potentially allowed only after evidence and review

• The source record names App Intents and related Apple-platform work as a proposed qualification scope.
• Tim is the listed owner and Apple platform specialist.
• The related jobs and field guides are those supplied in the source record.
• New entitlements, store submission, production credentials, and scope outside authorized Apple files are principal gates.
• Race another writer, claim an unavailable API, publish or submit without approval are never-rules.
• Documentation can define deterministic qualification, accessibility, privacy, abuse, source, and authority tests.
• All implementation, connection, deployment, API availability, entitlement approval, credential access, and submission status remain unproven unless separately evidenced.

Still held

• That App Intents is implemented or connected.
• That any specific Apple API is available, current, or authorized.
• That iOS 27, iPadOS 27, macOS 27, or Liquid Glass behavior has been verified.
• That Spotlight indexing or cross-device product-family behavior works.
• That the tool can request entitlements, obtain production credentials, submit to a store, or deploy software.
• That Tim or any other party has authority to approve production changes or submissions.
• That the tool has customer use, current metrics, provider backing, or production effects.
• That any compatible instrument exists in the supplied instrument directory.

Sources and evidence

These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.

• source_record:tool:app-intents
• agents/index.html#tim