Apple capability index — examples

The distinct examples record for Apple capability index. This page is proposal-only.

Status: proposedLifecycle: 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.

Hypothetical scenarios

A reviewer opens the Apple capability index guide for bounded local rehearsals. Every fixture uses invented placeholders, performs no provider or external action, and remains held until source evidence and human review are recorded.

1. Guided inquiry fixture

A reviewer records a bounded question, links only supplied source references, and marks every unanswered point Needs review.

Fixture ID: apple-capability-index-example-001
Evidence: Hypothetical source placeholders only
Decision: HELD · human review required
External effects: None

2. Source comparison fixture

A reviewer compares two hypothetical source locators, preserves disagreement, and holds any conclusion until provenance is supplied.

Fixture ID: apple-capability-index-example-002
Evidence: Hypothetical source placeholders only
Decision: HELD · human review required
External effects: None

3. Uncertainty and pathway fixture

A reviewer constructs a local procedure or study pathway with checkpoints while labelling uncertainty and leaving external effects Held.

Fixture ID: apple-capability-index-example-003
Evidence: Hypothetical source placeholders only
Decision: HELD · human review required
External effects: None

4. Potentially allowed claim fixture

A hypothetical claim may advance only when its exact evidence locator, scope, reviewer, and decision rationale are recorded; this fixture asserts no fact.

Fixture ID: apple-capability-index-example-004
Evidence: Hypothetical source placeholders only
Decision: HELD · human review required
External effects: None

5. Held claim fixture

A hypothetical unsupported claim remains Held with missing evidence and human-review rationale visible; it is not published or indexed.

Fixture ID: apple-capability-index-example-005
Evidence: Hypothetical source placeholders only
Decision: HELD · human review required
External effects: None

Filled example fields

Scope and ownership fixture

Define the capability question, owner, and bounded review scope.

guide_id: Example value to be supplied and reviewed
capability_question: Example value to be supplied and reviewed
owner_agent: Named human or Agent owner required
related_job: Example value to be supplied and reviewed
platform_scope: Example value to be supplied and reviewed
review_date: Not supplied in this hypothetical fixture

Source binding fixture

Preserve the supplied source relationship and provenance before analysis.

source_record_id: fixture-source-001 (hypothetical; no external claim)
source_locator: fixture-source-001 (hypothetical; no external claim)
source_sha256: fixture-source-001 (hypothetical; no external claim)
origin: Example value to be supplied and reviewed
provenance_note: Example value to be supplied and reviewed
revision_id: Example value to be supplied and reviewed

Capability hypothesis fixture

Describe a possible Apple-platform capability without presenting it as an existing connected feature.

capability_name: Example value to be supplied and reviewed
user_problem: Example value to be supplied and reviewed
candidate_native_surface: Not supplied in this hypothetical fixture
required_app_context: Example value to be supplied and reviewed
specialist_app_owner: Named human or Agent owner required
canonical_record_owner: Named human or Agent owner required

Review questions

A new record stores a canonical ID, owner agent, source locator, source SHA-256, provenance, lifecycle, and revision history.
The record distinguishes a named native surface from an observed Guth route and labels unverified effects Held.
The form cannot mark a capability approved without evidence records, reviewer identity, review timestamp, and an approval receipt.
The lifecycle model rejects invalid transitions and exposes a visible failure or Held state.
A missing source locator or failed checksum prevents qualification advancement.
The record links to exactly one accountable owner and at least one related job before review.
Every implementation candidate includes inputs, outputs, permission assumptions, failure state, and accessibility requirements.
The workback includes discovery, technical validation, accessibility, and approval due dates.

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/
Observed native contract: web_boundary
Observed app route: /app/notebook/field-guides/
Observed app route: /app/notebook/approvals/
Observed app route: /app/notebook/agent-logs/
Allowed instruments: finite-state-machine-simulator
Allowed instruments: wcag-contrast-ratio-checker
Allowed instruments: checksum-verifier