ms2k/lazaret
SHA256
Watch
0
Code Releases 3 Activity

Bind cross-process configuration by identity

Browse source
This commit is contained in:
ms2k 2026-07-16 22:55:40 +09:00
commit 308c5a1b56
1 changed files with 7 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

12
docs/specification.md
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
fallback.
`ResolvedDomainConfiguration` is created before a generation, durable intent,
or external runtime resource. Every production configuration consumer receives
that same owned resolved value or a capability-bounded borrow from it; consumers
do not reparse the TOML document or independently repeat default, path, network,
environment, fingerprint, or approval decisions.
Configuration resolution occurs before a generation, durable intent, external
runtime resource, or session admission relies on it. Across a process boundary,
a production consumer may resolve its own `ResolvedDomainConfiguration`, but it
must first match the exact expected Domain ID and Configuration Fingerprint. A
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