Source: https://guthlabs.ai/docs/project-templates/apple-feature/qualification/ project template / candidate # Apple platform feature — qualification The distinct qualification 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**: qualification **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. ## Qualification status **Result**: NOT RUN **Disposition**: HELD **Reviewer**: Not recorded **Receipt**: Not recorded This page defines proposed acceptance criteria for the qualification lane. It does not execute tests, establish compliance, qualify the subject, or authorize an effect. ### Lane-specific instrument aids [date-duration-calculatorrequired · Check deterministic milestone durations and workback intervals.]()[countdown-days-until-timerrequired · Display proposal-only countdowns to evidence freeze or qualification target dates.]() ## Outcome definitions **Verified**: All stated evidence and acceptance requirements passed for the exact reviewed revision; this still does not authorize deployment or an external effect. **Failed**: One or more deterministic acceptance requirements failed with an inspectable reason. **Needs review**: Evidence or interpretation is incomplete, conflicting, or awaits an identified human reviewer. **Held**: Authority, required evidence, safe execution conditions, or a principal gate is absent. The current record remains NOT RUN / HELD. These definitions describe candidate outcomes only. ## Proposed deterministic acceptance tests Route-resolution and distinct-content checks apply only to the admitted canonical routes in this record. Held source-proposed extensions are non-resolving proposals and are excluded. - FORM-001: Submitting without a project title, user outcome, owner, target platform, or qualification reviewer is rejected with field-level errors and focus moves to the first invalid field. - FORM-002: A target OS range with a minimum greater than its maximum is rejected; an empty or malformed device matrix row is rejected. - FORM-003: An entitlement marked verified cannot be saved without an evidence locator and reviewer; unknown, requested, and held states remain valid without verification claims. - FORM-004: A qualification test cannot be marked passed without preconditions, steps, expected result, actual result, reviewer, and evidence reference. - FORM-005: A dueAt value without timezone is rejected; a dependent milestone cannot be completed while its blocking dependency is incomplete or held. - SCHED-001: Workback dates are calculated deterministically from the target date, declared durations, timezone, and dependencies; boundary-day behavior is displayed rather than hidden. - SCHED-002: A conflicting or overdue item is visibly flagged and remains human-reviewable; no external write occurs. - DEP-001: Removing or holding a required entitlement, device, permission, or framework dependency changes affected tests to blocked or needs review and records the causal dependency. - DEP-002: A test referencing a missing dependency record cannot pass and provides a link to create or repair that record. - REV-001: Editing scope, acceptance criteria, evidence, owner, or disposition creates a new revision containing changed fields, author, reason, timestamp, and prior revision linkage. - REV-002: Superseded evidence remains inspectable and is not presented as current evidence without its revision state. - A11Y-001: All form controls have programmatic labels, grouped instructions, visible focus, keyboard operation, logical tab order, and errors associated with the relevant control. - A11Y-002: Status is conveyed by text and not color alone; blocked, held, failed, and passed states are announced to assistive technology. - A11Y-003: Long test steps, tables, and evidence references remain usable at narrow widths and with text resized to 200 percent without loss of content or required controls. - PRIV-001: The form rejects unexplained sensitive data fields and requires purpose, minimum-data rationale, disclosure, retention, and deletion behavior for each collected element. - PRIV-002: Evidence views redact or withhold sensitive values according to the declared boundary; absent permission or consent produces a clear held state rather than fabricated data. - DEST-001: Deleting a project, evidence reference, or dependency requires an explicit confirmation naming the record and consequence; cancel leaves all records unchanged. - DEST-002: Destructive actions preserve a revision or tombstone receipt where required and never delete linked qualification evidence silently. - AUTH-001: A user without declared approval authority can draft and submit for review but cannot mark final qualification approved. - AUTH-002: Attempted external send, provider write, entitlement change, credential use, database mutation, customer indexing, publication, or deployment is held with an authority receipt. - FAIL-001: Missing entitlement, unsupported OS, unavailable hardware, denied permission, network failure, unavailable account, malformed input, or missing evidence produces a specific recoverable error and preserves entered work locally. - FAIL-002: A partial save or interrupted review does not create a passed result; the record returns to draft or needs review with an audit note. - FAIL-003: If an instrument is unavailable, the project remains proposal-only and records the unavailable calculation as held rather than substituting an unverified result. - QUAL-001: A project is eligible for a proposed qualification disposition only when all mandatory tests pass, no blocking dependency is unresolved, privacy and accessibility checks pass, and an authorized reviewer signs the receipt. - QUAL-002: Even after all local acceptance tests pass, the record must not claim deployment, provider connection, credential validity, production state, customer indexing, publication, or qualification beyond the recorded proposal disposition. ## Negative and held-state tests - A named native Apple surface may be mistaken for a connected or implemented feature. - Entitlement, credential, provider, hardware, OS, or account availability may be assumed without evidence. - A qualification pass may be misrepresented as deployment, publication, or production readiness. - Permission denial or sensitive-data handling may expose private information or produce misleading success states. - Unowned deadlines and hidden dependencies may cause silent schedule drift. - Overwriting revisions can destroy the evidence trail needed for review. - Color-only status indicators, unlabeled controls, focus loss, or inaccessible tables can block reviewers. - Destructive deletion can remove linked evidence or records without informed confirmation. - Agents or interfaces may exceed authority by sending messages, writing externally, changing entitlements, or publishing results. - Errata-bearing or unavailable instruments may produce unsupported calculations if their status is ignored. ## Qualification claim boundary ### Potentially allowed only after the stated evidence - A proposal template defines a bounded qualification workflow. - The project records intended tests, dependencies, deadlines, owners, privacy boundaries, accessibility checks, and held actions. - The observed native contract includes project collections, deadlines, revisions, provenance, PointGuard context, and held external effects. - The listed instruments are verified-directory entries designated for educational date and duration calculations only. ### Still held - Implementation or deployment of the Apple-platform capability. - Successful entitlement request, credential validation, provider connection, device access, or OS support. - Production, database, customer, publication, or external-calendar effects. - Completion or pass status for tests without recorded evidence and reviewer disposition. - Qualification, certification, readiness, or availability beyond the explicit proposal record. - Any claim that a named app route is a connected web feature. ## 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 records preserve canonical IDs, provenance, revisions, lifecycle, tags, links, and attachments` - `PointGuard persistent cross-app context surface` - `Current GuthHub app routes are local prototypes or indexes; external effects remain held` - `/app/notebook/projects/` - `/app/notebook/agenda/` - `/app/notebook/approvals/` - `/app/notebook/agent-logs/` - `date-duration-calculator` - `countdown-days-until-timer`