diff --git a/docs/architecture/ghostlight-world-consumer-api.md b/docs/architecture/ghostlight-world-consumer-api.md index 0306223..d40fb53 100644 --- a/docs/architecture/ghostlight-world-consumer-api.md +++ b/docs/architecture/ghostlight-world-consumer-api.md @@ -179,9 +179,11 @@ enters a log, a receipt, or the journal. The consumer capability's tag is part of the commit digest and the externally controlled assignment is part of the state shape, so both bump the -schema: state schema `ghostlight.world_state.consumer.v4` (state-schema -generation `world-v3`), commit schema `ghostlight.world_commit.consumer.v4`. -A store written under an earlier schema is refused, not migrated. +schema. World lens weights later entered the state and `SetLensWeights` +the commit, so the live schemas are state `ghostlight.world_state.consumer.v5` +(state-schema generation `world-v3`) and commit +`ghostlight.world_commit.consumer.v5`. A store written under an earlier schema +is refused, not migrated. ## Not in this pass diff --git a/docs/architecture/ghostlight-world-ontology.md b/docs/architecture/ghostlight-world-ontology.md index 5d2cb93..24d3645 100644 --- a/docs/architecture/ghostlight-world-ontology.md +++ b/docs/architecture/ghostlight-world-ontology.md @@ -257,8 +257,9 @@ travels over two wire schema constants, `CONSUMER_PATCH_SCHEMA` and is refused, not migrated. `WorldScaleIntent` now arrives at creation, not as a later admission: -`world_create.v3` declares the title, the brief, targets, and jurisdiction -roots top-level in the genesis patch beside `commons`; an invocation +`world_create.v4` declares the title, the brief, targets, jurisdiction +roots top-level in the genesis patch beside `commons`, and the world's lens +weights, which the library requires and never defaults; an invocation announcing an earlier schema is refused before any handler runs, and the intent is write-once, set once at genesis and resolved nowhere else. The brief is the world's authored premise, trimmed at ingress and never @@ -304,8 +305,8 @@ is the typed component diff against the fresh components plus the knowledge row, and never another subject's snapshot. The re-lowering's provider request is a distinct round (`interpreter_round`) with its own content-addressed request id, so it cannot collide with the first lowering's -request. State schema is `ghostlight.world_state.consumer.v4`, commit schema -`ghostlight.world_commit.consumer.v4`, controller work `controller_work.v15`, +request. State schema is `ghostlight.world_state.consumer.v5`, commit schema +`ghostlight.world_commit.consumer.v5`, controller work `controller_work.v15`, Persona turn receipt `ghostlight.persona_turn_receipt.v3`; earlier stores and earlier rows are refused. Ghostlight owns a conserved narrative ledger; Delvehold owns the economy (`delvehold-forced-ontology-integration.md`).