Apple tools decide
Xcode, xcodebuild, XCTest, Simulator, simctl, and .xcresult evidence
are authoritative.
Cloud build architecture
Axint Cloud Build should let any client control a real Apple build without pretending Xcode runs natively on Windows or Linux. Authoring and portable checks can run anywhere; decisive Apple compilation, Simulator execution, signing, and distribution run on managed Apple hardware.
Product promise
Section titled “Product promise”Connect or upload a project, select a reproducible toolchain, run the real Xcode build and tests, interact with the actual Simulator in a browser, and receive a proof receipt or exact repair packet.
The unit of value is a running app with trustworthy evidence, not a raw compute minute.
Non-negotiable principles
Section titled “Non-negotiable principles”Untrusted builds are isolated
Tenants never share writable filesystems, keychains, credentials, process namespaces, or writable caches.
Jobs are reconnectable
Every operation has a durable ID, lease, heartbeat, event stream, cancellation path, and terminal state.
Evidence is first-class
Build receipts, tests, screenshots, recordings, crash traces, accessibility snapshots, and repair packets share one artifact manifest.
Core execution flow
Section titled “Core execution flow”- Authorize a selected repository or confirm a screened local upload.
- Pin an immutable commit or source snapshot.
- Discover project containers, schemes, package managers, and destinations.
- Resolve the macOS, Xcode, SDK, Simulator, and architecture image.
- Allocate an isolated Apple-silicon runner.
- Restore only policy-approved caches.
- Build and run focused tests.
- Boot the Simulator, install the app, and launch it.
- Attach browser streaming and safe interaction controls.
- Finalize the artifact manifest, receipt, and repair packet.
Security boundaries
Section titled “Security boundaries”- repository credentials are exchanged for short-lived fetch credentials
- build scripts never receive the provider installation token
- forked pull requests run without workspace secrets
- signing runs in a separate high-trust lane
- source retention is explicit and user-controlled
- product-learning data is source-free unless a user deliberately shares an artifact
- retries are idempotent and cannot double-charge or open duplicate pull requests
Agent API
Section titled “Agent API”The build API should return immediately with a durable job ID. Agents poll or subscribe to structured events, then request the compact repair packet rather than complete logs. The packet contains:
- confirmed evidence
- probable causes
- advisory findings
- likely files
- exact rerun command
- artifact references
- stop conditions for repeated or low-confidence repair attempts
Platform rollout
Section titled “Platform rollout”Initial production should prioritize:
- native
.xcodeprojand.xcworkspace - Swift packages
- iOS and iPadOS Simulator
- unsigned Simulator builds
- focused build and test evidence
- Git repositories plus screened resumable local uploads
Signed archives, TestFlight upload, physical devices, interactive macOS and visionOS sessions, and cross-platform framework recipes should graduate only after the core path is dependable.
Full engineering specification
Section titled “Full engineering specification”The repository contains the complete vision, data model, lifecycle, infrastructure, security, runner, streaming, billing, observability, testing, and contributor handoff: