From 300efeddf87f2744e439b4b54be0be1358a587ef Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 27 Oct 2026 08:11:54 +0000 Subject: [PATCH 1/8] docs(affirmation): fill the template; Zig and the gate NOT RUN here, CI attests MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit What was wrong: AFFIRMATION.adoc was the unfilled estate template. What changed: the template instructions are deleted; the claims table has the two executable claims (zig build test; the invoke-slice gate) marked NOT RUN here with the exact command, the reason, and the CI workflow that runs them on every push (vocarium-ci.yml, mlugg/setup-zig pinned to 0.16.0); the store format / wire-boundary claim is marked affirmed-by-reading; "What we do NOT claim" names evoke/convoke/transvoke/provoke/revoke, the M2 adapter, Haec ingestion, neighbours, and that nothing of voc was executed in the session. The gate's own checker pin 69221ad6 is recorded (bypassed when TROPECHECK_BIN is set; bump tracked as an issue, not changed here). What I ran: nothing of voc. The session could not run Zig 0.16.0: ziglang.org and every community mirror were unreachable through the proxy; a checksummed conda-forge 0.16.0 binary was fetched but its execution was refused by the session's permission classifier. What I did not run: zig build test; tests/e2e/invoke_slice.sh — the CI run on this branch is cited in the pull request. Co-Authored-By: Claude Fable 5.1 Claude-Session: https://claude.ai/code/session_01J4QvDh3p24SCUjyM9HHT31 --- AFFIRMATION.adoc | 119 ++++++++++++++++++++++------------------------- 1 file changed, 55 insertions(+), 64 deletions(-) diff --git a/AFFIRMATION.adoc b/AFFIRMATION.adoc index 3a840b4..f905771 100644 --- a/AFFIRMATION.adoc +++ b/AFFIRMATION.adoc @@ -1,94 +1,85 @@ // SPDX-License-Identifier: CC-BY-SA-4.0 // SPDX-FileCopyrightText: 2026 Jonathan D.A. Jewell -= AFFIRMATION — {{PROJECT_NAME}}, as of += AFFIRMATION — Vocarium, as of 2026-10-27 :toc: macro :toclevels: 2 _the No-Bullshit file: what we affirm was true and checkable at this moment._ -[NOTE] -==== -*This file is a template.* Replace the `{{…}}` placeholders and the `<…>` anchor -fields, then re-run your project's own checks in the same session before signing. - -An *affirmation* is a solemn declaration of the truth of a statement, made by -someone who _declines to swear an oath_ — our truth-as-best-believed at a stamped -instant, binding on our honesty, not a claim of infallibility. It is the third of -the README / EXPLAINME / AFFIRMATION trio: - -[cols="1,3,2",options="header"] -|=== -| File | Answers | Tense -| `README.adoc` | _Where is this going, and why?_ — steering, intent, vision | future / aspirational -| `EXPLAINME.adoc` | _How is it built, and what's the evidence?_ — engineering | descriptive / mechanism -| *`AFFIRMATION.adoc`* (this file) | _What can we honestly affirm was *true and checkable* at a stamped moment?_ | a frozen instant, falsifiable -|=== -==== - toc::[] == What this is, and how it works -*What it is.* A short, dated, signed snapshot of what {{OWNER}} can honestly and -verifiably claim about *{{PROJECT_NAME}}* at one exact commit. Nothing here is -marketing and nothing is a promise about the future — those live in the README. -This file is the receipt. - -*How it stays trustworthy.* Three moving parts: - -. *Ground truth, not memory.* Every claim below must be produced by _running the - project's own checks_ in the session that writes this file (build, tests, - typecheck, `just audit`). Where a status doc, the `Justfile`, or memory says - otherwise, the live run wins and the contradiction is flagged here. -. *A frozen anchor.* The file names the exact commit SHA, branch, UTC timestamp, - and toolchain (see <>), so "true" always means "true _at - this point_". Move the SHA and this file is a draft until it is re-run. -. *A real signature.* It is landed by a *signed git commit*; that signature over - this content at the anchored SHA is what makes the affirmation tamper-evident - and attributable — not the prose alone. - -*We are fallible.* This is our best honest belief, not a proof of its own -correctness. Treat it as a falsifiable claim, not gospel. - -== The epistemic contract (read this before you trust _or_ attack) +A short, dated, signed snapshot of what hyperpolymath can honestly and verifiably +claim about *Vocarium* at one exact commit. Nothing here is marketing or a +promise; those live in the README. Every claim is tied to a command, and where a +command could not be run in the session that wrote this file it says so and names +the run that attests it instead. The anchor (<>) fixes commit, +time and toolchain. It is landed by a signed commit. -This document records {{OWNER}}'s *best belief* at the timestamp below. It is -*not a guarantee of correctness.* The only guarantee is *no intentional -overclaim*: where something is proven we say "proven"; where it is a documented -trust boundary, an experiment, or an unwired module, we say so; where a claim is -the README's aspiration rather than a checked result, we say so. An honest claim -that later turns out false is an *error to be fixed* — not a lie. +== The epistemic contract -*Standing invitation to refute.* You are invited to bulldoze any claim in this -file. Bring a counter-example, a failing run, or a contradicting source. +Best belief at the timestamp below, not a guarantee of correctness; the only +guarantee is no intentional overclaim. Refute any line with a counter-example, a +failing run, or a contradicting source. -== What we affirm (fill in — delete the examples) +== What we affirm [cols="2,1,3",options="header"] |=== -| Claim | Status | Evidence (command / `file:line`) -| _e.g. The library builds clean_ | affirmed | `just build` at the anchor SHA -| _e.g. The ABI seam typechecks_ | affirmed | `idris2 --typecheck abi.ipkg` -| _e.g. Feature X is complete_ | aspiration | README §… (not yet checked) +| Claim | Status | Evidence (command / file) + +| The store engine `voc` (pure Zig, no C; ADR-0002) builds and its unit tests +pass under the pinned Zig 0.16.0. +| NOT RUN here — attested by CI +| `zig build test` (Zig 0.16.0, `.tool-versions`). The session that wrote this +file could not run Zig: ziglang.org and its mirrors were unreachable and a +checksummed conda-forge 0.16.0 binary was obtained but not permitted to execute. +CI runs it on every push: `.github/workflows/vocarium-ci.yml` (mlugg/setup-zig +pinned to 0.16.0). The run on this branch is cited in the Phase 0 pull request. + +| The M1 invoke slice holds end to end: the canonical fixture ingests; the same +stored trope yields opposite tropecheck verdicts under two use-models +(`casual-note` → `p-sufficient`, `critical-paraphrase` → `p-insufficient` with +the witness edge named); an unwarranted edge is refused at the store door. +| NOT RUN here — attested by CI +| `TROPECHECK_BIN= bash tests/e2e/invoke_slice.sh` → expected +`GATE PASS: invoke slice proven (use-relativity + warrant door + unit tests)`. +Same CI workflow (`./tests/e2e/invoke_slice.sh`), which hard-fails on toolchain +absence or skew. Note: without `TROPECHECK_BIN` the script builds the checker at +its own pin `69221ad6`; with it set, the pin is bypassed. The pin predates the +spec v0.2 consolidation and is to be bumped once Phase 0 lands upstream (issue +filed, not changed here). + +| The store format is append-only JSONL (`{"t":"trope"|"edge"|"use_model"|"warrant"}`) +replayed into in-memory indexes; the only external contract is Trope IR v0.2 over +process I/O, verified by `tropecheck`. +| affirmed (by reading) +| `src/store/`, `docs/decisions/0002-pure-zig-wire-boundary.adoc`; the schema +at `trope-checker/schemas/trope-ir.schema.json` is the trust boundary. |=== == What we do NOT claim -* List the known gaps, trust boundaries, postulates, unwired modules, and stale - docs here. Silence is not affirmation — name what you have *not* verified. +* `evoke`, `convoke`, `transvoke`, `provoke`, `revoke` — not implemented. +* The M2 Hermeneia `StoreProvider` adapter — not implemented (wire, do not link). +* Haec ingestion — not implemented. +* `neighbours` / nearestness — `unsupported` by design; the retention order and the + cross-kind algebra live in trope-checker and are never reimplemented here. +* Nothing about `voc` was executed in the session that wrote this file; the two + NOT RUN rows above are exactly that. [#verifiable-anchor] == Verifiable anchor [cols="1,3"] |=== -| Project | {{PROJECT_NAME}} -| Repository | https://{{FORGE}}/{{OWNER}}/{{REPO}} -| Commit (SHA) | -| Branch | {{MAIN_BRANCH}} -| Timestamp (UTC) | -| Toolchain | -| Affirmed by | {{AUTHOR}} <{{AUTHOR_EMAIL}}> +| Project | Vocarium +| Repository | https://github.com/hyperpolymath/vocarium +| Commit (SHA) | 57944e6ad15067a29456096654e4f7dee44dc816 (`main` at the time; this file lands on the Phase 0 branch) +| Timestamp (UTC) | 2026-10-27 +| Toolchain | pinned: Zig 0.16.0 (`.tool-versions`); checker for the gate: `tropecheck-rs` from trope-checker (script pin `69221ad6`; the session's binary was built from 44020f9). Zig was not executed in this session (see above). +| Affirmed by | Jonathan D.A. Jewell (owner signs on landing; written by the Phase 0 agent) |=== _Landed by a signed git commit. Verify with `git log --show-signature` that the From 71c43744ca5304cc7c228c5d8273ef92be789a4e Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 27 Oct 2026 08:11:54 +0000 Subject: [PATCH 2/8] docs(readme): add the five-repo map paragraph What was wrong: the README had the ecology list but not the five-repo map with the dependency facts (HC-1; ADR-0002 wire-not-link). What changed: a "## Where this repo sits" section with the paragraph verbatim, placed before "Relationship to other systems". What I ran: n/a (prose only). What I did not run: n/a. Co-Authored-By: Claude Fable 5.1 Claude-Session: https://claude.ai/code/session_01J4QvDh3p24SCUjyM9HHT31 --- README.adoc | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.adoc b/README.adoc index 883ef84..aad9920 100644 --- a/README.adoc +++ b/README.adoc @@ -161,6 +161,10 @@ Vocarium makes that difference queryable. Vocarium is an experimental database architecture for trope-aware, loss-aware, warrant-aware data. It is intended to support research into particularity-preserving computation, interpretive query languages, AI-assisted reasoning, evidential databases, and transformation-aware knowledge systems. +## Where this repo sits + +Vocabulary track: trope-particularity-workbench → haec → trope-checker (verdict). Store/query track: haec → vocarium → hermeneia → trope-checker (verdict). trope-checker depends on nothing (HC-1); the workbench depends on nothing; vocarium and hermeneia meet at the M2 StoreProvider adapter (vocarium ADR-0002: wire, do not link). + ## Relationship to other systems Vocarium is part of a wider language/database ecology: From ae80eec97ba2bf4b7fd194ed9e373b1926a1b98b Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 27 Oct 2026 08:23:15 +0000 Subject: [PATCH 3/8] docs(affirmation): cite the green CI gate run for the two NOT RUN rows MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit What was wrong: the two NOT RUN rows pointed at "the run on this branch" in the abstract. What changed: both rows now cite vocarium-ci.yml run 40472451463 (job "invoke-slice gate", success, 2026-10-27T08:17Z), which ran `zig build test` and tests/e2e/invoke_slice.sh under mlugg/setup-zig 0.16.0 on this branch's head. The rows stay NOT RUN here: the attestation is CI's, not this session's. What I ran: nothing locally (see above). What I did not run: zig build test; the gate — unchanged. Co-Authored-By: Claude Fable 5.1 Claude-Session: https://claude.ai/code/session_01J4QvDh3p24SCUjyM9HHT31 --- AFFIRMATION.adoc | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/AFFIRMATION.adoc b/AFFIRMATION.adoc index f905771..9467dd4 100644 --- a/AFFIRMATION.adoc +++ b/AFFIRMATION.adoc @@ -31,18 +31,19 @@ failing run, or a contradicting source. | The store engine `voc` (pure Zig, no C; ADR-0002) builds and its unit tests pass under the pinned Zig 0.16.0. -| NOT RUN here — attested by CI +| NOT RUN here — attested by CI run 40472451463 (success, 2026-10-27T08:17Z) | `zig build test` (Zig 0.16.0, `.tool-versions`). The session that wrote this file could not run Zig: ziglang.org and its mirrors were unreachable and a checksummed conda-forge 0.16.0 binary was obtained but not permitted to execute. CI runs it on every push: `.github/workflows/vocarium-ci.yml` (mlugg/setup-zig -pinned to 0.16.0). The run on this branch is cited in the Phase 0 pull request. +pinned to 0.16.0). On this branch: job "invoke-slice gate" of +https://github.com/hyperpolymath/vocarium/actions/runs/40472451463 — success. | The M1 invoke slice holds end to end: the canonical fixture ingests; the same stored trope yields opposite tropecheck verdicts under two use-models (`casual-note` → `p-sufficient`, `critical-paraphrase` → `p-insufficient` with the witness edge named); an unwarranted edge is refused at the store door. -| NOT RUN here — attested by CI +| NOT RUN here — attested by CI run 40472451463 (success, 2026-10-27T08:17Z) | `TROPECHECK_BIN= bash tests/e2e/invoke_slice.sh` → expected `GATE PASS: invoke slice proven (use-relativity + warrant door + unit tests)`. Same CI workflow (`./tests/e2e/invoke_slice.sh`), which hard-fails on toolchain From 30a0aea5573b45b9d8afc8d17bc62dc34e2f02bb Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 27 Oct 2026 08:34:33 +0000 Subject: [PATCH 4/8] docs(affirmation): table-safe record tags, exact CI anchor, real timestamp, pin drift noted MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit What was wrong (review findings on #42): the JSONL union used raw `|` inside a PSV table cell, splitting the row; the CI sentence said "on every push" (the workflow runs on pushes to main, pull requests and dispatch); the attestation rows named a run but not the tested commit or completion time; "Timestamp (UTC)" was a bare date; the footer asked readers to match the base SHA against the introducing commit; `` is not shell-safe; "pinned Zig 0.16.0" ignored that mise.toml says `zig = "latest"`. What changed: tags written as a list; trigger scope stated; run 40472451463 on commit 71c4374, success, 2026-10-27T08:17:46Z in both NOT RUN rows and the anchor; "Commit (SHA) tested" + "Landing commit" rows with a matching footer; `/path/to/tropecheck-rs` marked as a placeholder; the toolchain row records the mise.toml drift (issue filed) alongside the .tool-versions pin the gate enforces. What I ran: n/a (prose); the CI run cited is unchanged. What I did not run: zig build test; the gate — unchanged (NOT RUN here). Co-Authored-By: Claude Fable 5.1 Claude-Session: https://claude.ai/code/session_01J4QvDh3p24SCUjyM9HHT31 --- AFFIRMATION.adoc | 30 +++++++++++++++++------------- 1 file changed, 17 insertions(+), 13 deletions(-) diff --git a/AFFIRMATION.adoc b/AFFIRMATION.adoc index 9467dd4..d013228 100644 --- a/AFFIRMATION.adoc +++ b/AFFIRMATION.adoc @@ -1,6 +1,6 @@ // SPDX-License-Identifier: CC-BY-SA-4.0 // SPDX-FileCopyrightText: 2026 Jonathan D.A. Jewell -= AFFIRMATION — Vocarium, as of 2026-10-27 += AFFIRMATION — Vocarium, as of 2026-10-27T08:17Z :toc: macro :toclevels: 2 @@ -31,20 +31,22 @@ failing run, or a contradicting source. | The store engine `voc` (pure Zig, no C; ADR-0002) builds and its unit tests pass under the pinned Zig 0.16.0. -| NOT RUN here — attested by CI run 40472451463 (success, 2026-10-27T08:17Z) +| NOT RUN here — attested by CI run 40472451463 on commit 71c4374 (success, 2026-10-27T08:17:46Z) | `zig build test` (Zig 0.16.0, `.tool-versions`). The session that wrote this file could not run Zig: ziglang.org and its mirrors were unreachable and a checksummed conda-forge 0.16.0 binary was obtained but not permitted to execute. -CI runs it on every push: `.github/workflows/vocarium-ci.yml` (mlugg/setup-zig -pinned to 0.16.0). On this branch: job "invoke-slice gate" of -https://github.com/hyperpolymath/vocarium/actions/runs/40472451463 — success. +CI runs it on pushes to `main`, pull requests and manual dispatch: +`.github/workflows/vocarium-ci.yml` (mlugg/setup-zig pinned to 0.16.0). On this +branch, at commit 71c43744ca5304cc7c228c5d8273ef92be789a4e: job "invoke-slice gate" of +https://github.com/hyperpolymath/vocarium/actions/runs/40472451463 — success, +2026-10-27T08:17:46Z. | The M1 invoke slice holds end to end: the canonical fixture ingests; the same stored trope yields opposite tropecheck verdicts under two use-models (`casual-note` → `p-sufficient`, `critical-paraphrase` → `p-insufficient` with the witness edge named); an unwarranted edge is refused at the store door. -| NOT RUN here — attested by CI run 40472451463 (success, 2026-10-27T08:17Z) -| `TROPECHECK_BIN= bash tests/e2e/invoke_slice.sh` → expected +| NOT RUN here — attested by CI run 40472451463 on commit 71c4374 (success, 2026-10-27T08:17:46Z) +| `TROPECHECK_BIN=/path/to/tropecheck-rs bash tests/e2e/invoke_slice.sh` (placeholder path) → expected `GATE PASS: invoke slice proven (use-relativity + warrant door + unit tests)`. Same CI workflow (`./tests/e2e/invoke_slice.sh`), which hard-fails on toolchain absence or skew. Note: without `TROPECHECK_BIN` the script builds the checker at @@ -52,7 +54,7 @@ its own pin `69221ad6`; with it set, the pin is bypassed. The pin predates the spec v0.2 consolidation and is to be bumped once Phase 0 lands upstream (issue filed, not changed here). -| The store format is append-only JSONL (`{"t":"trope"|"edge"|"use_model"|"warrant"}`) +| The store format is append-only JSONL (one record per line, `"t"` one of `trope`, `edge`, `use_model`, `warrant`) replayed into in-memory indexes; the only external contract is Trope IR v0.2 over process I/O, verified by `tropecheck`. | affirmed (by reading) @@ -77,11 +79,13 @@ at `trope-checker/schemas/trope-ir.schema.json` is the trust boundary. |=== | Project | Vocarium | Repository | https://github.com/hyperpolymath/vocarium -| Commit (SHA) | 57944e6ad15067a29456096654e4f7dee44dc816 (`main` at the time; this file lands on the Phase 0 branch) -| Timestamp (UTC) | 2026-10-27 -| Toolchain | pinned: Zig 0.16.0 (`.tool-versions`); checker for the gate: `tropecheck-rs` from trope-checker (script pin `69221ad6`; the session's binary was built from 44020f9). Zig was not executed in this session (see above). +| Commit (SHA) tested | 57944e6ad15067a29456096654e4f7dee44dc816 (`main` at the time; the tree the CI gate ran on is this branch's 71c4374, whose only differences from it are this file and the README) +| Landing commit | the signed commit that introduces this file, identified with `git log --show-signature -- AFFIRMATION.adoc`; a file cannot record its own commit's SHA +| Timestamp (UTC) | 2026-10-27T08:17:46Z (completion of the cited CI gate job) +| Toolchain | Zig 0.16.0 pinned in `.tool-versions`, which the gate enforces; `mise.toml` still says `zig = "latest"` — a drift the gate would reject, to be reconciled (issue). Checker for the gate: `tropecheck-rs` from trope-checker (script pin `69221ad6`; the session's binary was built from 44020f9). Zig was not executed in this session (see above). | Affirmed by | Jonathan D.A. Jewell (owner signs on landing; written by the Phase 0 agent) |=== -_Landed by a signed git commit. Verify with `git log --show-signature` that the -anchor SHA above matches the commit that introduced this affirmation._ +_To be landed by a signed git commit. The "Commit (SHA) tested" row is the base the +checks ran on; verify the introducing commit and its signature with +`git log --show-signature -- AFFIRMATION.adoc`._ From bb84dbb1aa83a173215a66911f7f417c9dc92c60 Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 27 Oct 2026 08:48:09 +0000 Subject: [PATCH 5/8] docs(affirmation): anchor the tested commit to the CI head; signing is prospective Review round 2 (Codex) on PR #42: "Commit (SHA) tested" is now 71c4374, the commit the cited gate run actually ran on, with 57944e6 recorded separately as the affirmed `main` base; "is landed by a signed commit" becomes "is to be landed ... the owner signs on landing", true before and after landing. Co-Authored-By: Claude Fable 5.1 Claude-Session: https://claude.ai/code/session_01J4QvDh3p24SCUjyM9HHT31 --- AFFIRMATION.adoc | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/AFFIRMATION.adoc b/AFFIRMATION.adoc index d013228..005b321 100644 --- a/AFFIRMATION.adoc +++ b/AFFIRMATION.adoc @@ -15,7 +15,8 @@ claim about *Vocarium* at one exact commit. Nothing here is marketing or a promise; those live in the README. Every claim is tied to a command, and where a command could not be run in the session that wrote this file it says so and names the run that attests it instead. The anchor (<>) fixes commit, -time and toolchain. It is landed by a signed commit. +time and toolchain. It is to be landed by a signed commit — the owner signs on +landing. == The epistemic contract @@ -79,13 +80,14 @@ at `trope-checker/schemas/trope-ir.schema.json` is the trust boundary. |=== | Project | Vocarium | Repository | https://github.com/hyperpolymath/vocarium -| Commit (SHA) tested | 57944e6ad15067a29456096654e4f7dee44dc816 (`main` at the time; the tree the CI gate ran on is this branch's 71c4374, whose only differences from it are this file and the README) +| Commit (SHA) tested | 71c43744ca5304cc7c228c5d8273ef92be789a4e (this branch; the commit CI run 40472451463 ran on) +| Affirmed base | 57944e6ad15067a29456096654e4f7dee44dc816 (`main` at the time; differs from the tested commit only in this file and the README, so the gate result carries over to it) | Landing commit | the signed commit that introduces this file, identified with `git log --show-signature -- AFFIRMATION.adoc`; a file cannot record its own commit's SHA | Timestamp (UTC) | 2026-10-27T08:17:46Z (completion of the cited CI gate job) | Toolchain | Zig 0.16.0 pinned in `.tool-versions`, which the gate enforces; `mise.toml` still says `zig = "latest"` — a drift the gate would reject, to be reconciled (issue). Checker for the gate: `tropecheck-rs` from trope-checker (script pin `69221ad6`; the session's binary was built from 44020f9). Zig was not executed in this session (see above). | Affirmed by | Jonathan D.A. Jewell (owner signs on landing; written by the Phase 0 agent) |=== -_To be landed by a signed git commit. The "Commit (SHA) tested" row is the base the -checks ran on; verify the introducing commit and its signature with +_To be landed by a signed git commit. The "Commit (SHA) tested" row is the commit the +CI gate ran on and the "Affirmed base" row the `main` state it speaks for; verify the introducing commit and its signature with `git log --show-signature -- AFFIRMATION.adoc`._ From 5f220379ca09a5acdd087503733a2cf078685d09 Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 27 Oct 2026 08:53:28 +0000 Subject: [PATCH 6/8] docs(affirmation): name the landing commit precisely Same correction Codex made on hermeneia #76: AFFIRMATION.adoc predates this snapshot as a template, so "the commit that introduces this file" selected nothing useful. The anchor and footer now say the signed commit that lands the snapshot on main is found with `git log --first-parent --show-signature -1 main -- AFFIRMATION.adoc`. Co-Authored-By: Claude Fable 5.1 Claude-Session: https://claude.ai/code/session_01J4QvDh3p24SCUjyM9HHT31 --- AFFIRMATION.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/AFFIRMATION.adoc b/AFFIRMATION.adoc index 005b321..0a29d8a 100644 --- a/AFFIRMATION.adoc +++ b/AFFIRMATION.adoc @@ -82,12 +82,12 @@ at `trope-checker/schemas/trope-ir.schema.json` is the trust boundary. | Repository | https://github.com/hyperpolymath/vocarium | Commit (SHA) tested | 71c43744ca5304cc7c228c5d8273ef92be789a4e (this branch; the commit CI run 40472451463 ran on) | Affirmed base | 57944e6ad15067a29456096654e4f7dee44dc816 (`main` at the time; differs from the tested commit only in this file and the README, so the gate result carries over to it) -| Landing commit | the signed commit that introduces this file, identified with `git log --show-signature -- AFFIRMATION.adoc`; a file cannot record its own commit's SHA +| Landing commit | the signed commit that lands this snapshot on `main` (the file itself predates it as a template); after landing, `git log --first-parent --show-signature -1 main -- AFFIRMATION.adoc` selects it. A file cannot record its own commit's SHA | Timestamp (UTC) | 2026-10-27T08:17:46Z (completion of the cited CI gate job) | Toolchain | Zig 0.16.0 pinned in `.tool-versions`, which the gate enforces; `mise.toml` still says `zig = "latest"` — a drift the gate would reject, to be reconciled (issue). Checker for the gate: `tropecheck-rs` from trope-checker (script pin `69221ad6`; the session's binary was built from 44020f9). Zig was not executed in this session (see above). | Affirmed by | Jonathan D.A. Jewell (owner signs on landing; written by the Phase 0 agent) |=== _To be landed by a signed git commit. The "Commit (SHA) tested" row is the commit the -CI gate ran on and the "Affirmed base" row the `main` state it speaks for; verify the introducing commit and its signature with -`git log --show-signature -- AFFIRMATION.adoc`._ +CI gate ran on and the "Affirmed base" row the `main` state it speaks for; verify the landing commit and its signature with +`git log --first-parent --show-signature -1 main -- AFFIRMATION.adoc`._ From d245ec58e15ba58209b9acb18070344ce96e9e15 Mon Sep 17 00:00:00 2001 From: "coderabbitai[bot]" <136622811+coderabbitai[bot]@users.noreply.github.com> Date: Tue, 27 Oct 2026 11:23:30 +0000 Subject: [PATCH 7/8] refactor(metadata): rename 6a2 directory to descriptiles and update tooling and documentation references --- .github/GOVERNANCE.md | 2 +- .github/pull_request_template.md | 6 ++-- .machine_readable/0.1-AI-MANIFEST.a2ml | 16 +++++------ .machine_readable/ai/.clinerules | 2 +- .machine_readable/ai/.windsurfrules | 2 +- .machine_readable/ai/AI.a2ml | 4 +-- .machine_readable/ai/README.adoc | 6 ++-- .../arrival-pack/claude-md.k9.ncl | 10 +++---- .machine_readable/arrival-pack/extract.sh | 2 +- .machine_readable/arrival-pack/generate.sh | 2 +- .machine_readable/arrival-pack/verify.sh | 2 +- .machine_readable/coaptation/coapt.k9.ncl | 10 +++---- .machine_readable/coaptation/coapt.sh | 2 +- .machine_readable/coaptation/extract-facts.sh | 2 +- .../coaptation/receipts/latest.a2ml | 4 +-- .machine_readable/coaptation/verify.sh | 2 +- .machine_readable/coaptation/witness-map.ncl | 4 +-- .machine_readable/contractiles/Justfile | 8 +++--- .../contractiles/adjust/adjust.k9.ncl | 4 +-- .../contractiles/bust/bust.k9.ncl | 4 +-- .../contractiles/dust/dust.k9.ncl | 4 +-- .../contractiles/intend/intend.k9.ncl | 8 +++--- .../contractiles/must/Mustfile.a2ml | 8 +++--- .../contractiles/must/must.k9.ncl | 4 +-- .../contractiles/trust/trust.k9.ncl | 6 ++-- .../{6a2 => descriptiles}/0-AI-MANIFEST.a2ml | 4 +-- .../{6a2 => descriptiles}/AGENTIC.a2ml | 0 .../{6a2 => descriptiles}/CLADE.a2ml | 0 .../{6a2 => descriptiles}/ECOSYSTEM.a2ml | 0 .../{6a2 => descriptiles}/META.a2ml | 0 .../{6a2 => descriptiles}/NEUROSYM.a2ml | 0 .../{6a2 => descriptiles}/PLAYBOOK.a2ml | 4 +-- .../{6a2 => descriptiles}/README.adoc | 2 +- .../{6a2 => descriptiles}/STATE.a2ml | 0 .../anchors/0-AI-MANIFEST.a2ml | 0 .../{6a2 => descriptiles}/anchors/ANCHOR.a2ml | 0 .../{6a2 => descriptiles}/anchors/README.adoc | 0 .../policies/MAINTENANCE-AXES.a2ml | 2 +- .../policies/MAINTENANCE-CHECKLIST.a2ml | 2 +- .../self-validating/methodology-guard.k9.ncl | 2 +- .pre-commit-config.yaml | 2 +- Justfile | 8 +++--- build/just/assess.just | 12 ++++---- build/just/groove.just | 2 +- build/just/validate.just | 28 +++++++++---------- docs/RSR_OUTLINE.adoc | 2 +- docs/governance/CRG-AUDIT-TEMPLATE.adoc | 8 +++--- docs/practice/AI-CONVENTIONS.adoc | 12 ++++---- docs/status/READINESS.adoc | 6 ++-- .../canonical-directory-structure/README.adoc | 2 +- 50 files changed, 111 insertions(+), 111 deletions(-) rename .machine_readable/{6a2 => descriptiles}/0-AI-MANIFEST.a2ml (82%) rename .machine_readable/{6a2 => descriptiles}/AGENTIC.a2ml (100%) rename .machine_readable/{6a2 => descriptiles}/CLADE.a2ml (100%) rename .machine_readable/{6a2 => descriptiles}/ECOSYSTEM.a2ml (100%) rename .machine_readable/{6a2 => descriptiles}/META.a2ml (100%) rename .machine_readable/{6a2 => descriptiles}/NEUROSYM.a2ml (100%) rename .machine_readable/{6a2 => descriptiles}/PLAYBOOK.a2ml (97%) rename .machine_readable/{6a2 => descriptiles}/README.adoc (97%) rename .machine_readable/{6a2 => descriptiles}/STATE.a2ml (100%) rename .machine_readable/{6a2 => descriptiles}/anchors/0-AI-MANIFEST.a2ml (100%) rename .machine_readable/{6a2 => descriptiles}/anchors/ANCHOR.a2ml (100%) rename .machine_readable/{6a2 => descriptiles}/anchors/README.adoc (100%) diff --git a/.github/GOVERNANCE.md b/.github/GOVERNANCE.md index 14c9c55..4a7f376 100644 --- a/.github/GOVERNANCE.md +++ b/.github/GOVERNANCE.md @@ -46,7 +46,7 @@ release schedules, contributor access, and community standards. - ADR statuses: `proposed`, `accepted`, `deprecated`, `superseded`, `rejected`. - ADRs provide a historical record of why decisions were made and what alternatives were considered. -- See `.machine_readable/6a2/META.a2ml` for the machine-readable ADR index. +- See `.machine_readable/descriptiles/META.a2ml` for the machine-readable ADR index. --- diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md index c46a4e0..65789e9 100644 --- a/.github/pull_request_template.md +++ b/.github/pull_request_template.md @@ -29,9 +29,9 @@ Copyright (c) Jonathan D.A. Jewell ### As Applicable -- [ ] `.machine_readable/6a2/STATE.a2ml` updated (if project state changed) -- [ ] `.machine_readable/6a2/ECOSYSTEM.a2ml` updated (if integrations changed) -- [ ] `.machine_readable/6a2/META.a2ml` updated (if architectural decisions changed) +- [ ] `.machine_readable/descriptiles/STATE.a2ml` updated (if project state changed) +- [ ] `.machine_readable/descriptiles/ECOSYSTEM.a2ml` updated (if integrations changed) +- [ ] `.machine_readable/descriptiles/META.a2ml` updated (if architectural decisions changed) - [ ] Documentation updated for user-facing changes - [ ] `TOPOLOGY.md` updated (if architecture changed) - [ ] `CHANGELOG` or release notes updated diff --git a/.machine_readable/0.1-AI-MANIFEST.a2ml b/.machine_readable/0.1-AI-MANIFEST.a2ml index 7d8ce9e..a28ee37 100644 --- a/.machine_readable/0.1-AI-MANIFEST.a2ml +++ b/.machine_readable/0.1-AI-MANIFEST.a2ml @@ -12,14 +12,14 @@ description: | automation scripts. canonical_locations: - state: "6a2/STATE.a2ml" - meta: "6a2/META.a2ml" - ecosystem: "6a2/ECOSYSTEM.a2ml" - agentic: "6a2/AGENTIC.a2ml" - neurosym: "6a2/NEUROSYM.a2ml" - playbook: "6a2/PLAYBOOK.a2ml" - clade: "6a2/CLADE.a2ml" - anchors: "6a2/anchors/" + state: "descriptiles/STATE.a2ml" + meta: "descriptiles/META.a2ml" + ecosystem: "descriptiles/ECOSYSTEM.a2ml" + agentic: "descriptiles/AGENTIC.a2ml" + neurosym: "descriptiles/NEUROSYM.a2ml" + playbook: "descriptiles/PLAYBOOK.a2ml" + clade: "descriptiles/CLADE.a2ml" + anchors: "descriptiles/anchors/" policies: "policies/" ai_configs: "ai/" compliance: "compliance/" diff --git a/.machine_readable/ai/.clinerules b/.machine_readable/ai/.clinerules index 8f38042..30d21a5 100644 --- a/.machine_readable/ai/.clinerules +++ b/.machine_readable/ai/.clinerules @@ -2,7 +2,7 @@ # Copyright (c) {{CURRENT_YEAR}} {{AUTHOR}} ({{OWNER}}) <{{AUTHOR_EMAIL}}> # Authoritative source: docs/AI-CONVENTIONS.md -# STARTUP: Read 0-AI-MANIFEST.a2ml first, then .machine_readable/6a2/STATE.a2ml. +# STARTUP: Read 0-AI-MANIFEST.a2ml first, then .machine_readable/descriptiles/STATE.a2ml. # LICENSE # All original code: MPL-2.0. diff --git a/.machine_readable/ai/.windsurfrules b/.machine_readable/ai/.windsurfrules index 8f38042..30d21a5 100644 --- a/.machine_readable/ai/.windsurfrules +++ b/.machine_readable/ai/.windsurfrules @@ -2,7 +2,7 @@ # Copyright (c) {{CURRENT_YEAR}} {{AUTHOR}} ({{OWNER}}) <{{AUTHOR_EMAIL}}> # Authoritative source: docs/AI-CONVENTIONS.md -# STARTUP: Read 0-AI-MANIFEST.a2ml first, then .machine_readable/6a2/STATE.a2ml. +# STARTUP: Read 0-AI-MANIFEST.a2ml first, then .machine_readable/descriptiles/STATE.a2ml. # LICENSE # All original code: MPL-2.0. diff --git a/.machine_readable/ai/AI.a2ml b/.machine_readable/ai/AI.a2ml index 3754aca..ed3cd3c 100644 --- a/.machine_readable/ai/AI.a2ml +++ b/.machine_readable/ai/AI.a2ml @@ -7,8 +7,8 @@ - Prefer to keep generated files out of source control, and regenerate them with the documented commands before committing. ## Workflow -1. Inspect `.machine_readable/6a2/STATE.a2ml` for blockers and next actions. -2. Respect any constraints listed inside `.machine_readable/6a2/AGENTIC.a2ml` when tooling changes are requested. +1. Inspect `.machine_readable/descriptiles/STATE.a2ml` for blockers and next actions. +2. Respect any constraints listed inside `.machine_readable/descriptiles/AGENTIC.a2ml` when tooling changes are requested. 3. After finishing edits, update STATE with your outcomes and commit with a concise, imperative message. ## Delivery Promises diff --git a/.machine_readable/ai/README.adoc b/.machine_readable/ai/README.adoc index 29d3c06..a5dec59 100644 --- a/.machine_readable/ai/README.adoc +++ b/.machine_readable/ai/README.adoc @@ -16,9 +16,9 @@ Avoid scattering agent instruction files around the repo root. Recommended machine read order: -* `.machine_readable/6a2/anchors/ANCHOR.a2ml` +* `.machine_readable/descriptiles/anchors/ANCHOR.a2ml` * `.machine_readable/policies/MAINTENANCE-AXES.a2ml` * `.machine_readable/policies/MAINTENANCE-CHECKLIST.a2ml` * `.machine_readable/policies/SOFTWARE-DEVELOPMENT-APPROACH.a2ml` -* `.machine_readable/6a2/STATE.a2ml` -* `.machine_readable/6a2/META.a2ml` +* `.machine_readable/descriptiles/STATE.a2ml` +* `.machine_readable/descriptiles/META.a2ml` diff --git a/.machine_readable/arrival-pack/claude-md.k9.ncl b/.machine_readable/arrival-pack/claude-md.k9.ncl index 6367467..de971c5 100644 --- a/.machine_readable/arrival-pack/claude-md.k9.ncl +++ b/.machine_readable/arrival-pack/claude-md.k9.ncl @@ -34,11 +34,11 @@ # Inputs the projection reads (single source of truth). inputs = { descriptiles = [ - ".machine_readable/6a2/CLADE.a2ml", - ".machine_readable/6a2/ECOSYSTEM.a2ml", - ".machine_readable/6a2/AGENTIC.a2ml", - ".machine_readable/6a2/STATE.a2ml", - ".machine_readable/6a2/anchors/ANCHOR.a2ml", + ".machine_readable/descriptiles/CLADE.a2ml", + ".machine_readable/descriptiles/ECOSYSTEM.a2ml", + ".machine_readable/descriptiles/AGENTIC.a2ml", + ".machine_readable/descriptiles/STATE.a2ml", + ".machine_readable/descriptiles/anchors/ANCHOR.a2ml", ], estate_common = "hyperpolymath/manifesto@", # DRAFT-unratified today target = "CLAUDE.md", diff --git a/.machine_readable/arrival-pack/extract.sh b/.machine_readable/arrival-pack/extract.sh index b77a8d5..c0adf70 100755 --- a/.machine_readable/arrival-pack/extract.sh +++ b/.machine_readable/arrival-pack/extract.sh @@ -13,7 +13,7 @@ # Determinism (no timestamps) is required so the k9 drift check can byte-compare. set -euo pipefail -DIR6A2="${1:-.machine_readable/6a2}" +DIR6A2="${1:-.machine_readable/descriptiles}" CLADE="$DIR6A2/CLADE.a2ml" ECO="$DIR6A2/ECOSYSTEM.a2ml" AGENTIC="$DIR6A2/AGENTIC.a2ml" diff --git a/.machine_readable/arrival-pack/generate.sh b/.machine_readable/arrival-pack/generate.sh index 3caafa9..ac2a859 100755 --- a/.machine_readable/arrival-pack/generate.sh +++ b/.machine_readable/arrival-pack/generate.sh @@ -13,7 +13,7 @@ ROOT="$(git rev-parse --show-toplevel)" AP="$ROOT/.machine_readable/arrival-pack" TARGET="$ROOT/CLAUDE.md" -bash "$AP/extract.sh" "$ROOT/.machine_readable/6a2" > "$AP/claude-md-data.json" +bash "$AP/extract.sh" "$ROOT/.machine_readable/descriptiles" > "$AP/claude-md-data.json" nickel export --format raw "$AP/arrival-pack.ncl" > "$AP/.region.tmp" if [ -f "$TARGET" ] && grep -q 'ARRIVAL-PACK:BEGIN' "$TARGET"; then diff --git a/.machine_readable/arrival-pack/verify.sh b/.machine_readable/arrival-pack/verify.sh index 0763f00..1d90acf 100755 --- a/.machine_readable/arrival-pack/verify.sh +++ b/.machine_readable/arrival-pack/verify.sh @@ -13,7 +13,7 @@ TARGET="$ROOT/CLAUDE.md" [ -f "$TARGET" ] || { echo "DRIFT: CLAUDE.md missing — run \`just claude-md\`"; exit 1; } -bash "$AP/extract.sh" "$ROOT/.machine_readable/6a2" > "$AP/claude-md-data.json" +bash "$AP/extract.sh" "$ROOT/.machine_readable/descriptiles" > "$AP/claude-md-data.json" fresh="$(nickel export --format raw "$AP/arrival-pack.ncl")" committed="$(awk '/