Page actions

project template / candidate

Apple platform feature — forms

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

Status: proposedLifecycle: candidate

Record status

Record ID: project:apple-feature
Parent lifecycle: candidate
Page lane: forms
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 — 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.

Proposed form sections

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

Intake

Describe the proposed capability and establish accountable ownership without asserting implementation or platform access.

project name
capability summary
user problem
intended Apple platform or platforms
target OS range if known
requestor
project owner
technical owner
reviewers
proposed start date
proposed target date
success statement
known entitlement or device boundary
source record references
visibility

Scope and boundaries

Make inclusion, exclusion, assumptions, and held effects explicit.

in-scope behavior
out-of-scope behavior
supported devices
unsupported devices
supported OS versions
unsupported OS versions
required permissions or entitlements
credential requirements
provider or external-service dependencies
data and privacy considerations
production-effect status
assumptions
open decisions
scope approver
scope decision date

Milestones

Create ordered deliverables with owners, dates, evidence requirements, and exit criteria.

milestone name
milestone type
description
owner
planned start
planned finish
predecessor milestones
required inputs
deliverables
evidence required
reviewer
status
completion date
blocked reason
replan note

Deadlines and workback

Translate the target date into deterministic, reviewable due items.

target outcome date
hard or soft deadline
timezone
deadline rationale
workback calendar
buffer days
milestone due dates
review windows
approval due dates
evidence capture due dates
communication due dates
recurrence candidate
priority
completion state
revision note

Dependencies

Track conditions that can block execution or qualification.

dependency name
dependency category
description
owning party
internal or external
required-by milestone
requested date
expected resolution date
status
blocking severity
fallback
verification evidence
escalation owner

Owners and responsibilities

Prevent ambiguous accountability across implementation, testing, evidence, and approval.

role
person or team
responsibility
decision authority
backup owner
availability window
handoff condition
acknowledged date

Tools and guides

Record only designated local interfaces, specialist execution surfaces, and source-backed procedures.

tool or guide name
kind
route or record link
purpose
canonical owner
required before milestone
access state
authority boundary
fallback procedure
last reviewed

Evidence

Preserve reproducible proof for behavior, boundaries, and qualification decisions.

evidence ID
evidence type
related milestone
test case or observation
device and OS context
preconditions
steps performed
expected result
observed result
pass or fail
reviewer
capture date
source locator
attachment or local file reference
source SHA-256 if available
provenance
revision
visibility
limitations

Approvals

Separate proposal, review, approval, and held decisions.

approval request
decision category
proposed decision
decision owner
required reviewers
evidence links
status: Needs review, Approved, or Held
decision date
conditions
receipt or revision reference
reason held
reopen trigger

Risks and failure states

Make uncertainty and recovery actions visible before closure.

risk or failure state
category
likelihood
impact
severity
trigger
affected milestone
mitigation
contingency
owner
review date
status
residual risk
evidence link

Closure

Confirm what was completed, what remains held, and whether follow-up work is required.

closure status
completed scope
deferred scope
known limitations
final evidence set
open risks
unresolved dependencies
approval receipts
documentation links
follow-up project or task
owner handoff
closure reviewer
closure date
retention or visibility decision

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

Feature identity

Define the capability and establish project ownership.

Project name
Feature title
Problem statement
User outcome
Product owner
Technical owner
Canonical project ID
Tags
Lifecycle state

Platform and entitlement boundary

Capture native assumptions without asserting that any web or provider connection exists.

Apple platform or framework
Target device families
Minimum OS version
Required capability or entitlement name
Entitlement verification status
Signing or provisioning dependency
Device-only behavior
Simulator limitation
Known platform constraints
Evidence links

Scope and acceptance

Separate included behavior from unsupported or deferred behavior.

In-scope behaviors
Out-of-scope behaviors
User-visible states
Failure states
Offline behavior
Privacy-sensitive data handled
Accessibility requirements
Acceptance criteria
Qualification decision owner

Deadlines and workback

Create explicit due items and derive earlier review checkpoints.

Target qualification date
Target release decision date
Design freeze date
Implementation complete date
Device test start date
Accessibility review date
Privacy/security review date
Evidence cutoff date
Buffer days
Timezone
Dependency owner

Evidence and records

Link source-labelled artifacts while preserving provenance and revision history.

Linked notes
Linked files
Source locators
Source SHA-256
Test run references
Screenshots or recordings as local references
Revision note
Evidence visibility
Open questions

Required or proposed record references

No record existence is asserted by this documentation page.

project record
intake record
scope decision record
milestone records
deadline and workback to-dos
dependency records
owner assignments
tool and guide links
evidence records
approval records
risk records
closure record
Project record
Feature brief
Entitlement and capability assessment
Device and OS support matrix
Implementation task records
Test evidence records
Accessibility review record
Approval record
Held external-effect receipt

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