Source: https://guthlabs.ai/docs/project-templates/apple-feature/field-guides/

project template / candidate

# Apple platform feature — field guides

The distinct field guides record for Apple platform feature. This page is proposal-only.

Status: **proposed**Lifecycle: **candidate**

## Record status

**Record ID**: project:apple-feature

**Parent lifecycle**: candidate

**Page lane**: app_features

**Lane lifecycle**: proposed

**Owner**: Not separately recorded

**Owner role**: Not separately recorded

**Owner status**: Not separately recorded

**Qualification result**: NOT RUN · held for evidence and human review

**Working browser surface:** [Project templates & workflows — overview](<https://guthlabs.ai/labs.html#templates-workflows>) — Create a local project from this template and validate its forms. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held.

## Related field-guide records

- /app/notebook/field-guides/

Source-proposed guide paths are references, not proof that those paths resolve.

## Operating sequence

- Create the project record with a canonical ID, provenance, lifecycle, owner, and source references.

- Complete intake and identify the proposed capability, intended users, platform boundary, target outcome, and accountable owners.

- Complete scope and record supported and unsupported devices, OS versions, entitlements, permissions, data boundaries, and held production effects.

- Create milestones with deliverables, predecessors, owners, evidence requirements, reviewers, and exit criteria.

- Set the target date and generate a workback of milestone, evidence, review, approval, and communication deadlines.

- Record dependencies and assign an owner, requested date, fallback, and escalation path for each blocking condition.

- Link only designated local interfaces, specialist execution surfaces, records, providers, or source-backed guides; mark unavailable connections as held.

- Implement within the approved scope while preserving canonical-record ownership in the specialist app and cross-app context in PointGuard.

- Capture evidence for supported and unsupported devices, OS versions, entitlement behavior, permission behavior, accessibility, error states, and held external effects.

- Run acceptance tests, attach source-labelled evidence, record failures, and create corrective milestones or risks for any failed result.

- Submit approval records with evidence links; preserve Needs review, Approved, or Held status and the decision receipt.

- Reconcile scope, milestones, deadlines, dependencies, risks, evidence, and approvals before closure.

- Close only when required acceptance tests pass or each exception is explicitly deferred, owned, dated, and approved or held.

## Handoff boundary

- Treating an indexed or prototype route as proof of a connected Apple, provider, credential, database, customer, publication, or production feature.

- Recording an entitlement or device assumption as verified without reproducible evidence.

- Allowing a target date to exist without a workback, owner, review window, or change history.

- Closing a project after implementation evidence but before accessibility, failure-state, boundary, or approval review.

- Attaching unlabelled files or unverifiable screenshots that lack device, OS, provenance, or revision context.

- Using a specialist app as if PointGuard were the canonical execution or record owner.

- Silently converting a candidate recurring task into automation.

- Publishing customer-facing claims from proposal, prototype, held, or incomplete evidence.

## Sources and evidence

These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.

- `source_record:project:apple-feature`

- `NotebookCollectionKind.project`

- `NotebookTodoPayload.dueAt`

- `Notebook Agenda deadlines/workbacks`

- `Notebook records canonical IDs, provenance, source locators, source SHA-256, revisions, lifecycle, tags, links, and attachments`

- `PointGuard persistent cross-app context surface`

- `APP_ROUTES:/app/notebook/projects/`

- `APP_ROUTES:/app/notebook/to-dos/`

- `APP_ROUTES:/app/notebook/agenda/`

- `APP_ROUTES:/app/notebook/files/`

- `APP_ROUTES:/app/notebook/approvals/`

- `APP_ROUTES:/app/notebook/field-guides/`

- `APP_ROUTES:/app/notebook/agent-logs/`

- `APP_ROUTES:/app/pointguard/`

- `Notebook records provenance and revision contract`

- `Current GuthHub app routes and held external-effect boundary`