Source: https://guthlabs.ai/docs/jobs/tim-swift-and-swiftui-implementation/field-guides/ job / candidate # Swift and SwiftUI implementation โ€” field guides The distinct field guides record for Swift and SwiftUI implementation. This page is proposal-only. Status: **proposed**Lifecycle: **candidate** ## Record status **Record ID**: job:tim:swift-and-swiftui-implementation **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 - Capture the request as a canonical job-linked implementation brief. - Confirm the owner, authorized Apple files, target platforms, target OS versions, and explicit exclusions before editing. - Inspect the relevant project and field-guide records in Notebook; preserve source locators, provenance, revisions, and attachments. - Assess candidate Swift, SwiftUI, App Intents, Core Spotlight, Apple Intelligence, and other Apple framework capabilities without claiming an unavailable API. - Create a platform capability record that distinguishes known capability, assumption, unknown, fallback, and hold state. - Draft the cross-platform interaction model for iPhone, iPad, and Mac, including accessibility, layout, input, loading, empty, error, and degraded states. - Implement only within the authorized Apple files and record every changed path. - Run bounded local checks appropriate to the change, such as build, previews, unit checks, simulator checks, and accessibility inspection where available. - Record evidence receipts, limitations, unresolved defects, and any divergence between intended and observed behavior. - Route entitlement, credential, Store submission, production, and scope-exception decisions to human approval; do not execute or imply those effects. - Update the job, project, implementation, and approval records with revisions and deterministic acceptance results. - Close as locally verified, held, or needs revision; never mark external publication or production deployment from this package. ## Handoff 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/` - `job:tim:swift-and-swiftui-implementation` - `Observed native contract: records preserve canonical IDs, provenance, revisions, lifecycle, tags, links, attachments, and record revisions.` - `Observed native contract: PointGuard is a persistent cross-app context surface while specialist apps remain execution and canonical-record owners.` - `Observed app route: /app/notebook/agent-logs/` - `Observed app route: /app/notebook/approvals/` - `Observed app route: /app/notebook/field-guides/` - `Observed app route: /app/notebook/projects/` - `Observed app route: /app/pointguard/`