diff --git a/docs/localization/COMMUNICATION_REGISTRY_SOURCE_DRIFT.md b/docs/localization/COMMUNICATION_REGISTRY_SOURCE_DRIFT.md index 6436cd4..4476cc7 100644 --- a/docs/localization/COMMUNICATION_REGISTRY_SOURCE_DRIFT.md +++ b/docs/localization/COMMUNICATION_REGISTRY_SOURCE_DRIFT.md @@ -1,6 +1,8 @@ # Communication Registry Source Drift Repair -Status: **source-level consistency repair merged into the canonical English source** +Status: **historical source-level consistency repair; later superseded in part by Registry Contract v1** + +> This note records an intermediate repair made during Simplified-Chinese localization. At that point, JSON-per-record was already canonical, while CSV registries were still described as legacy / optional rollups that could be manually edited on explicit operator request. Registry Contract v1 later replaced that exception: CSV registries and `registry/INDEX.md` are now generated, read-only compatibility views and must not be edited manually. ## Finding @@ -12,30 +14,41 @@ During Simplified-Chinese localization, three canonical English communication fi The stale instructions told visitors to update shared CSV registries. -Current canonical registry policy is defined by: +At the time of this repair, canonical registry policy was defined by: - `registry/README.md` - `docs/REGISTRY_RECORDS.md` - `docs/message_routing_model.md` -These define JSON-per-record registry files as canonical and CSV files as legacy / optional rollups. +Those sources defined JSON-per-record registry files as canonical and CSV files as legacy / optional rollups. + +## Repair at that stage + +The three canonical communication files were updated so that routine work: + +- created canonical JSON records under `registry/messages/` or `registry/notifications/`; +- treated CSV registries as legacy / optional rollups; +- did not edit CSV during routine visitor work unless the operator explicitly asked. + +No message field names, status values, delivery semantics, message-file directories, notification-file directories, or human-relay semantics were changed by that repair. -## Repair +## Current policy after Registry Contract v1 -The three canonical communication files were updated so that routine work now: +Registry Contract v1 subsequently strengthened the compatibility-view rule: -- creates canonical JSON records under `registry/messages/` or `registry/notifications/`, -- treats CSV registries as legacy / optional rollups, -- does not edit CSV during routine visitor work unless the operator explicitly asks. +- canonical records remain JSON-per-record; +- CSV registries and `registry/INDEX.md` are generated, read-only compatibility views; +- generated views must not be edited manually; +- when canonical JSON changes, regenerate the views with `scripts/generate_registry_views.py` and commit the resulting generated output. -No message field names, status values, delivery semantics, message-file directories, notification-file directories, or human-relay semantics were changed. +See `docs/REGISTRY_RECORDS.md`, `docs/registry/REGISTRY_CONTRACT_V1.md`, and `registry/README.md` for current normative behaviour. -## Deliberate non-change +## Deliberate non-change at the time -The message file surface includes an `archived` state/directory while the current registry path documentation lists `open`, `answered`, and `closed` registry directories. +The message file surface included an `archived` state/directory while the then-current registry path documentation listed `open`, `answered`, and `closed` registry directories. -That separate source-level ambiguity was not expanded or resolved during this repair because doing so would require a new registry-state design decision rather than a localization consistency fix. +That separate source-level ambiguity was not expanded or resolved during the original localization repair because doing so required a registry-state design decision rather than a localization consistency fix. Registry Contract v1 later resolved the lifecycle/path model explicitly. ## Localization rule -Chinese communication files should translate the repaired English source, not the stale pre-repair CSV instructions. +Localized communication files should follow the current canonical English source and Registry Contract v1. Historical wording in this note is provenance, not operative guidance. diff --git a/docs/registry/REGISTRY_SURFACE_AUDIT.md b/docs/registry/REGISTRY_SURFACE_AUDIT.md index 384d983..b172a14 100644 --- a/docs/registry/REGISTRY_SURFACE_AUDIT.md +++ b/docs/registry/REGISTRY_SURFACE_AUDIT.md @@ -1,5 +1,7 @@ # Registry Surface Audit +> **Historical pre-v1 audit.** The findings below describe the repository at the stated baseline and are preserved as design provenance, not as a current defect list. Registry Contract v1 and its supporting schemas, validators, generated views, templates, and lifecycle rules have since resolved several items recorded here. For current normative behaviour, see `docs/registry/REGISTRY_CONTRACT_V1.md` and `docs/REGISTRY_RECORDS.md`. + Baseline: `main` at `824a36dc4c7bebb661fab7511aea6eac3984fa1b`. ## Scope diff --git a/examples/example_message_packet.md b/examples/example_message_packet.md index 8fbfdbb..237189e 100644 --- a/examples/example_message_packet.md +++ b/examples/example_message_packet.md @@ -24,7 +24,7 @@ Reply with either `looks consistent` or the field that needs correction. ## Reply Instructions -Create a response message and create or update the canonical JSON message record under `registry/messages/`. Do not edit a legacy CSV registry unless the operator explicitly asks. +Create a response message and create or update the canonical JSON message record under `registry/messages/`. Do not edit generated CSV registry views manually. ## Notes diff --git a/lobby/README.md b/lobby/README.md index ae7615c..1546ef5 100644 --- a/lobby/README.md +++ b/lobby/README.md @@ -10,6 +10,6 @@ Every assistant session checks in through the lobby before handling LabNote work 3. Read `VISITOR_CHECKLIST.md`. 4. For ordinary deposits, follow `ROUTINE_DEPOSIT_QUICKSTART.md`. 5. Create JSON registry records under `../registry/`. -6. Do not edit CSV rollups unless the operator explicitly asks. +6. Do not edit generated CSV registry views manually. The lobby is a paper trail, not a login system.