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

job / candidate

# App Intents and Spotlight — forms

The distinct forms 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**: 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](<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.

## Proposed form sections

Each section is a candidate schema for inspectable records. Required-field presence does not establish factual truth.

### Scope and source

Define the authorized Apple work and bind every claim to supplied source material.

- job record ID

- owner agent

- owner role

- authorized repository or file scope

- source locator

- source SHA-256

- target platforms

- target OS versions

- out-of-scope areas

### Capability assessment

Record what a named Apple capability may support without treating its presence as proof of availability or connection.

- capability name

- Apple framework or surface

- intended user outcome

- required inputs

- expected outputs

- platform-specific differences

- availability evidence

- unknowns

- fallback behavior

- accessibility considerations

### App Intent proposal

Specify a bounded intent contract for review before implementation.

- intent name

- user-facing description

- parameters

- parameter validation

- result type

- invocation contexts

- required permissions

- side effects

- confirmation requirement

- error states

- reversible behavior

- human approval requirement

### Spotlight indexing proposal

Define local indexing behavior and visibility controls without claiming customer indexing or production search.

- record type

- searchable title

- keywords

- content description

- deep-link target

- visibility class

- source record ID

- revision token

- freshness policy

- update trigger

- removal trigger

- private-data handling

- empty and stale states

### Product-family review

Check coherent behavior across iPhone, iPad, and Mac while preserving specialist app ownership.

- platform

- surface owner

- layout or interaction adaptation

- shared record contract

- input method

- keyboard and pointer behavior

- voice or accessibility behavior

- offline behavior

- unsupported capability treatment

- review notes

### Authority and approvals

Capture gates that cannot be crossed by this package.

- entitlement required

- credential required

- provider dependency

- database or customer effect

- store submission effect

- production effect

- approver

- decision state

- decision receipt

- held reason

### 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

Record the bounded job, accountable specialist, and source location.

- job title

- canonical job ID

- owner agent

- owner role

- owner status

- source reference

- record lifecycle

- revision note

### Capability scope

Separate platform areas from implementation claims and identify what requires evidence.

- platform area

- framework or API name

- capability description

- supported device family

- minimum platform version if verified

- source locator

- availability status

- unverified claim flag

### Product-family mapping

Describe how a capability could fit across iPhone, iPad, and Mac without implying connected production behavior.

- product surface

- user-facing purpose

- shared behavior

- platform-specific behavior

- design dependency

- canonical record owner

- held integration effect

### Principal gates and boundaries

Make approval requirements and never-rules explicit before implementation or publication.

- new entitlement required

- Store submission required

- production credential required

- authorized Apple files

- excluded files or systems

- approval owner

- blocked state

- reason for hold

### Evidence and review

Preserve traceable support for every public documentation claim.

- claim text

- evidence source

- source SHA-256 if available

- reviewer

- review date

- confidence state

- receipt ID

- replacement or correction note

## Required or proposed record references

No record existence is asserted by this documentation page.

- Source-labelled job record for job:tim:app-intents-and-spotlight

- Project record grouping the capability assessment, platform targets, and approval state

- Field-guide record for the bounded evaluation procedure

- Apple capability index reference with source locator and source SHA-256

- Platform-surface assessment records for iPhone, iPad, and Mac

- App Intent proposal records with inputs, outputs, invocation context, and authority boundary

- Spotlight indexing proposal records with searchable entities, visibility, freshness, and removal behavior

- Apple intelligence/context proposal record with unsupported claims explicitly held

- Entitlement and submission gate records marked Needs review or Held

- Agent log with current work, receipts, revisions, and authority review

- Approval record for any proposed implementation or entitlement change

- Deadline to-do records for review, validation, and approval workbacks

- Job record with canonical ID, owner, lifecycle, source reference, and revision history

- Capability evidence record for each documented Apple framework or platform claim

- Scope decision record for authorized Apple files and excluded work

- Approval record for entitlements, Store submission, credentials, and any production effect

- Verification receipt linking claims to reviewed source material

## 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/pointguard/`

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

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

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

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

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

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

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

- `App route: /app/notebook/to-dos/`

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

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

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

- `source_record.job:tim:app-intents-and-spotlight`

- `Observed native contract: web_boundary`

- `Observed app route: /app/pointguard/`

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

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

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

- `Observed app route: /app/notebook/projects/`

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