Make service command identity own execution intent
This commit is contained in:
parent
2a797370f6
commit
b03ab6265f
7 changed files with 175 additions and 124 deletions
|
|
@ -93,6 +93,14 @@
|
|||
- Receipt status is derived as `completed`; callers cannot submit status.
|
||||
- Forbidden evidence: missing, non-JSON, pre-intent, out-of-root, or mismatched-run artifacts.
|
||||
|
||||
## Daemon-supervisor install authority boundary (2026-07-12)
|
||||
|
||||
- Plan commands force non-execution and may only write planned artifacts/receipts.
|
||||
- Execute commands force execution intent and must pass the existing elevation gate before service-manager mutation.
|
||||
- Wrapper command identity matches the Rust command exactly; no hidden `--execute-install` switch selects reality.
|
||||
- Ambiguous install aliases are not accepted.
|
||||
- Negative proof: hostile plan flag cannot mutate; execute without elevation produces an explicit refusal receipt.
|
||||
|
||||
This is the source-grounded map of the live machine. Historical route and
|
||||
bridge anatomy belongs in git history and evidence ledgers, not here.
|
||||
|
||||
|
|
|
|||
|
|
@ -44,6 +44,10 @@ The monolithic `epiphany-verse-query smoke` fixture writer can no longer accept
|
|||
|
||||
`epiphany-operator-run receipt` no longer accepts `--status`. It loads the latest operator intent and requires matching run id/mode, canonicalizes the result and artifact-root paths, requires the result to be a file contained under the artifact root, parses it as JSON, and rejects it if its modification time predates the intent. Only then does it derive `status=completed`. The wrapper no longer passes a completion assertion. Negative proof rejects caller status and out-of-root artifacts; positive proof uses a post-intent JSON artifact. Next audit daemon-supervisor planning/rehearsal receipts against actual service/process evidence.
|
||||
|
||||
## 2026-07-12 daemon-supervisor plan/execute identity
|
||||
|
||||
Install command names now determine execution authority. `service-install-plan` and `cluster-service-install-plan` force `execute_install=false` even if a hostile flag is supplied. `service-install-execute` and `cluster-service-install-execute` force `execute_install=true` without a separate flag. Ambiguous aliases were deleted, and the wrapper invokes exact command names instead of always invoking plan plus `--execute-install`. Proof in the non-elevated shell: hostile plan remained `planned` / `executed=false`; execute without a flag returned `execution-refused-not-elevated` / `executed=false`. Receipt status now follows an inspectable command boundary rather than hidden argument combination.
|
||||
|
||||
This is the re-entry rite for `E:\Projects\EpiphanyAgent`: the waking chant for
|
||||
the local machine-spirit before it touches the forge.
|
||||
|
||||
|
|
|
|||
|
|
@ -19,9 +19,9 @@ A forged operator-status artifact containing `intentId=forged-intent`, `receiptI
|
|||
|
||||
## Remaining scrutiny
|
||||
|
||||
1. Inspect daemon-supervisor plan/rehearsal receipts separately from execution receipts so planning cannot masquerade as service mutation.
|
||||
2. Extend the same store quarantine invariant to standalone smoke binaries that accept output paths.
|
||||
3. Distill or remove dead public receipt constructors once every named provider executable exists.
|
||||
1. Extend the same store quarantine invariant to standalone smoke binaries that accept output paths.
|
||||
2. Distill or remove dead public receipt constructors once every named provider executable exists.
|
||||
3. Distill obsolete historical authority claims in `state/map.yaml`.
|
||||
|
||||
## Smoke quarantine update
|
||||
|
||||
|
|
@ -30,3 +30,9 @@ A forged operator-status artifact containing `intentId=forged-intent`, `receiptI
|
|||
## Operator-run evidence binding update
|
||||
|
||||
The standalone `receipt` command previously accepted caller status and path strings, then wrote `completed` evidence without inspecting the run. It now requires the latest persisted intent to match run id and mode, derives status internally as `completed`, requires an existing valid JSON result contained by the canonical artifact root, and requires the result modification time to be no earlier than the intent request time. `--status` no longer exists. The PowerShell orchestrator supplies only the result coordinates after its checked subprocess completes.
|
||||
|
||||
## Daemon-supervisor command authority update
|
||||
|
||||
Lifecycle receipt status values already distinguished planned, refused, observed, and executed outcomes, but install command aliases allowed command names and the `--execute-install` flag to disagree. Dispatch now makes command identity authoritative: `service-install-plan` and `cluster-service-install-plan` forcibly disable execution; `service-install-execute` and `cluster-service-install-execute` force execution intent and reach the elevation gate without a side-channel flag. Ambiguous `install-service`, `windows-service-install`, `service-install-windows`, and `cluster-windows-service-install` aliases are removed. The wrapper invokes the exact plan/execute command and no longer appends `--execute-install`.
|
||||
|
||||
Negative proof passed both directions: a plan command given hostile `--execute-install` remained `planned` with `executed=false`; an execute command without the flag reached `execution-refused-not-elevated` with `executed=false` in the non-elevated shell.
|
||||
|
|
|
|||
Reference in a new issue