Repository navigation
chore(arrival-pack): take the template's generated Proofs guidance #36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -20,6 +20,11 @@ let data = import "claude-md-data.json" in | |
| # owner's voice. Until then the estate-common block is explicitly DRAFT. | ||
| let manifesto_pin = "DRAFT-unratified" in | ||
|
|
||
| let anchor_override = | ||
| if std.array.length data.anchor_forbidden == 0 then "" | ||
| else "\n- **Anchor override** (ANCHOR) — This repo's anchor forbids: %{std.string.join ", " data.anchor_forbidden}. The anchor overrides the estate policy above." | ||
| in | ||
|
|
||
| let provenance = "DEED@%{data.h_deed} ANCHOR@%{data.h_anchor}" | ||
| in | ||
|
|
||
|
|
@@ -57,7 +62,7 @@ The descriptive family (working name *descriptiles*) describes what-is; the **co | |
|
|
||
| | File | Answers | | ||
| |---|---| | ||
| | `%{data.deed}` | **CHORA**, the repo deed. Its `(identity)` `(clade)` `(lineage)` clauses say what this repo IS (registers into `gv-clade-index`); `(meta)` the architecture axes; `(agentic)` *may I act now?*; `(ecosystem)` where it sits and what it is not; `(status)` and `(maturity)` where it is now. Read fields with `scripts/deed-field.sh`. | | ||
| | `%{data.deed}` | **CHORA**, the repo deed. Its header `:repo-uuid` is the repo's one id, and `(identity)` and `(lineage)` say what this repo IS; a `(clade)` clause, when present, records the repo's clade placements: identity facts about where it sits, never its id and never an edict. chora-registry (formerly `gv-clade-index`) is authoritative for them; this repo's validation checks only that a declared clade is one of the 12 shelves; `(meta)` the architecture axes; `(agentic)` *may I act now?*; `(ecosystem)` where it sits and what it is not; `(status)` and `(maturity)` where it is now. Read fields with `scripts/deed-field.sh`. | | ||
| | `(anchor)` | *Semantic authority + golden path* — what downstream may extend-not-redefine; if a recognised-drift / re-anchor marker is present, it **supersedes** accumulated context — read it first. | | ||
| | `(neurosym)` | *Meaning* of operations — proof obligations. | | ||
| | `(playbook)` | *How* permitted actions run. | | ||
|
|
@@ -66,7 +71,15 @@ The descriptive family (working name *descriptiles*) describes what-is; the **co | |
| | k9 | *Validation*. Kennel (data) / Yard (pure eval) / Hunt (guarded exec). | | ||
|
|
||
| ## Canon pointers | ||
| - `hyperpolymath/standards` — the canon source. · `hyperpolymath/gv-clade-index` — the estate map (identity registry). · `hyperpolymath/manifesto` — this doctrine. | ||
| Estate data-format route: **kyq** handles exactly **TOML, Dhall, KYAML, | ||
| I-JSON/JCS**. Preserve TOML/Dhall; migrate YAML/YML to KYAML and JSON variants | ||
| through kyq using **hyperpolymath/ijson-jcs**, the actual estate implementation | ||
| repository. **kyX** owns wider projection. DEED/K9/coordination keep their own | ||
| grammars. Canon: `metadatastician/standards/3-practice/DATA-FORMAT-ROUTING.adoc`. | ||
| Planned support is not operational evidence: retain explicit transitional | ||
| checks until a pinned kyq executable passes positive and negative tests. | ||
|
|
||
| - `hyperpolymath/standards` — the canon source. · `hyperpolymath/gv-clade-index` (being renamed chora-registry) — the estate registry of repo identities and classification schemes. · `hyperpolymath/manifesto` — this doctrine. | ||
| - **Before you invent, rename, or consolidate anything: STOP and check the map + IS-NOT.** | ||
|
|
||
| ## Estate language policy (overridable per-repo via AGENTIC) | ||
|
|
@@ -77,16 +90,55 @@ Use plain JavaScript when this tooling is needed. TypeScript and ReScript migrat | |
| ## Asking the owner | ||
| Put every question that needs the owner's decision through the selector (the AskUserQuestion tool), not as prose at the end of a report. Batch up to four per call, offer concrete options with the recommended one first, and say what each option would cause. | ||
|
|
||
| ## Proofs — which prover for which obligation | ||
|
|
||
| Normative source: `3-practice/PROOF-POLICY.adoc` in `hyperpolymath/standards`. | ||
| Read it there; `verification/proofs/README.adoc` maps it onto this repo. | ||
|
|
||
| | Code or obligation | Verifier | | ||
| |---|---| | ||
| | Rust code | **Creusot** with **Pearlite** contracts, and **Verus**, by default and on the code (§1.2). Kani for `unsafe`/FFI seams and Aeneas for Rust that implements an Agda theorem run alongside, never instead | | ||
| | Ada code | **SPARK** | | ||
| | APIs, ABIs, engineering properties | **Idris2** | | ||
| | Theory | **Agda**, rechecked in **Rocq** and **Lean** (no Mathlib) | | ||
|
|
||
| Always name Creusot, Pearlite and Verus in Rust verification plans and in | ||
| `docs/status/PROOF-STATUS.adoc`. Pearlite is Creusot's specification | ||
| language, not a third verifier. Plan scopes for both verifiers, and record | ||
| any that is unsupported, inapplicable or not yet run, with its reason; never | ||
| present an unexecuted check as a pass. Using both does not make two | ||
| independent witnesses (policy §1.2). | ||
|
|
||
| Third-party code (crates such as Bevy, libraries, forks) is **not** converted | ||
| or re-proved. Where a proof relies on a dependency the prover does not check, | ||
| state the reliance as an `ASSUMED` boundary specification. Where the | ||
| dependency's whole import cone compiles under the prover's safe mode with zero | ||
| postulates, it is *checked, not assumed*: record the cone (root module, flags, | ||
| postulate count of zero, library name, version and pin) instead of an | ||
| `ASSUMED` row (policy §1.1). A cone with a postulate, or compiled outside safe | ||
|
Comment on lines
+115
to
+118
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
When a dependency's import cone passes the new safe-mode/zero-postulate rule, this generated guidance tells agents to record it as checked rather than Useful? React with 👍 / 👎. |
||
| mode, is not checked. When choosing between dependencies that fit equally | ||
| well, prefer one that carries its own verification. A preference, not a gate. | ||
|
|
||
| Proof Witness Grades are policy §8. They apply to *theory* theorems only: Agda | ||
| source, rechecked in Rocq and Lean (§8.1). Engineering proofs (Creusot, Verus, | ||
| SPARK, Idris2) are not graded on this ladder; they use the §5 tokens only. For | ||
| a theory theorem, `PWG-3` < `PWG-2i` < `PWG-2ii` < `PWG-1`, where `PWG-1` is | ||
| strongest. A theorem that does not reach `PWG-3` is `ungraded`, with no | ||
| qualifier. A grade is derived from receipts, never asserted. A "verified" or | ||
| "machine-checked" claim needs current receipts. Report a census with its | ||
| denominator, never a percentage. Always write the `PWG-` prefix: CRG, TRG, ARG | ||
| and FRG letters, and ECHIDNA's `TrustLevel`, are different schemes. | ||
|
|
||
| --- | ||
|
|
||
| # This repo: `%{data.canonical_name}` · clade `%{data.prefixed_name}` | ||
| # This repo: `%{data.canonical_name}` | ||
|
|
||
| - **Identity** — uuid `%{data.uuid}`; clade `%{data.clade_primary}` (secondary `%{data.clade_secondary}`); born %{data.born}; forge `%{data.forge_gh}`. | ||
| - **Identity** — chora id `%{data.uuid}`; clade: %{data.clade_aid}; born %{data.born}; forge `%{data.forge_gh}`. | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
For this repository, Useful? React with 👍 / 👎. |
||
| - **IS** — %{data.purpose} | ||
| - **IS-NOT** — %{data.isnot} | ||
| - **Where it sits** — pipeline position **%{data.pipeline_pos}**; chain `%{data.chain}`; coordination = `%{data.coordination}`. | ||
| - **Constraints here** (AGENTIC) — fail-closed; evidence-per-step; no-silent-skip; rerun-after-fix; release-claim-requires-hard-pass. Never: banned langs (above), secrets, state files in repo root, AGPL. Details: the deed's `(bot-directives (methodology) (coverage) (debt))` clauses. | ||
| - **Golden path** (ANCHOR) — `%{data.golden_smoke}` → %{data.golden_crit}. | ||
| - **Golden path** (ANCHOR) — `%{data.golden_smoke}` → %{data.golden_crit}.%{anchor_override} | ||
| - **State** — phase %{data.phase}; maturity %{data.maturity}. Milestones and next actions: `docs/status/ROADMAP.adoc`. | ||
|
|
||
| <!-- ARRIVAL-PACK:END · provenance: %{provenance} · Manifesto@%{manifesto_pin} · regenerate: `just claude-md` (k9 drift-detects; do not hand-edit above) --> | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When an anchor explicitly allows a language denied by the estate policy—or supplies only an
allowedlist—this condition emits no corresponding override, even thoughextract.shreadsanchor_allowed. The generated guidance therefore continues telling agents that the language is forbidden, contradicting the repo-specific anchor; include allowed entries in the override and emit it when either list is nonempty.Useful? React with 👍 / 👎.