Guth
NewsDocs
Page actions
View as Markdown ↗
Explore MCP tools ↗

field guide / candidate

macOS 27 — forms

The distinct forms 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
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.

Proposed form sections

Each section is a candidate schema for inspectable records. Required-field presence does not establish factual truth.

Scope and ownership

Define the bounded discovery question and accountable owner.

  • capability question
  • in-scope macOS surface
  • out-of-scope effects
  • owner agent
  • related job
  • source locator
  • source SHA-256
  • record lifecycle

Observed native contract

Record only capabilities explicitly observed in the supplied contract.

  • relevant contract clause
  • native surface name
  • what the surface permits
  • what remains unproven
  • canonical record owner
  • specialist app owner

Evidence ledger

Attach source-labelled, reviewable evidence without implying connected behavior.

  • evidence ID
  • source locator
  • evidence description
  • test or observation date
  • revision
  • attachment or local file reference
  • confidence state
  • reviewer

Workback and review

Make review timing explicit and prevent stale proposals from being treated as qualification.

  • discovery due date
  • implementation review due date
  • approval due date
  • next checkpoint
  • priority
  • recurrence candidate
  • completion state
  • tags

Qualification decision

Capture a bounded local decision and unresolved failure branches.

  • decision status
  • qualified proposal
  • held claims
  • blocking gaps
  • follow-up owner
  • receipt reference
  • revision

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 tools lane and remain separate from the primary operating form.

Scope and ownership

Define the macOS capability question, owner, related job, and review boundary.

  • guide title
  • capability question
  • owner agent
  • related job
  • reviewer
  • in-scope native surfaces
  • out-of-scope provider or production effects

Evidence capture

Attach source-labelled evidence without treating a named native surface as proof of a connected feature.

  • source locator
  • source SHA-256
  • evidence type
  • artifact or file reference
  • observed behavior
  • unknowns
  • revision identifier
  • provenance note

Capability qualification

Separate observed native affordances from proposed implementation and held effects.

  • native surface name
  • user-facing purpose
  • canonical record owner
  • execution owner
  • lifecycle state
  • accessibility considerations
  • failure state
  • privacy or visibility boundary
  • App Intents or Spotlight relevance
  • cross-device relevance
  • qualification decision

Implementation workback

Turn the proposal into bounded, reviewable work with explicit deadlines.

  • task
  • dependency
  • priority
  • due date
  • review date
  • recurrence candidate
  • completion state
  • tags
  • blocking condition
  • responsible owner

Review and receipt

Preserve a human decision and an auditable result.

  • decision status
  • approver
  • decision rationale
  • held claims
  • accepted claims
  • receipt reference
  • next review date

Required or proposed record references

No record existence is asserted by this documentation page.

  • field-guide:macos-27:plan
  • source-note:agents/index.html#tim
  • qualification-log:macos-27
  • capability-evidence:macos-27
  • decision-receipt:macos-27
  • field-guide:macos-27:tools
  • source note for each native capability claim
  • file reference for each inspected artifact
  • project record for implementation work
  • to-do records for review work and deadlines
  • approval record for each proposed capability qualification
  • agent-log receipt for each bounded review

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
  • source record field-guide:macos-27:plan
  • Observed native contract: project_and_field_guide_collections
  • Observed native contract: deadlines
  • Observed native contract: records
  • Observed native contract: pointguard
  • App route /app/notebook/field-guides/
  • App route /app/notebook/agent-logs/
  • App route /app/notebook/notes/
  • App route /app/notebook/files/
  • App route /app/notebook/projects/
  • App route /app/notebook/to-dos/
  • App route /app/notebook/agenda/
  • App route /app/notebook/approvals/
  • App route /app/pointguard/
  • field-guide:macos-27:tools
  • /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/