Remove phase vocabulary from Lazaret interfaces
This commit is contained in:
parent
3f9b1b3543
commit
e7dd95aea6
1 changed files with 547 additions and 579 deletions
|
|
@ -76,10 +76,10 @@ non-ancestral. Each volume container path is a strict descendant of exactly one
|
|||
persistent path; equality with that path is invalid. Resolution requires an
|
||||
internal `SandboxLayoutV1`, whose closed protected-destination set contains
|
||||
`/workspace` and every control, credential, mailbox, proc, sys, dev, runtime,
|
||||
and other product-owned sandbox mount destination selected by the production
|
||||
and other product-owned sandbox mount destination selected by the default
|
||||
layout. Persistent and volume paths must not intersect any protected
|
||||
destination in either ancestry direction. Configuration semantics do not assign
|
||||
destinations other than the specification-fixed `/workspace`; the production
|
||||
destinations other than the specification-fixed `/workspace`; the default
|
||||
sandbox-layout constructor owns that complete set and cannot construct a layout
|
||||
that omits `/workspace`. A volume source has the declared kind. `create=true` is
|
||||
valid only for a directory source anchored strictly beneath `{profile_dir}`; a
|
||||
|
|
@ -216,7 +216,7 @@ configuration authority.
|
|||
|
||||
`SandboxLayoutV1` is an internal, non-serializable product value with no public
|
||||
unchecked constructor. Configuration resolution cannot succeed without it. Its
|
||||
production constructor is owned by sandbox-layout construction and supplies the
|
||||
default constructor is owned by sandbox-layout construction and supplies the
|
||||
complete normalized protected-destination set; configuration loading neither
|
||||
guesses unnamed destinations nor permits a caller to remove `/workspace`. Every
|
||||
member is a normalized, absolute, non-root sandbox path using the sandbox-path
|
||||
|
|
|
|||
Loading…
Reference in a new issue