Make generated run lifecycle autonomous
This commit is contained in:
+16
@@ -0,0 +1,16 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: Generated Run build input includes autonomous lifecycle plan
|
||||
The platform-owned distribution builder SHALL receive a generated Run autonomous lifecycle plan for `run` component packages and SHALL keep that plan inside platform-side build input rather than requiring a machine-side Run endpoint to claim lifecycle bootstrap work.
|
||||
|
||||
#### Scenario: Platform builder assembles Run package input
|
||||
- **WHEN** an owner requests Run generation for a server instance
|
||||
- **THEN** the platform builder input and generated workspace seed include plugin lifecycle action refs, selected profile key, dependency probes, install plans, process log sources, deployment revision, and redacted deployment execution inputs for that server
|
||||
|
||||
#### Scenario: Client-manager build input
|
||||
- **WHEN** an owner requests client-manager generation
|
||||
- **THEN** the build input does not include a server Run autonomous lifecycle plan
|
||||
|
||||
#### Scenario: Build input remains platform-owned
|
||||
- **WHEN** a machine-side Run endpoint attempts to claim or read a platform-owned distribution build
|
||||
- **THEN** Platform denies that access and does not expose the plaintext component auth key or autonomous lifecycle plan through the machine job channel
|
||||
Reference in New Issue
Block a user