Source: https://guthlabs.ai/docs/field-guides/macos-27/qualification/ field guide / candidate # macOS 27 โ€” qualification The distinct qualification record for macOS 27. This page is proposal-only. Status: **proposed**Lifecycle: **candidate** ## Record status **Record ID**: field-guide:macos-27 **Parent lifecycle**: candidate **Page lane**: docs_urls **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. ## Qualification status **Result**: NOT RUN **Disposition**: HELD **Reviewer**: Not recorded **Receipt**: Not recorded This page defines proposed acceptance criteria for the docs_urls 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. - Every route has distinct content: overview explains scope, steps explain procedure, tools maps surfaces, forms defines fields, examples show bounded scenarios, qualification defines evidence and decisions, and related-jobs pages explain job-specific handoffs. - The overview visibly labels the guide Proposed and states that native surfaces and app routes do not prove a connected web feature. - A reader can identify the record owner, source locator, revision, lifecycle, deadline, and next review action for every worked example. - The form rejects or flags records without an owner, source locator, problem statement, failure state, or qualification decision state. - A proposed App Intents or Spotlight example states that registration, provider connection, production indexing, and customer indexing are held. - A cross-device example identifies specialist-app ownership and does not make PointGuard the canonical execution owner. - Missing, stale, conflicting, or inaccessible evidence produces Needs review or Held, never Approved by default. - Approval preserves a receipt and revision; changing evidence creates a new revision rather than overwriting provenance. - Routes remain usable with keyboard navigation, visible focus, labelled fields, semantic headings, readable status labels, and non-color-only lifecycle indicators. - Search results distinguish private, held, and proposed records and do not expose unsupported customer or publication claims. ## Negative and held-state tests - A macOS version label may be mistaken for a verified platform release or API contract. - Named jobs such as App Intents and Spotlight may be read as proof that registration, indexing, or integration exists. - Prototype app routes may be mistaken for production web features or canonical backends. - Cross-device language can obscure which specialist app owns execution and records. - Accessibility review may be omitted if the guide focuses only on framework names. - Stale or conflicting source material can create false qualification confidence. - Medical, financial, safety, or other high-impact conclusions must not be inferred from this platform guide. ## Qualification claim boundary ### Potentially allowed only after the stated evidence - This is a proposed, source-backed field guide for organizing macOS 27 discovery and implementation review. - The guide covers related jobs including Swift and SwiftUI implementation, Apple platform discovery, App Intents and Spotlight, cross-device product families, and native capability qualification. - Notebook, PointGuard, Projects, Field Guides, Approvals, Search, and related routes are observed native surfaces or local prototype/index surfaces as described by the contract. - Records can preserve provenance, revisions, lifecycle, tags, links, attachments, and source locators when supported by the observed contract. ### Still held - macOS 27 availability, release status, or API behavior. - A connected Swift or SwiftUI implementation. - App Intents registration, Spotlight indexing, provider connection, customer indexing, or publication. - Cross-device synchronization, external writes, or production backend effects. - Native capability qualification or approval. - Database authority, customer records, credentials, protected upload, or deployed web behavior. ## Sources and evidence These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment. - `source_record:field-guide:macos-27` - `agents/index.html#tim` - `field-guide:macos-27` - `observed_native_contract.project_and_field_guide_collections` - `observed_native_contract.records` - `observed_native_contract.pointguard` - `observed_native_contract.web_boundary` - `app:/app/notebook/field-guides/` - `app:/app/notebook/projects/` - `app:/app/notebook/notes/` - `app:/app/notebook/files/` - `app:/app/notebook/to-dos/` - `app:/app/notebook/approvals/` - `app:/app/notebook/agent-logs/` - `app:/app/notebook/search/` - `app:/app/pointguard/`