Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 10 additions & 3 deletions docs/ADRs/013_sampled_forecast_wire_contract.md
Original file line number Diff line number Diff line change
Expand Up @@ -689,10 +689,10 @@ a "simplification."
this contract governs the **data** crossing the Appwrite seam; the
**identity/config** crossing the same seam (which key, which coordinates,
sourced from where, named how) is governed by
**[the Appwrite Seam Contract](https://github.com/views-platform/views-appwrite/blob/20dfd0f/docs/ADRs/platform/appwrite_seam_contract.md)**,
**[the Appwrite Seam Contract](https://github.com/views-platform/views-appwrite/blob/90fc105/docs/ADRs/platform/appwrite_seam_contract.md)**,
homed in views-appwrite and referenced here **by pinned URL, never by copy** —
with its coordinate registry
([`coordinate_registry.toml`](https://github.com/views-platform/views-appwrite/blob/20dfd0f/docs/ADRs/platform/coordinate_registry.toml), v1.4.0)
([`coordinate_registry.toml`](https://github.com/views-platform/views-appwrite/blob/90fc105/docs/ADRs/platform/coordinate_registry.toml), v1.4.1)
as the canonical source of the non-secret coordinates this repo's runtime
resolves. This repo's declared environment (`unfao/appwrite_env.py`, fail-loud
entry validation) follows that registry's names.
Expand All @@ -705,7 +705,14 @@ a "simplification."
a pinned commit, which is what "referenced by URL, never by copy" was always supposed
to mean — an unpinned `main` link drifts silently under the reader.

**Re-pinned again 2026-08-03 — the drift detector's first real firing.** The registry
**Re-pinned a third time, hours later, to v1.4.1 @ `90fc105`.** The registry moved
twice in one day (v1.4.1 adds a register reframing upstream; our 13 names were
re-verified unchanged in class and membership both times). The detector is doing its
job, but a pin that must be chased per-PR is a cost worth naming: if views-appwrite
settles into a slower cadence this is fine, and if it does not, the check may want to
compare a MAJOR/MINOR floor rather than an exact version. Recorded, not acted on.

**Re-pinned 2026-08-03 — the drift detector's first real firing.** The registry
moved to **v1.4.0** on 2026-08-02 (four CRAFD coordinates graduated from reserved to
real, and the CRAFD caller key was recorded as issued). `test_env_declaration.py`
failed on the next run, naming the version and telling the reader what to do, which is
Expand Down
8 changes: 4 additions & 4 deletions views_postprocessing/unfao/appwrite_env.py
Original file line number Diff line number Diff line change
Expand Up @@ -5,9 +5,9 @@
views-appwrite and referenced by pinned URL, never copied — copies were the
platform's original failure (þing-01 sáttmál S6):

https://github.com/views-platform/views-appwrite/blob/20dfd0f/docs/ADRs/platform/coordinate_registry.toml
https://github.com/views-platform/views-appwrite/blob/90fc105/docs/ADRs/platform/coordinate_registry.toml

That pin is registry **v1.4.0** — declared below as
That pin is registry **v1.4.1** — declared below as
``SEAM_CONTRACT_VERSION`` / ``SEAM_CONTRACT_COMMIT`` so the pin is a value a test can
check rather than a fact buried in prose. A pinned URL does not rot, but it does go
stale, and nothing in this repository could previously tell you it had (register C-57).
Expand Down Expand Up @@ -44,8 +44,8 @@
#: Bumping these is not bookkeeping: it asserts that someone re-checked this module's
#: declaration against that edition of the registry. ``tests/test_env_declaration.py``
#: enforces the pair against a local views-appwrite checkout when one is present.
SEAM_CONTRACT_VERSION = "1.4.0"
SEAM_CONTRACT_COMMIT = "20dfd0f"
SEAM_CONTRACT_VERSION = "1.4.1"
SEAM_CONTRACT_COMMIT = "90fc105"

CONNECTION_ENV = (
"APPWRITE_ENDPOINT",
Expand Down
Loading