Decision
Govern generated outputs, text patches, and clean-release upgrades through shared portable contracts.
Groundwork Rule
Keep application lifecycle work inspectable
Complete user-readable behavior generated from the authoritative rule module.
Rule decision
Behavior
Required behavior
Treat patch text and old installations as untrusted read-only input until approved; Use the lifecycle registry and separate bounded histories; Keep patch inspection and upgrade planning read only; Preserve the new release identity during upgrades and the base release identity during patches
Prohibited behavior
Let a patch authorize itself or weaken safeguards; Upgrade an old installation in place; Copy old executable behavior, custom rules, or interface customizations into a clean release; Store patch bodies, private domain content, host paths, secrets, or hidden reasoning in lifecycle histories
Boundary or exception
Stop on unsafe paths, stale review identity, newer source formats, or unresolved customization conflicts.
No items match this search.