Source: https://guthlabs.ai/docs/jobs/tim-swift-and-swiftui-implementation/forms/ job / candidate # Swift and SwiftUI implementation โ€” forms The distinct forms 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**: 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. ## Proposed form sections Each section is a candidate schema for inspectable records. Required-field presence does not establish factual truth. ### Implementation brief Define the requested native behavior and its bounded scope. - request title - user problem - target product surface - target platforms: iPhone, iPad, Mac - target OS versions - authorized repositories or file paths - out-of-scope files and systems - success criteria - requester - requested due date ### Platform capability assessment Record only capabilities supported by supplied source material or verified local evidence. - Swift or SwiftUI surface - Apple framework or API candidate - App Intents involvement - Core Spotlight involvement - Apple Intelligence involvement - availability assumptions - entitlement implications - evidence links - unknowns requiring review ### Experience and accessibility review Check coherent product-family behavior across supported Apple form factors. - navigation and information architecture - iPhone behavior - iPad behavior - Mac behavior - Liquid Glass treatment if applicable - Dynamic Type behavior - VoiceOver labels and order - keyboard and pointer behavior - color and contrast notes - reduced motion and localization notes ### Implementation and verification Track bounded work, evidence, and failure states without implying production deployment. - ordered implementation tasks - files changed - files intentionally not changed - local build result - unit or preview checks - device or simulator checks - availability and fallback behavior - error and empty states - test evidence references - remaining defects ### Review and release hold Separate local implementation approval from external or production authority. - review status: Needs review, Approved, Held - reviewer - entitlement decision - credential decision - store-submission decision - production-effect decision - scope exception decision - approval receipt - next action - approval deadline ### 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 docs_urls lane and remain separate from the primary operating form. ### Job brief Capture the implementation objective, owner, authorized Apple files, and current packaging state. - job title - owner agent - owner role - owner status - objective - authorized file scope - source reference - current lifecycle ### Platform capability scope Separate verified platform capabilities from proposals and identify the target Apple platforms. - target platform: iPhone - target platform: iPad - target platform: Mac - Swift scope - SwiftUI scope - Apple Intelligence scope - Spotlight indexing scope - App Intents scope - capability evidence or source locator ### Product-family coherence Describe how the implementation should remain coherent across Apple devices without asserting completed behavior. - shared product principles - platform-specific adaptations - navigation and interaction notes - accessibility considerations - cross-device risks - open design decisions ### Principal gates Record blockers and approval requirements before any consequential Apple-platform action. - new entitlement required - store submission requirement - production credential requirement - scope exception request - approval owner - gate status: needs review/approved/held - blocking reason - receipt or source locator ### Packaging and handoff Prepare a reviewable implementation package with revisions, receipts, and unresolved risks. - implementation summary - changed files or file references - test evidence - known failures - reproduction steps - revision identifier - handoff recipient - next action ## Required or proposed record references No record existence is asserted by this documentation page. - Canonical job record with owner, role, lifecycle, source locator, source SHA-256, provenance, revision, links, and attachments - Implementation brief defining authorized Apple files and requested behavior - Platform capability record for each targeted OS and framework - Design and accessibility review record - Entitlement and capability review record - Test and evidence receipt record - Approval record for any held boundary or release action - Revision record for each material change - job:tim:swift-and-swiftui-implementation - agent log for Tim's work - linked implementation project record - field guide covering Apple capability review - approval records for entitlements and store submission - source-labelled notes and revisions ## 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/`