Swift and SwiftUI implementation — tools

The distinct tools record for Swift and SwiftUI implementation. This page is proposal-only.

Status: proposedLifecycle: candidate

Record status

Record ID: job:tim:swift-and-swiftui-implementation
Parent lifecycle: candidate
Page lane: package
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.

Authoritative package lane tools and interfaces

Canonical tools-page assignments

Xcode (interface · required) — Proposed native implementation and local verification surface for authorized Apple files.
SwiftUI (interface · required) — Proposed declarative UI implementation surface across Apple form factors.
App Intents (skill · optional) — Use only when the brief explicitly requires system actions or discoverability and capability evidence supports it.
Core Spotlight (skill · optional) — Use only for an explicitly scoped local indexing design; customer indexing and production search effects remain held.
Apple frameworks (skill · optional) — Use only documented or locally evidenced framework capabilities; unavailable APIs must be recorded as unknown or held.
Notebook Projects (interface · required) — Owns project grouping, linked work, evidence, and lifecycle visibility.
Notebook Field Guides (interface · required) — Provides source-backed bounded procedures and prerequisites.
Notebook Approvals (interface · required) — Owns review states and receipts for held authority boundaries.
Notebook Agent Logs (interface · required) — Preserves Tim's work, authority, receipts, and current state.
PointGuard (interface · required) — Carries the current implementation context across Guth surfaces without becoming the canonical execution owner.

Only the page's admitted lane is rendered as an assignment. Other lane inventories remain source records but are not merged here. Tool kind and required/optional status are preserved.

Authoritative lane instrument assignments

Canonical tools-page assignments

No verified instrument is assigned to this tools lane.

An instrument listed only for another lane does not become a tools-page assignment.

Use boundary

A named native surface or framework may be mistaken for a connected web feature; all app routes remain local prototypes or indexes unless separately evidenced.
New entitlements may create security, privacy, review, or submission consequences and require human approval.
Production credentials, Store submission, publication, and external writes are outside Tim's authority in this package.
Core Spotlight or App Intents designs must not be represented as customer indexing, system registration, or live integration without evidence.
Apple Intelligence behavior and API availability may vary by OS, device, region, entitlement, or SDK; record uncertainty and provide a fallback.
Scope outside authorized Apple files is prohibited; stop and request approval rather than editing adjacent files.
Do not race another writer; coordinate through linked records and revisions.
Accessibility regressions can be introduced by custom SwiftUI components, Liquid Glass treatments, dynamic layout, or platform-specific navigation.
Platform divergence between iPhone, iPad, and Mac can undermine product-family coherence if each surface is implemented independently.
Local builds, previews, or simulator checks do not prove device coverage, Store readiness, production behavior, or customer qualification.
Sensitive source files or credentials must not be uploaded or copied into unapproved storage; Notebook Files may hold references while protected storage or upload remains held.
A failed build, unavailable capability, missing dependency, or unresolved review must produce a visible Held or Needs review state rather than a completion claim.

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:swift-and-swiftui-implementation
Observed native contract: project_and_field_guide_collections
Observed native contract: deadlines
Observed native contract: records
Observed native contract: pointguard
App route: /app/
App route: /app/pointguard/
App route: /app/notebook/projects/
App route: /app/notebook/field-guides/
App route: /app/notebook/approvals/
App route: /app/notebook/agent-logs/
App route: /app/notebook/files/