nicweyand/argand-site-registry
1
0
Fork 0
Code Issues Pull requests Projects Releases 7 Packages Wiki Activity Actions

docs: record Argand registry cutover
All checks were successful
Standalone registry checks / check (push) Successful in 4m46s
Details

Browse source
This commit is contained in:
Nic Weyand 2026-09-13 02:54:50 -04:00
commit 1f92e7aa14
Signed by: nicweyand
SSH key fingerprint: SHA256:2te+ycJIQON/Wo/dH6+ZkFSQ4HnHWpetV2azx9E65dQ
2 changed files with 13 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

6
README.md
View file

@ -82,7 +82,7 @@ automatic destination: use the native `resolve` result and your application's
own admission policy. A null destination is a meaningful abstention. own admission policy. A null destination is a meaningful abstention.
The [consumer contract](docs/CONSUMERS.md) covers Rust dependencies, CLI JSON, The [consumer contract](docs/CONSUMERS.md) covers Rust dependencies, CLI JSON,
SQLite/JSONL distribution, compatibility and Argand's eventual upstream cutover. SQLite/JSONL distribution, compatibility and Argand's pinned upstream integration.
Exact entity, URL/domain, source-separated popularity and redacted Curlie category Exact entity, URL/domain, source-separated popularity and redacted Curlie category
queries support audit tools. `resolve` also reports a stable abstention reason and queries support audit tools. `resolve` also reports a stable abstention reason and
decision counts. The bounded `evaluate` command replays JSONL judgments and reports decision counts. The bounded `evaluate` command replays JSONL judgments and reports
@ -123,6 +123,6 @@ The code remains **AGPL-3.0-or-later**; the complete license is in [LICENSE](LIC
Original attribution is retained. [UPSTREAM.json](UPSTREAM.json) records the signed Original attribution is retained. [UPSTREAM.json](UPSTREAM.json) records the signed
Argand extraction revision and original file hashes. Version 0.3 advances the Argand extraction revision and original file hashes. Version 0.3 advances the
standalone database to schema version 3; the migration and consumer rules are standalone database to schema version 3; the migration and consumer rules are
documented in [CONSUMERS.md](docs/CONSUMERS.md). Argand still uses its embedded copy; documented in [CONSUMERS.md](docs/CONSUMERS.md). Argand pins this signed `v0.3.0`
its switch to a pinned upstream release is a coordinated downstream change. This release by full Git revision and no longer carries an embedded source copy. This
repository does not operate a public approved-link dataset. repository does not operate a public approved-link dataset.

19
docs/CONSUMERS.md
View file

@ -49,16 +49,17 @@ receipts. Unsupported contracts fail closed. Pin source releases,
compile consumers and replay fixed fixtures before upgrades. Preserve import and compile consumers and replay fixed fixtures before upgrades. Preserve import and
review history; never mutate complete generations to migrate them. review history; never mutate complete generations to migrate them.
## Argand transition ## Argand integration
UPSTREAM.json pins the exact Argand source baseline, including the beta agent's UPSTREAM.json pins the exact Argand source baseline, including the beta agent's
selection-context API. The first standalone extraction preserves runtime Rust and selection-context API. The first standalone extraction preserves runtime Rust and
migration bytes. Argand currently consumes its embedded workspace crate; this migration bytes. Argand main commit
package does not silently redirect that dependency. `d9dfd1585ce21d9c4136bcc24fa01fe3bfb8ed6e` replaced its embedded workspace
crate with this signed `v0.3.0` release at full Git revision
`ac8282093d8a815c6227cff86e1f40714d510bcd`.
At cutover, coordinate with the Argand source/build owner, compare both trees with Develop the library here and update Argand through explicit reviewed revision-pin
the recorded baseline, carry any subsequent fixes forward, replace the embedded changes. Each update must compare the old and new contracts and rerun Argand's
dependency with a reviewed standalone revision, and run Argand's complete engine navigation compiler and API gates. Preserve existing registry receipts and public
and navigation-compiler gates. Preserve existing registry receipts and public navigation admission; a source dependency change does not activate a registry
navigation admission. After cutover, develop the library upstream and update generation or approve a destination.
Argand through explicit pinned dependency changes, avoiding permanent dual copies.