Guth
NewsDocs
Page actions
View as Markdown ↗
Explore MCP tools ↗

job / candidate

Apple platform discovery — field guides

The distinct field guides record for Apple platform discovery. This page is proposal-only.

Status: proposedLifecycle: candidate

Record status

Record ID
job:tim:apple-platform-discovery
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. Create a source-labelled discovery brief in Notebook and assign Tim as owner.
  2. State the exact Apple platform question, target platforms, Guth surface, requested deadline, and explicit exclusions.
  3. Collect only supplied or authorized Apple evidence and record source locators, provenance, revisions, and SHA-256 values when available.
  4. Separate observed native terminology such as Xcode, SwiftUI, App Intents, Core Spotlight, Apple frameworks, iOS 27, iPadOS 27, macOS 27, Liquid Glass, and Apple capability index from any claim that a Guth web feature is connected or deployed.
  5. Describe candidate inputs, outputs, constraints, accessibility needs, and product relevance for each capability.
  6. Map each assessment to the responsible Guth app surface and canonical record owner; use PointGuard only as cross-app context, not as the execution or canonical-record owner.
  7. Create deadline and workback to-dos with due dates, priority, tags, completion state, and revision history.
  8. Log blockers and failure states, including unavailable or unverified APIs, missing entitlements, unclear platform version support, unauthorized scope, and approval dependencies.
  9. Route claims involving new entitlements, Store submission, production credentials, or scope outside authorized Apple files to human review and preserve an approval or held record.
  10. Draft a reusable field guide from the evidence, capability assessment, and receipts; do not publish or submit it as production documentation.
  11. Close the job with a decision summary, allowed claims, held claims, follow-up tasks, lifecycle state, and reviewer receipt.

Handoff boundary

  • Treating a named Apple framework or platform guide as proof that an API exists, is available to Guth, or is suitable for production.
  • Claiming Core Spotlight indexing, App Intents integration, Apple Intelligence behavior, customer search, provider connection, or database authority without verified evidence and approved implementation.
  • Using Xcode or SwiftUI work outside authorized Apple files or presenting local prototype work as deployed product state.
  • Submitting to the App Store, requesting or using production credentials, or adding entitlements without approval.
  • Publishing documentation that repeats unsupported claims or creates doorway pages without distinct useful content.
  • Racing another writer or overwriting source-labelled records instead of preserving revisions and provenance.
  • Failing to disclose version, platform, permission, entitlement, accessibility, or hardware constraints.
  • Allowing an Agent to send messages, write external schedules, upload protected files, or make irreversible changes without human review.
  • Confusing PointGuard context with canonical ownership.
  • Presenting educational or exploratory capability notes as qualification, compliance, security, or production certification.

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:apple-platform-discovery
  • Observed native contract: Notebook collections, deadlines, record provenance, PointGuard boundary
  • Observed app routes: /app/pointguard/, /app/notebook/notes/, /app/notebook/files/, /app/notebook/to-dos/, /app/notebook/approvals/, /app/notebook/projects/, /app/notebook/field-guides/, /app/notebook/agent-logs/, /app/notebook/search/
  • Observed app route state: local prototypes or indexes; provider, credential, database, customer, publication, and production effects held
  • Allowed verified-instrument directory reviewed; no instrument selected because the supplied job is platform discovery rather than a calculation task
  • job:tim:apple-platform-discovery
  • 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 native contract: provider, credential, database, customer, publication, and production effects are held.