macOS 27 — tools

The distinct tools record for macOS 27. This page is proposal-only.

Status: proposedLifecycle: candidate

Record status

Record ID: field-guide:macos-27
Parent lifecycle: candidate
Page lane: tools
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.

Authoritative tools lane tools and interfaces

Canonical tools-page assignments

Notebook Field Guides (interface · required) — Compose the source-backed procedure, prerequisites, bounded steps, instruments, and receipts for macOS capability review.
Notebook Notes (interface · required) — Capture source-labelled observations, unknowns, revisions, and distinctions between native affordances and unverified connected behavior.
Notebook Files (interface · required) — Keep local file references and artifact metadata beside the guide without implying hidden upload or protected-storage behavior.
Notebook Projects (interface · required) — Group the guide with Swift and SwiftUI implementation, Apple platform discovery, App Intents and Spotlight, cross-device, and qualification work.
Notebook To-dos (interface · required) — Track implementation and review work with due dates, priority, completion state, tags, and human-review signals.
Notebook Approvals (interface · required) — Hold capability qualification decisions for explicit human review and preserve approval receipts.
PointGuard (interface · required) — Provide a persistent contextual room for current macOS work while leaving specialist apps as execution and canonical-record owners.
Finite State Machine Simulator (provider · optional) — Use only as an educational model to test proposed lifecycle transitions such as proposed, indexed, prototype, and held, and to expose invalid transitions before implementation. Do not use it as evidence of Notebook lifecycle enforcement or production state.
Checksum Verifier (provider · optional) — Use to independently verify a captured source SHA-256 value for an attached artifact. Do not use it to establish source authority, publication, customer indexing, or deployment.
WCAG Contrast Ratio Checker (provider · optional) — Use during proposed SwiftUI interface review to check documented foreground/background color pairs for readable contrast. Do not use it as a complete accessibility audit or as proof that a native interface is implemented.
Date & Duration Calculator (provider · optional) — Use for deterministic workback intervals and review-date calculations when planning bounded macOS implementation tasks. Do not use it as an external calendar provider or to write schedules.

Only the page's admitted lane is rendered as an assignment. Other lane inventories remain source records but are not merged here. Tool kind and required/optional status are preserved.

Authoritative lane instrument assignments

Canonical tools-page assignments

finite-state-machine-simulatoroptional · Model and test the proposed guide and capability lifecycle transitions; retain the model as educational evidence only.checksum-verifieroptional · Verify recorded SHA-256 values for local source-labelled artifacts before attaching them to notes or files.wcag-contrast-ratio-checkeroptional · Check proposed color pairs for macOS interface accessibility review; document tested pairs and limitations.date-duration-calculatoroptional · Calculate bounded workback durations and review intervals for Notebook to-dos.

An instrument listed only for another lane does not become a tools-page assignment.

Use boundary

A native surface name may be mistaken for a connected web feature; require observed evidence and keep unverified effects held.
App Intents or Spotlight relevance may be proposed without implying indexing, publication, or operating-system registration.
Cross-device language may imply synchronization or provider connectivity; record only the observed local contract and hold external effects.
A local prototype or index route may be mistaken for production state; preserve route state and lifecycle explicitly.
Using checksum verification can confirm a digest match but cannot establish provenance authority or document authenticity.
Contrast checking covers only supplied color pairs and cannot replace keyboard, VoiceOver, Dynamic Type, focus, motion, or other accessibility review.
Educational calculator outputs can be misread as implementation qualification; keep instrument results separate from native capability evidence.
External calendar, message, storage, database, credential, and provider actions remain held.
Incomplete evidence, stale revisions, or missing owners can cause unsupported capability claims.
Search must respect private and held partitions and must not be treated as customer indexing.

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:tools
Observed native contract: project_and_field_guide_collections
Observed native contract: deadlines
Observed native contract: records
Observed native contract: pointguard
/app/notebook/field-guides/
/app/notebook/projects/
/app/notebook/notes/
/app/notebook/files/
/app/notebook/to-dos/
/app/notebook/approvals/
/app/notebook/agent-logs/
/app/pointguard/