Source: https://guthlabs.ai/docs/field-guides/apple-capability-index/steps/ field guide / candidate # Apple capability index โ€” steps The distinct steps record for Apple capability index. This page is proposal-only. Status: **proposed**Lifecycle: **candidate** ## Record status **Record ID**: field-guide:apple-capability-index **Parent lifecycle**: candidate **Page lane**: plan **Lane lifecycle**: proposed **Owner**: Tim **Owner role**: Not separately recorded **Owner status**: Not separately recorded **Qualification result**: NOT RUN ยท held for evidence and human review **Working browser surface:** [Field guides โ€” documentation]() โ€” Inspect the guide and persist local checkpoints. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held. ## Ordered procedure - Open the source record and confirm that the guide is limited to Apple capability discovery, Swift and SwiftUI implementation, App Intents and Spotlight, cross-device product families, and native capability qualification. - Create or update a source-bound field-guide record using the supplied source record ID, title, slug, owner agent Tim, related jobs, source locator, provenance, revision, and lifecycle metadata. - Write the capability question in one sentence. Separate the user problem from the proposed native surface and label the proposal as a hypothesis. - For each hypothesis, name the candidate native surface only as a concept to investigate. Do not treat the name of a native surface as proof of a connected web feature, provider integration, credential flow, database authority, customer indexing, publication, or deployment. - Assign the specialist app that would execute the work and own the canonical record. Use PointGuard only as a persistent cross-app context surface; do not assign canonical ownership to PointGuard. - Link the hypothesis to the relevant local Guth surfaces for notes, files, projects, field guides, to-dos, approvals, search, and Agent Logs. Treat these routes as prototypes or indexes according to the observed route state, not as proof of production behavior. - Collect only source-bound evidence available in the supplied record, observed native contract, app-route descriptions, or later verified evidence supplied through an approved record. Store source locators, source SHA-256 where available, origin, provenance, revision, and lifecycle for each evidence record. - Compare the hypothesis with the observed contract: records can preserve canonical IDs and provenance; deadlines can carry dueAt, priority, recurrenceCandidate, completion state, tags, revisions, and scheduled/deadline views; PointGuard carries context while specialist apps remain owners. - Document platform constraints and unknowns explicitly, including whether the proposed capability has an implementable interface, how records would be owned, how accessibility would be maintained, and which external effects remain held. - Create bounded to-dos for every unresolved question. Set an owner, priority, dueAt deadline, dependency, completion state, and review tag. Use Agenda only to draft or inspect local schedule state; hold external calendar writes. - Attach source-labelled notes or file references for design material. Do not imply hidden upload, protected storage, external publication, or an authoritative customer index. Keep upload and protected storage held unless separately verified. - Prepare a local review proposal in Approvals with state Needs review. Include the hypothesis, evidence, constraints, record owner, acceptance tests, and claims that must remain held. - Branch to qualification only when every required evidence locator is present and the proposed interface, ownership, accessibility, and failure behavior are specified. Otherwise mark the capability Held and create the missing-evidence workback. - On reviewer disposition, preserve the decision, reviewer, timestamp, reason, linked evidence, and follow-up deadline in the approval receipt. A local approval changes proposal state only and does not authorize deployment, provider connection, publication, or external writes. - Revisit the index when source records, native-contract observations, or route states change. Create a new revision rather than overwriting prior evidence or decisions. ## Deadline and chronology rules - Every unresolved qualification question must have a named owner and dueAt value. - Set the initial review deadline before approval submission; if no date is supplied, leave the record Needs review rather than inventing one. - Dependencies must be completed before the dependent qualification task is marked complete. - Overdue work must remain visible in Today, To-dos, or Agenda local views and must not trigger an external write. - A capability without complete evidence, ownership, accessibility, and failure-state fields remains Held. - Revisions must preserve prior decisions and evidence rather than silently replacing them. ## Failure branches during execution - Confusing a named Apple native surface with an implemented or connected feature. - Claiming App Intents, Spotlight, SwiftUI, cross-device behavior, deployment, publication, or qualification without source-bound evidence. - Assigning canonical record ownership to PointGuard instead of the specialist app. - Treating prototype or indexed local routes as production applications or authoritative databases. - Inventing provider, credential, customer, or external calendar effects. - Losing provenance, source locators, hashes, or revision history when consolidating evidence. - Creating keyword-only documentation routes with no distinct useful content. - Using inaccessible controls, unlabeled fields, color-only status, or interaction patterns that cannot be keyboard, assistive-technology, or reduced-motion reviewed. - Allowing overdue or incomplete qualification tasks to appear complete. - Exposing private work through public documentation or search partitions. ## Sources and evidence These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment. - `source_record:field-guide:apple-capability-index` - `field-guide:apple-capability-index` - `agents/index.html#tim` - `Observed native contract: project_and_field_guide_collections` - `Observed native contract: deadlines` - `Observed native contract: records` - `Observed native contract: pointguard` - `APP_ROUTES:/app/notebook/field-guides/` - `APP_ROUTES:/app/notebook/approvals/` - `APP_ROUTES:/app/notebook/to-dos/` - `APP_ROUTES:/app/pointguard/`