Archetype B - historical package-install agent design

Status: Fictional historical acceptance-design lesson, not a runnable workload or supported package promotion implementation. The old control-plane files were retired.

This archetype contrasted a pinned global package version and multiple instance homes with Archetype A's exact-commit release. The proposed lesson was to capture running version and rollback target before changing an instance, rather than infer readiness from package installation. The former promotion/rollback plan was not an implemented production path; no claim of agent-agnostic validation follows from these fictional designs.

The operator-reported public architecture uses a generic host, operator-core VM, logical realms for workload grouping, and individual agent sandboxes. Profile or realm grouping is not itself proof of a security boundary.