This recipe carries one checked application root through planning, Build, release, interruption, reconciliation, and deliberate inspection.
Command outputs are illustrative end-product examples. Exact identifiers are owner-qualified references, shortened here only for readability.
1. Check the locked project
$ one check --root OrdersApi
checked parcelhub#OrdersApi@1
source parcelhub.one rev:8a31…
lock one.lock rev:41f2…
closure 7 semantic, 3 implementation, 5 provider requirements
report check:sha256:7c0d…Checking resolves the lock and validates semantic and implementation claims. It does not select a deployment provider, execute Build, or grant authority.
2. Test and invoke the exact operation
$ one test --root OrdersApi
12 passed; report test:sha256:31b9…
$ one invoke parcelhub.orders#Orders.Get@1 request.json
result ready
operation parcelhub.orders#Orders.Get@1
impl parcelhub.orders_impl#GetRust@1
receipt invoke:sha256:91ab…3. Explain and accept a physical plan
$ one plan --root OrdersApi --target local-release
candidate plan:sha256:ad14…
selected process host one.process#Supervised@1
selected state one.data.local#Transactional@1
selected transport one.http#Loopback@1
authority none
estimated monthly cost EUR 0.00$ one inspect plan:sha256:ad14… --subject state
requirement parcelhub.order_state#Orders@1
accepted one.data.local#Transactional@1
evidence conformance:sha256:11c2…
rejected one.data.memory#Ephemeral@1: durability unsatisfiedThe plan commits exact normalized configuration and evidence. It remains authority-free and cannot mutate the machine.
4. Build without reselecting
$ one build --root OrdersApi
artifact artifact:sha256:2e77…
report build:sha256:cc80…
reproducible true
provenance provenance:sha256:0721…
sbom sbom:sha256:44a0…Build executes the locked action graph and produces owned artifact records. Artifact bytes alone are not Build evidence.
5. Create and apply a release plan
$ one observe state:OrdersApi
observation observation:sha256:08dd…
$ one release local build:sha256:cc80…
release plan:sha256:18f4…
build build:sha256:cc80…
provider_config provider-config:sha256:d891…
authority epoch:local-23
$ one approve plan:sha256:18f4…
approval approval:sha256:991e…
$ one apply plan:sha256:18f4…
operation operation:sha256:731c…
state awaiting_observationIf the apply response is lost, resume the same operation instead of issuing a new apply:
$ one reconcile operation:sha256:731c…
state reconciled
release release:sha256:f421…Deployment journals intent before dispatch, validates fresh matching authority, retains the fence, and reconciles provider observation.
6. Inspect from product to evidence
$ one inspect release:sha256:f421…
status healthy
plan plan:sha256:18f4…
artifact artifact:sha256:2e77…
journal deployment:journal:sha256:c201…
postconditions satisfied
history history:fact-set:sha256:a883…$ one inspect why release:sha256:f421… --subject state
OrdersApi requires durable transactional Orders state
the release plan selected one.data.local#Transactional@1
the active binding matches provider configuration d891…
the latest independent observation is currentInspection does not create authority or invent absent evidence. A stale observation, revoked claim, unresolved reference, or missing receipt remains explicit.
Executable evidence
Developer Interface's Accountable lifecycle acceptance exercises invocation, Build, local filesystem release, History facts, inspection, and idempotent resume through the public CLI. Supply the exact current standard distribution and explicitly enable the acceptance:
ONE_ACCOUNTABLE_ACCEPTANCE_DISTRIBUTION=/path/to/distribution \
cargo test -p one-cli --test custom_agent_lifecycle \
accountable_root_reaches_invoke_build_apply_inspect_and_history \
-- --exact --ignored --nocaptureThe path is caller-supplied. A default Cargo run skips this acceptance, and a passing run establishes only the selected application's exact release path. It does not establish the illustrative Orders deployment above or installed release acceptance.