Source: https://guthlabs.ai/docs/tools/core-spotlight/qualification/ tool / candidate # Core Spotlight — qualification The distinct qualification record for Core Spotlight. This page is proposal-only. Status: **proposed**Lifecycle: **candidate** ## Record status **Record ID**: tool:core-spotlight **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. ### Lane-specific instrument aids [http-status-code-header-lookupoptional · Optional documentation aid for teaching HTTP status and header concepts; not evidence of Apple API availability, implementation, deployment, or authority.]()[regex-testeroptional · Optional deterministic text-pattern checking for route identifiers and evidence labels; not an Apple-platform implementation or qualification authority.]()[checksum-verifieroptional · Optional integrity check for supplied evidence artifacts; not proof of provenance, API support, entitlement approval, or submission status.]() ## 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:core-spotlight **slug**: core-spotlight **title**: Core Spotlight **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 fidelity: page displays tool_id, slug, title, owner_agents, owner_roles, related_jobs, related_field_guides, principal_gates, never_rules, and source_refs exactly from the supplied source record. - AT-02 Proposal boundary: every page states that implementation, connection, qualification, deployment, API availability, credentials, and authority are not proven unless separately recorded. - AT-03 Route distinctness: each documentation route has a unique purpose, required records, and decision output; no route is a duplicate of another. - AT-04 Platform separation: iOS 27, iPadOS 27, and macOS 27 are evaluated as separate rows; missing evidence produces unknown or blocked, never qualified by inference. - AT-05 API evidence: a capability cannot be marked available without supplied evidence identifying the API or behavior, target platform, authorized scope, and verification record. - AT-06 Entitlement gate: any new entitlement yields blocked until an explicit approval record exists. - AT-07 Submission gate: Store submission status yields blocked or unknown unless an approval record and submission evidence are supplied. - AT-08 Credential gate: production-credential status yields blocked or unknown unless explicitly recorded; no credential is requested, generated, or implied. - AT-09 Scope gate: files outside authorized Apple files are rejected from the qualification record. - AT-10 Never-rule enforcement: no workflow permits racing another writer, claiming an unavailable API, publishing or submitting without approval. - AT-11 Accessibility: all interactive documentation controls are keyboard reachable, have programmatic names, expose visible focus, preserve logical reading order, support text enlargement without clipping, and do not require color alone; dynamic updates are announced to assistive technology. - AT-12 Accessibility behavior: platform-specific capability claims include a non-visual completion path and a documented fallback when the native surface is unavailable or inaccessible. - AT-13 Privacy minimization: every proposed indexed field has a purpose, data classification, retention rule, deletion path, and user-control record; absent records block qualification. - AT-14 Privacy exposure: sensitive, private, or user-entered content is not proposed for Spotlight or App Intents exposure without explicit authorization and review. - AT-15 Abuse resistance: test cases cover deceptive labels, spammy indexing, unauthorized automation, privilege escalation, sensitive-query leakage, and repeated invocation; unresolved high-risk cases block publication. - AT-16 Source provenance: every factual claim links to a supplied source reference or a supplied evidence artifact; catalog observation is labeled observation, not validation. - AT-17 Authority: owner role is recorded as Apple platform specialist, but publication and submission authority remain unproven until an approval record is supplied. - AT-18 Deterministic decision: identical inputs produce the same qualified, blocked, or insufficient-evidence result. - AT-19 Instrument boundary: compatible instruments are used only for their stated auxiliary purpose and never treated as Apple-platform evidence. - AT-20 Publication: proposal documentation cannot be marked production-ready or submitted without explicit approval records for all applicable gates. ## Negative and abuse cases - Inferring implementation or API availability from an agent catalog entry - Confusing related jobs or field guides with verified platform support - Applying an iOS conclusion to iPadOS or macOS without separate evidence - Requesting or implying new entitlements or production credentials - Publishing or submitting without approval - Expanding beyond authorized Apple files - Indexing sensitive or private content unintentionally - Accessibility failures in Spotlight, App Intents, SwiftUI, or documentation flows - Deceptive or spam-like discovery metadata - Unauthorized automation or privilege escalation - Treating auxiliary calculators or checkers as authority or source validation - Presenting proposal-only records as customer use, deployment, or production capability ## Qualification claim boundary ### Potentially allowed only after evidence and review - The supplied source record names Core Spotlight and identifies Tim as owner agent with Apple platform specialist role. - The source record associates the tool with Swift and SwiftUI implementation, Apple platform discovery, App Intents and Spotlight, cross-device product families, and native capability qualification. - The source record lists iOS 27, iPadOS 27, macOS 27, Liquid Glass, and Apple capability index as related field guides. - The source record lists new entitlements, Store submission, production credentials, and scope outside authorized Apple files as principal gates. - The source record requires no racing another writer, no claiming an unavailable API, and no publishing or submitting without approval. - Documentation qualification can be proposed using deterministic evidence, accessibility, privacy, abuse, source, and authority checks. ### Still held - The tool implements or connects to Spotlight or App Intents. - Any named Apple API is available on any target platform. - The tool has new entitlements, production credentials, or Store-submission access. - The tool is deployed, production-ready, approved, or authoritative. - The owner role alone authorizes publication or submission. - Any customer use, customer outcome, cross-device behavior, or native capability effect. - Any current Apple platform behavior beyond the supplied source record. - Any privacy, accessibility, security, or abuse posture not supported by test evidence. ## Sources and evidence These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment. - `source_record:tool:core-spotlight` - `agents/index.html#tim`