Skip to content

Commit e3b8a72

Browse files
committed
docs(isolation): describe attach-only lifecycle
Signed-off-by: Drew Newberry <anewberry@nvidia.com>
1 parent 1f94cd9 commit e3b8a72

1 file changed

Lines changed: 6 additions & 7 deletions

File tree

  • crates/openshell-isolation-interface/src

‎crates/openshell-isolation-interface/src/lib.rs‎

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -18,13 +18,12 @@
1818
//!
1919
//! # Ordering is a security property
2020
//!
21-
//! The lifecycle states run in order: either create or attach -> Bound ->
22-
//! confirm -> Ready -> `start_agent` -> Running. Creation is optional; a
23-
//! distributed topology can remain compute-driver-provisioned and attach-only.
24-
//! Nothing untrusted runs inside the boundary until it is confirmed ready. This
25-
//! is enforced *by construction*: each transition consumes the prior state by
26-
//! value, and no state type has a public constructor, so the supervisor cannot
27-
//! skip a stage or run a workload before [`contract::ReadyBoundary`] exists.
21+
//! The lifecycle states run in order: attach -> Bound -> confirm -> Ready ->
22+
//! `start_agent` -> Running. Nothing untrusted runs inside the boundary until it
23+
//! is confirmed ready. This is enforced *by construction*: each transition
24+
//! consumes the prior state by value, and no state type has a public
25+
//! constructor, so the supervisor cannot skip a stage or run a workload before
26+
//! [`contract::ReadyBoundary`] exists.
2827
//!
2928
//! [`AgentSpec`] is shared between the workload definition the supervisor
3029
//! submits and the [`contract::SandboxContext`] that `attach` binds to a

0 commit comments

Comments
 (0)