Skip to content

docs(epistemic): Epistemic Audit Amendment v1.1 + MUSTALAH pilot (recorded as DRAFT) - #226

Open
Deleted user (ghost) wants to merge 3 commits into
mainfrom
claude/aegis-epistemic-audit-amendment-ai8be8
Open

docs(epistemic): Epistemic Audit Amendment v1.1 + MUSTALAH pilot (recorded as DRAFT)#226
Deleted user (ghost) wants to merge 3 commits into
mainfrom
claude/aegis-epistemic-audit-amendment-ai8be8

Conversation

@ghost

@ghost ghost commented Jul 20, 2026

Copy link
Copy Markdown

Summary

Persists the AEGIS Epistemic Audit Amendment v1.1 and the MUSTALAH-ANANA-REPLAY-001 pilot preregistration as repo artifacts. No such architecture existed anywhere in the tree before this PR.

The frozen conceptual constitution (§1–5) records:

  • §1 observable-indexed faithfulness — certification unit is (arrow, observable), not the arrow alone
  • §2 directional Blackwell–Dubins non-merging (P ≪ Q, P-a.s.), symmetric only under P ∼ Q; dogmatic-zero diagnostic; Aumann as a shared-prior boundary, not a universal test
  • §3 selector-laden challenge protocols (S(x,T;λ,R,C)) — the selector burden stays visible
  • §4 audit-data endogeneity D_G = G(H), guard-differentiated (not statistically independent) channels, symmetric valence vectors
  • §5 termination obligation + co-tuning null: ΔCoh > 0 ⇏ ΔEvidence > 0

The pilot is recorded as PILOT_SPEC_DRAFT_RECORDED, not PILOT_SPEC_FROZEN. §8 rule text/classical_source/source_locator and §9 file_sha256/record_count for both critic editions (Ibn Maʿīn, Ibn Ḥanbal) are null because no edition is present on disk. Per the §18 admission gates and this repo's CLAIMS_LEDGER.md fabrication discipline (CLM-301…310), those hashes are not invented. spec_hash and payload_hash are real SHA-256 digests of the committed bytes and reproduce with sha256sum.

Freeze is one operator hand-off away: supply the two source editions as files → CORPUS_SNAPSHOT_RECORDED (real hashes) → PILOT_SPEC_FROZEN.

Stratum

  • Stratum I — Governance Runtime (sovereign-omega-v2 / aegis-cl-psi)
  • Stratum II — Interface (cockpit / studio)
  • Stratum III — Commercial (hub / products)
  • Cross-cutting (packages / .github / docs)

Gate results

Docs-only change — no runtime code touched; product/language gates are N/A.

Stratum I — TypeScript Gate 8 (run if sovereign-omega-v2 changed):

N/A — no sovereign-omega-v2 source changed

Stratum I — Rust (run if aegis-cl-psi changed):

N/A — no Rust changed

Stratum II–III — Product builds (run if applicable):

N/A — no product code changed

Constitutional files (run if any frozen file was touched):

N/A — no frozen file touched

Artifact integrity self-check (this PR):

sha256sum docs/EPISTEMIC_AUDIT_AMENDMENT.md
  -> 0452f3cce56de157d3f640eabe023e82329167a4b4de6acdf3f185a96288f44c  (== embedded spec_hash)
sha256sum docs/preregistrations/MUSTALAH-ANANA-REPLAY-001.spec.json
  -> 9ab8e1557523ffe968cd3fec684f3883a2e1ea2ab357425b63437b2e986d7515  (== embedded payload_hash)
both JSON artifacts parse

Invariants checklist

  • No Date.now() outside src/event/uuid.ts — N/A (docs only)
  • No Set/Map in ProjectionState — N/A
  • No JSON.stringify for integrity hashing — hashes are sha256sum of file bytes, reproducible
  • deepFreeze applied to all new state objects — N/A
  • Version mismatch triggers hard abort — N/A
  • No T4/T5 claim grounds T0–T2 assertion without evidence review — amendment is graded T2 / Proposed / EQ-D; corpus hashes deliberately left null rather than fabricated
  • All Rust: BTreeMap not HashMap — N/A
  • New TS files: .js extension — N/A (no TS added)
  • Epistemic tier declared in module header — amendment header declares T2

Constitutional files

  • gate.py — not modified
  • dna.py — not modified
  • router.py — not modified

Test plan

  • Wrote docs/EPISTEMIC_AUDIT_AMENDMENT.md, then computed spec_hash = sha256sum of its bytes; embedded that exact digest in the spec and event JSON.
  • Computed payload_hash = sha256sum of the spec JSON; embedded in the event.
  • Derived event_id deterministically from event_type | pilot_id | GENESIS-parent | spec_hash | payload_hash (reproduce command recorded in the event file).
  • Re-ran both sha256sum checks against the committed files — byte-identical to the embedded values (see Gate results above).
  • Validated both JSON artifacts parse.
  • Registered all three paths in INDEX.md per the MYTHOS authority-graph rule.

🤖 Generated with Claude Code


Generated by Claude Code

Claude (claude) and others added 2 commits July 20, 2026 23:10
…LAH pilot as DRAFT

Persist the frozen methodological constitution (§1-5: observable-indexed
faithfulness, directional Blackwell-Dubins non-merging with the Aumann
shared-prior boundary, selector-laden challenge protocols, audit-data
endogeneity) and the MUSTALAH-ANANA-REPLAY-001 pilot preregistration
(§6-19) as repo artifacts.

The pilot is recorded as PILOT_SPEC_DRAFT_RECORDED, not PILOT_SPEC_FROZEN:
§8 rule text/source and §9 corpus file_sha256/record_count for both critic
editions remain null because no edition is present on disk. Per §18
admission gates and the CLAIMS_LEDGER fabrication discipline, these hashes
are not invented. spec_hash and payload_hash are real SHA-256 digests of
the committed bytes and reproduce with sha256sum.

- docs/EPISTEMIC_AUDIT_AMENDMENT.md          frozen text (T2), spec_hash source
- docs/preregistrations/*.spec.json          machine spec, pending blocks null
- docs/preregistrations/events/*.json        recorded draft event, real digests
- INDEX.md                                    register the three paths

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FgtZWHMkrTYKVrHDrqQmvc
@vercel

vercel Bot commented Jul 20, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
hook-generator Ready Ready Preview, Comment Jul 20, 2026 11:23pm
hub Ready Ready Preview, Comment Jul 20, 2026 11:23pm
platform-picker Ready Ready Preview, Comment Jul 20, 2026 11:23pm

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
aegisomega 2e0bf94 Commit Preview URL

Branch Preview URL
Jul 20 2026, 11:22 PM

…dment

The experiment-admission gate requires exactly one changed
.aegis/experiments/*.json plan per PR; PR #226 was missing it (DENIED:
found 0). This binds the docs-only amendment as an EXPERIMENT plan:
policy -> docs/EPISTEMIC_AUDIT_AMENDMENT.md, zero-mutation/zero-cost
budget, T2 tier. All derived hashes (claims_ledger.root,
expected_parent_state_root, operator_approval.approval_record_hash) were
computed with the repo's own admission functions, not by hand.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FgtZWHMkrTYKVrHDrqQmvc
@qodo-code-review

Copy link
Copy Markdown

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

ghost pushed a commit that referenced this pull request Jul 27, 2026
Six artifacts that exist (or are believed to) on the operator's machine and
nowhere this session can reach. I verified their absence from the repository;
I could not verify their presence anywhere else. Dispatch has PC filesystem
access, so the recovery is addressed to it.

Highest value is the holon-gram compiler: an 8-file, +4446/-889 change a Codex
session reported and explicitly held rather than committed. Searched 342
commits across 42 remote branches and every tree in history — zero matches. It
exists in one working tree on a container that gets reclaimed. Flagged the
holonogram/holonngram spelling split so the repo does not inherit two compilers.

Also records the PR inventory: 17 open, 16 blocked on the same class — no
admitted experiment plan. #233 verified directly (4 red gates, everything else
green); the rest listed as unverified rather than assumed. #226 flagged as
possibly superseded by the now-admitted #229.

Includes the admission recipe learned today, including the two failures that
are invisible until you hit them: the schema sets additionalProperties:false on
operator_approval so a _comment there is its own denial, and the approval hash
must come from computeApprovalRecordHashV01 because the validator recomputes
and compares.

Authority boundary written in explicitly: state=APPROVED only on explicit
operator instruction for that specific plan. Absence of instruction is not
permission. Also: do not redeem or transcribe anything financial, do not resume
the paused Supabase project, do not cite MCB-001 before a results file exists.

Tier: T2 — operational handoff, no claim promoted.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Dw3SqfhmZZdiZ881Wdjb1n
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant