docs(governance): bind Host110 runtime V6 evidence
This commit is contained in:
67
docs/proposals/AWOOOI-AG99-H110-BACKUP-RUNTIME-V6.md
Normal file
67
docs/proposals/AWOOOI-AG99-H110-BACKUP-RUNTIME-V6.md
Normal file
@@ -0,0 +1,67 @@
|
||||
# AWOOOI Agent99 Host110 Backup Runtime V6
|
||||
|
||||
Status: proposed; owner approval required before any production apply.
|
||||
|
||||
This artifact supersedes V2 through V5. It is evidence for central review, not
|
||||
an active policy and not production execution authority.
|
||||
|
||||
## Scope
|
||||
|
||||
- Agent99 runtime bundle: 19 files. Deploy, bootstrap, sender, receiver,
|
||||
preflight, Signoz consumer, and contract checks must agree on this count.
|
||||
- Host110 backup payload: 18 files, comprising 17 backup scripts and
|
||||
`backup-health-textfile-exporter.py`.
|
||||
- Host110 remote stage: 21 files, comprising the 18 payload files, the fixed
|
||||
executor, the independent verifier, and the source manifest.
|
||||
- Fixed production target: `wooo@192.168.0.110`, dispatched from Windows99
|
||||
Agent99 with an exact Gitea revision and digest manifest.
|
||||
|
||||
## Exact Diff Serialization
|
||||
|
||||
The reviewer must substitute the V6 Gitea live-ref SHA for
|
||||
`<candidate_git_sha>` and hash these exact stdout bytes:
|
||||
|
||||
```sh
|
||||
git diff --binary --full-index \
|
||||
e7e3bcf8a5a8a19c1253d73f51d9dca248af0aa3..<candidate_git_sha> |
|
||||
shasum -a 256
|
||||
```
|
||||
|
||||
The proposal message must bind all of the following independently:
|
||||
|
||||
- Gitea live ref and exact 40-character candidate Git SHA.
|
||||
- This tracked artifact path and its SHA-256 bytes hash.
|
||||
- The exact diff serialization command above and resulting SHA-256.
|
||||
|
||||
## Apply Effects
|
||||
|
||||
- Agent99 runtime promotion writes the 19-file runtime bundle on Windows99 and
|
||||
writes its bounded deployment manifest and receipts.
|
||||
- Host110 Apply writes/replaces the 18 payload destinations through one
|
||||
exclusive, digest-bound filesystem transaction.
|
||||
- The transaction does not itself run a backup, sync Google Drive, prune or
|
||||
delete snapshots, restart a VM, or change a network, firewall, DB, or service.
|
||||
- The broader source diff also changes the Gitea backup route. A later scheduled
|
||||
or explicit Gitea offline-consistency backup may stop and restart the Gitea
|
||||
container within its bounded backup window. That deferred runtime effect is
|
||||
not part of the Host110 filesystem deployment transaction and requires its
|
||||
own verifier receipt.
|
||||
|
||||
## Validation
|
||||
|
||||
- Post-rebase focused suite: 51 passed, 4 skipped.
|
||||
- Central read-only review: 36 passed, 4 skipped; Host110 broker: 7 passed.
|
||||
- Ansible validation: green.
|
||||
- Changed PowerShell parser readback on Windows99: zero errors.
|
||||
- Prior broad regression baseline: 552 passed, 4 skipped.
|
||||
|
||||
## Rollback
|
||||
|
||||
- Source rollback reverts the exact V6 candidate diff to
|
||||
`e7e3bcf8a5a8a19c1253d73f51d9dca248af0aa3` without force-pushing.
|
||||
- Agent99 rollback restores the complete prior runtime bundle and prior runtime
|
||||
manifest, then independently verifies prior hashes.
|
||||
- Host110 rollback restores every prior payload's content, SHA-256, uid, gid,
|
||||
and mode under the exclusive lock.
|
||||
- Any mismatch terminates as `rollback_unverified`; it cannot be reported as a
|
||||
successful rollback.
|
||||
Reference in New Issue
Block a user