Source: https://guthlabs.ai/docs/jobs/tim-app-intents-and-spotlight/qualification/

job / candidate

# App Intents and Spotlight — qualification

The distinct qualification record for App Intents and Spotlight. This page is proposal-only.

Status: **proposed**Lifecycle: **candidate**

## Record status

**Record ID**: job:tim:app-intents-and-spotlight

**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](<https://guthlabs.ai/guth.html#builder>) — 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: candidate_id, source record ID, owner Tim, owner role Apple platform specialist, PACKAGING status, and agents/index.html#tim are preserved exactly.

- Deterministic qualification: every capability claim has a recorded source evidence value and is labeled proposed, verified from supplied evidence, or held; absent evidence cannot pass as verified.

- Negative: the package fails qualification if it claims an unavailable API, claims iOS 27/iPadOS 27/macOS 27 support as fact without supplied evidence, or treats a named native surface as a connected web feature.

- Negative: the package fails if it claims deployment, provider connection, credentials, database authority, customer indexing, publication, Store submission, or production effect.

- Accessibility: every proposed interaction has keyboard/focus order, screen-reader name and state, visible focus, sufficient contrast, reduced-motion behavior, and non-color-only status requirements recorded; missing any item yields Held.

- Privacy: indexing and intent records specify data minimization, visibility, record owner, exclusion of sensitive content unless explicitly authorized, and deletion/invalidation behavior; missing ownership or invalidation yields Held.

- Chronology: evidence with no source locator, revision, or capture order fails; later approval cannot be backdated to satisfy an earlier proposal.

- Source: all factual platform assertions trace to the supplied source record, observed native contract, app routes, or an allowed verified instrument; unsupported external assertions fail.

- Authority: work is limited to authorized Apple files and proposal records; any entitlement, submission, credential, publication, or scope expansion requires a human approval receipt.

- Failure state: unavailable API, missing entitlement, unsupported platform, indexing conflict, stale record, inaccessible interaction, privacy review failure, missing source evidence, or approval timeout produces an explicit Held state and next owner; it must not silently degrade into a claim of success.

- Ownership: specialist apps remain execution and canonical-record owners; PointGuard, Notebook, and routes may provide context or records but do not become canonical Apple implementation owners.

- Route honesty: references to /app/notebook/field-guides/, /app/notebook/agent-logs/, /app/notebook/approvals/, and /app/notebook/search/ describe prototype or indexed surfaces only and do not prove connected behavior.

- Instrument integrity: no instrument is designated because no allowed verified instrument is necessary for this platform qualification; no invented slug may appear.

- Documentation integrity: agents/index.html#tim is used only as the supplied source locator; any distinct future documentation URL must contain distinct useful content and must not be a doorway or keyword-spam page.

- Never-rule compliance: the record shows no race with another writer, no unavailable API claim, and no publication or submission without approval.

## Negative and held-state tests

- Confusing named Apple frameworks with verified availability or connected implementation.

- Treating platform-version labels in the source record as independently verified support claims.

- Accidentally indexing private, sensitive, stale, or deleted records.

- Creating duplicate or conflicting canonical records across specialist apps and Notebook surfaces.

- Performing entitlement, credential, Store, publication, or production work without approval.

- Using inaccessible intent, search, approval, or review flows.

- Allowing missing source evidence or chronology to be hidden by a polished prototype.

- Expanding scope beyond authorized Apple files.

## Qualification claim boundary

### Potentially allowed only after the stated evidence

- A proposal exists to qualify App Intents, Core Spotlight, Apple intelligence, and product-family coherence for an Apple platform specialist.

- The supplied job record names Xcode, SwiftUI, App Intents, Core Spotlight, Apple frameworks, and Apple platform guides as existing tools or guides.

- Observed Guth routes provide prototype or indexed surfaces for Notebook, PointGuard, approvals, search, Field Guides, and Agent Logs.

- External effects, publication, submission, credentials, provider connections, and production state are held.

### Still held

- That any App Intent or Spotlight integration is implemented, connected, deployed, indexed for customers, or production-ready.

- That iOS 27, iPadOS 27, or macOS 27 APIs are available or supported.

- That Apple intelligence integration exists or is authorized.

- That new entitlements were granted or Store submission occurred.

- That any provider, credential, database, customer record, or publication is connected.

- That qualification passed before human approval and recorded evidence exist.

## 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:app-intents-and-spotlight`

- `Observed native contract: project_and_field_guide_collections`

- `Observed native contract: deadlines`

- `Observed native contract: records`

- `Observed native contract: pointguard`

- `App route: /app/notebook/field-guides/`

- `App route: /app/notebook/agent-logs/`

- `App route: /app/notebook/approvals/`

- `App route: /app/notebook/search/`