Bind cross-process configuration by identity

This commit is contained in:
ms2k 2026-07-16 22:55:40 +09:00
commit 308c5a1b56

View file

@ -329,11 +329,13 @@ is a deliberate conservative compatibility boundary. Relaxing it requires a
new executable-alias authority policy in a later version; v1 has no exception or new executable-alias authority policy in a later version; v1 has no exception or
fallback. fallback.
`ResolvedDomainConfiguration` is created before a generation, durable intent, Configuration resolution occurs before a generation, durable intent, external
or external runtime resource. Every production configuration consumer receives runtime resource, or session admission relies on it. Across a process boundary,
that same owned resolved value or a capability-bounded borrow from it; consumers a production consumer may resolve its own `ResolvedDomainConfiguration`, but it
do not reparse the TOML document or independently repeat default, path, network, must first match the exact expected Domain ID and Configuration Fingerprint. A
environment, fingerprint, or approval decisions. mismatch refuses before creating or joining the generation. Each consumer uses
one resolved value for its subsequent path, network, environment, fingerprint,
and approval decisions; it does not combine decisions from different loads.
### 3.3 Domain and Session Lifecycle Refinement ### 3.3 Domain and Session Lifecycle Refinement