Chapter 30 - Worked Answers

1. Two revision domains

The Orch source SHA identifies the controller implementation, parser and mutation behavior. The local manifest repository’s checkout commit identifies the intent applied by that implementation. Both are needed for reproducibility; a mutable branch name identifies neither exact bytes nor historical behavior. The teaching run records real full manifest commit IDs without pushing a repository or pretending they are app-source revisions.

2. Partial apply provenance

The first sorted file can already mutate its service before parsing the second fails. LastError records the sync failure, while LastRevision can still describe the earlier successful sync because revision update happens after the loop/prune. Inspect live service specs/managed markers and retained command output to reconstruct partial effects. A failed sync is not proof of no changes, and deterministic order is not a transaction. An atomic design needs an explicit validation/apply protocol.

3. Mutating status

GitOpsStatus can restore DesiredSpec, increment version and reconcile under auto_revert. Therefore calling it can change accepted intent. That branch does not freshly call admission/quota as ordinary ApplyService does, so changed constraints require separate reasoning/testing. The executed Atlas fixture shows warn retaining manual replicas two and auto_revert restoring desired zero. It does not prove a continuous passive drift observer or physical container equivalence.

4. Prune ownership test

Mark a previously managed same-name service with a different current source owner, remove its manifest from the first source, then sync with prune. The baseline tests prior/wanted name sets within namespace but does not verify current source ID/object ID before deletion. A safer design should reject ownership mismatch or require explicit transfer semantics. The passing fixture only proves a never-managed unrelated name survives; it does not prove same-name replacement/transfer safety.

These answers use chapter 30 and its scoped claim/execution records. Design changes remain proposals until separately implemented and tested.