mirror of
https://github.com/callstack/agent-device.git
synced 2026-09-14 20:06:34 +08:00
Michał Pierzchała
04fb10dde5
* docs: adopt Simlock-backed Host device allocation * docs: link ADR 0021 implementation tracker * docs: define terminal allocation failures
41 lines
4.7 KiB
Markdown
41 lines
4.7 KiB
Markdown
# ADR index — read this when…
|
|
|
|
| ADR | Read when you touch… |
|
|
| --- | --- |
|
|
| [0001 Provider-First Integration Scenarios](0001-provider-first-integration-scenarios.md) | integration testing strategy, provider transcripts, the scenario harness |
|
|
| [0002 Persistent Platform Helper Sessions](0002-persistent-platform-helper-sessions.md) | helper process lifecycle, keep-alive semantics |
|
|
| [0003 Daemon Command Registry](0003-daemon-command-registry.md) | daemon routing, request-policy traits |
|
|
| [0004 iOS Snapshot Backend Strategy](0004-ios-snapshot-backend-strategy.md) | snapshot capture plans, backend fallbacks, quality verdicts |
|
|
| [0005 iOS Runner Interaction Lifecycle](0005-ios-runner-interaction-lifecycle.md) | XCTest runner sessions, leases, adoption, idle-stop |
|
|
| [0006 Daemon RPC Protocol Version](0006-daemon-rpc-protocol-version.md) | remote daemon HTTP/JSON-RPC compatibility |
|
|
| [0007 Remote Device Leases](0007-remote-device-leases.md) | leases, tenancy, provider-owned devices |
|
|
| [0008 Command Descriptor Registry](0008-command-descriptor-registry.md) | adding/changing a command, any surface projection (CLI/MCP/client/batch), timeout policy |
|
|
| [0009 Apple Platform Consolidation](0009-apple-platform-consolidation.md) | Apple platform family, apple/appleOs axes, the apple-leak guard |
|
|
| [0010 Error system conventions](0010-error-system.md) | error codes, hints, normalizeError, typed error signals |
|
|
| [0011 Interaction Guarantee Contract](0011-interaction-guarantee-contract.md) | interaction dispatch paths, fast paths, guards, the guarantee matrix, parity tables |
|
|
| [0012 Interactive Replay](0012-interactive-replay.md) | replay healing/`--update`, diagnostic resolution disclosure, bounded `.ad` target-binding evidence, bounded divergence wire/error handling, plan-bound replay-only `--from` semantics, and agent-supervised re-record repair ("heal-by-doing") |
|
|
| [0013 Unified Gesture Plans](0013-unified-gesture-plans.md) | gesture API/routing, contact topology, multi-touch geometry, native pointer injection, two-finger pan |
|
|
| [0014 Session Ref-Frame Lifetime](0014-session-ref-frame-lifetime.md) | ref authorization epochs, complete/partial issuance, pre-side-effect expiration, replay/batch compatibility, and cross-platform stale-mutation policy |
|
|
| [0015 Direct Maestro Compatibility Engine](0015-direct-maestro-engine.md) | Maestro YAML parsing/execution, compatibility observation policy, conformance, performance gates, gesture integration |
|
|
| [0016 Active-Session Script Publication](0016-active-session-script-publication.md) | publishing an armed open-to-destination `.ad` script without closing its live session |
|
|
| [0017 Parameterized Recorded Inputs](0017-parameterized-recorded-inputs.md) | safely authoring sensitive fill inputs as `${VAR}` placeholders across recording, replay, and repair |
|
|
| [0018 Unified Request Event Journal (Proposed)](0018-unified-event-journal.md) | event/diagnostic vocabulary, journal scopes and sinks, progress-channel separation, observability-only state |
|
|
| [0019 Request-Bound Platform Runtime](0019-request-bound-platform-runtime.md) | platform-package boundaries/composition, device discovery, runtime facts/facets, request binding, provider ownership, platform-shaped session resources, durable reattachment, daemon-handler migration |
|
|
| [0020 Composable Recorded Fragments (Proposed)](0020-composable-recorded-fragments.md) | lifecycle-free recorded fragment capture/composition, entry guards, fragment-local addresses/digests, staleness, and native `.ad`/Maestro composition |
|
|
| [0021 Host — Simlock-Backed Managed Device Allocation and the Host Supervisor](0021-host-simlock-managed-device-allocation.md) | local-first Simlock-managed execution, Host identity/admin boundaries, shape allocation, durable managed-device lease mapping, lifecycle ownership, and supervised maintenance |
|
|
|
|
ADRs record *why*; the registries and gates they describe are the living source of truth — when
|
|
prose and a registry disagree, the registry wins and the ADR needs a follow-up.
|
|
|
|
Shape conventions, so consulting an ADR stays cheap:
|
|
|
|
- **Normative rules first, terse.** Status, then a "Rules at a glance" summary a reader can stop
|
|
after; full contracts and rationale below it.
|
|
- **Rationale and refuted alternatives stay in the ADR** — they are what stops re-litigating
|
|
settled ideas — but below the fold.
|
|
- **Process history is deleted once complete, not archived in-file.** Migration plans, per-step
|
|
landing tables, and point-in-time status change-logs go to git history; the Status section keeps
|
|
one line saying so plus any accepted, still-relevant waiver or evidence gap.
|
|
- Once a rule is gate-enforced, the ADR keeps the why and points at the gate rather than restating
|
|
the rule's details.
|