implements PLN-0005
This commit is contained in:
@@ -52,6 +52,7 @@ Rules:
|
||||
- normal read requests should be served from that coherent snapshot when the runtime is active;
|
||||
- the runtime snapshot is an operational projection of packer-owned workspace artifacts, not a replacement authoring store;
|
||||
- the durable authoring workspace remains the persisted source of truth after successful commit.
|
||||
- backend consumers may derive smaller frontend-facing compile surfaces from the runtime snapshot without exposing the raw snapshot as a frontend contract.
|
||||
|
||||
### Embedded Bootstrap Rule
|
||||
|
||||
@@ -223,6 +224,17 @@ Rules:
|
||||
- adapters may remap event shapes for UI consumption, but must not invent causal relationships not present in packer events.
|
||||
- embedded hosts should preserve the same typed event bus reference across packer bootstrap and adapter wiring so subscription and publication stay causally coherent.
|
||||
|
||||
## Compile-Surface Integration Boundary
|
||||
|
||||
The packer snapshot is not itself the normative frontend compile contract.
|
||||
|
||||
Rules:
|
||||
|
||||
- the backend may derive a smaller frontend-facing compile surface from packer-owned state;
|
||||
- for asset references, that smaller surface may contain only `Addressable(address, asset_id)` entries;
|
||||
- Studio and compiler frontends may consume the derived surface through backend-owned contracts;
|
||||
- consumers must not treat the raw packer snapshot as the stable frontend API boundary.
|
||||
|
||||
### Event Ordering and Coalescing
|
||||
|
||||
Rules:
|
||||
|
||||
Reference in New Issue
Block a user