Native capability qualification — field guides

Record status

Record ID

job:tim:native-capability-qualification

Parent lifecycle

candidate

Page lane

docs_urls

Lane lifecycle

proposed

Owner

Tim

Owner role

Apple platform specialist

Owner status

PACKAGING

Qualification result

NOT RUN · held for evidence and human review

Working browser surface: Agent jobs — builder overview — Inspect the package and stage a local project. 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

1. Open the source-bound job and confirm Tim is the owning Apple platform specialist.
2. Record the capability question, intended user outcome, target Apple platforms, target OS assumptions, and requested decision date.
3. Collect only supplied or explicitly approved source references; preserve locator, SHA-256, provenance, and revision metadata.
4. Create a platform matrix for iPhone, iPad, and Mac, separating observed facts, proposed behavior, unknowns, and held states.
5. Map each proposed behavior to the named Apple frameworks or tools in the source record, without asserting API availability or production integration.
6. Identify entitlement, credential, store-submission, privacy, or scope implications and mark them as approval-gated.
7. Draft a field-guide procedure with prerequisites, evidence requirements, failure states, accessibility checks, and deterministic acceptance tests.
8. Create or update the qualification record and agent log with receipts, revisions, unresolved questions, and authority boundaries.
9. Route gated decisions to Notebook Approvals; do not grant entitlements, use production credentials, submit, publish, or expand scope.
10. Hand off the proposal to the relevant product, engineering, or approval owner and retain the qualification record as proposal-only until explicitly reclassified.

Handoff boundary

• Treating a named native surface, framework, or tool as proof of a connected web feature or production capability.
• Claiming an unavailable API, OS capability, entitlement, provider connection, or customer indexing behavior.
• Using production credentials, submitting to a store, publishing, or changing scope without approval.
• Confusing local prototype or index routes with deployed Apple-platform behavior.
• Failing to distinguish iPhone, iPad, and Mac availability, interaction, accessibility, or lifecycle differences.
• Relying on stale or untraceable source material without preserving provenance and revision metadata.
• Allowing PointGuard context to become the canonical execution or record owner.
• Racing another writer or overwriting a newer qualification revision.
• Publishing distinct documentation routes that contain no distinct useful content.
• Ignoring accessibility, privacy, data minimization, or failure-state review when proposing capability behavior.

Sources and evidence

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

• agents/index.html#tim
• source_record:job:tim:native-capability-qualification
• Observed native contract: project_and_field_guide_collections
• Observed native contract: deadlines
• Observed native contract: records
• Observed native contract: pointguard
• App route metadata for /app/pointguard/
• App route metadata for /app/notebook/projects/
• App route metadata for /app/notebook/field-guides/
• App route metadata for /app/notebook/agent-logs/
• App route metadata for /app/notebook/approvals/
• App route metadata for /app/notebook/files/
• App route metadata for /app/notebook/notes/
• Observed native contract: records preserve canonical IDs, source locators, source SHA-256, provenance, revisions, lifecycle, tags, links, and attachments.
• Observed native contract: PointGuard is a persistent cross-app context surface while specialist apps remain execution and canonical-record owners.
• Observed native contract: current GuthHub routes are local prototypes or indexes and provider, credential, database, customer, publication, and production effects remain held.
• Observed app route: /app/notebook/field-guides/
• Observed app route: /app/notebook/approvals/
• Observed app route: /app/notebook/agent-logs/
• Observed app route: /app/notebook/projects/
• Observed app route: /app/notebook/search/
• Observed app route: /app/pointguard/