Source: https://guthlabs.ai/docs/jobs/tim-apple-platform-discovery/forms/

job / candidate

# Apple platform discovery — forms

The distinct forms record for Apple platform discovery. This page is proposal-only.

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

## Record status

**Record ID**: job:tim:apple-platform-discovery

**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.

### Discovery brief

Define the bounded Apple platform question and intended Guth surface.

- discovery title

- question or capability to investigate

- target platform: iPhone, iPad, Mac, or multiple

- Guth product surface affected

- requestor

- owner

- requested completion date

- priority

- out-of-scope items

### Evidence and provenance

Capture source-bound observations without treating a native surface as proof of a connected web feature.

- source title

- source URL or locator

- source type

- source SHA-256 when available

- observation date

- platform version or version claim

- quoted or paraphrased evidence

- confidence label

- known gaps

- linked source record

### Capability assessment

Describe what the capability may support and separate evidence from proposal.

- capability name

- Apple framework or native surface named in source

- supported use case

- required inputs

- expected outputs

- platform constraints

- entitlement or permission considerations

- API availability status: evidenced, unknown, or held

- web/app boundary note

- accessibility considerations

### Product mapping

Map the assessment to Guth records and owning surfaces.

- related Guth record IDs

- proposed Notebook record type

- owning app

- candidate route

- PointGuard context

- handoff or dependency

- human review required

- customer or publication effect: held

### Authority and gates

Make approval and failure handling explicit.

- new entitlement gate

- Store submission gate

- production credential gate

- scope authorization check

- approval owner

- blocked state

- fallback or defer decision

- review deadline

- receipt or approval record

### Closeout

Preserve a reusable result and its lifecycle state.

- decision summary

- claims allowed

- claims held

- follow-up tasks

- linked field guide

- revision note

- lifecycle: proposed, indexed, prototype, or held

- reviewer sign-off status

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

### Scope and assignment

Define the authorized discovery boundary and prevent work outside Apple files or approved product scope.

- job_id

- owner_agent

- owner_role

- authorized_platforms

- authorized_topics

- out_of_scope_topics

- research_question

- requested_completion_window

### Capability evidence

Capture each capability as a source-bound finding without treating a named framework or surface as proof of connected product behavior.

- finding_title

- platform

- capability_area

- source_locator

- source_sha256

- observed_or_proposed

- confidence

- supporting_notes

- unknowns

- availability_check_needed

### Cross-platform comparison

Record meaningful differences and shared product-family implications across iPhone, iPad, and Mac.

- platform

- user_context

- candidate_surface

- shared_behavior

- platform_specific_behavior

- accessibility_considerations

- implementation_dependency

- open_question

### Principal gates and failure states

Make entitlement, submission, credential, and scope constraints explicit before any implementation recommendation.

- gate_type

- affected_finding

- required_approval

- credential_dependency

- failure_state

- fallback_or_hold_state

- owner

- review_status

### Proposal and review

Turn findings into bounded proposals with clear non-claims and a human review decision.

- proposed_action

- related_records

- implementation_assumption

- public_claim_allowed

- public_claim_held

- reviewer

- decision

- decision_notes

- receipt_reference

## Required or proposed record references

No record existence is asserted by this documentation page.

- source-labelled Apple capability note

- capability assessment record

- Apple platform evidence or source locator record

- linked field guide or procedure record

- deadline and review to-do records

- approval record for held claims or proposed decisions

- agent log with authority, receipts, revisions, and lifecycle

- project membership record when work is grouped into a platform-discovery project

- job record for job:tim:apple-platform-discovery

- source-labelled capability findings

- platform comparison record covering iPhone, iPad, and Mac

- Apple Intelligence assessment record

- Spotlight indexing assessment record

- App Intents assessment record

- product-family coherence proposal

- entitlement and submission gate register

- review decision and receipt record

## 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:apple-platform-discovery`

- `Observed native contract: Notebook collections, deadlines, record provenance, PointGuard boundary`

- `Observed app routes: /app/pointguard/, /app/notebook/notes/, /app/notebook/files/, /app/notebook/to-dos/, /app/notebook/approvals/, /app/notebook/projects/, /app/notebook/field-guides/, /app/notebook/agent-logs/, /app/notebook/search/`

- `Observed app route state: local prototypes or indexes; provider, credential, database, customer, publication, and production effects held`

- `Allowed verified-instrument directory reviewed; no instrument selected because the supplied job is platform discovery rather than a calculation task`

- `job:tim:apple-platform-discovery`

- `Observed native contract: records preserve canonical IDs, provenance, revisions, lifecycle, tags, links, attachments, and record revisions.`

- `Observed native contract: PointGuard is a persistent cross-app context surface while specialist apps remain execution and canonical-record owners.`

- `Observed native contract: provider, credential, database, customer, publication, and production effects are held.`
