Skip to content

Harden repo governance and add spec traceability - #3

Merged
mdheller merged 8 commits into
mainfrom
hardening/license-provenance-traceability
Jun 1, 2026
Merged

Harden repo governance and add spec traceability#3
mdheller merged 8 commits into
mainfrom
hardening/license-provenance-traceability

Conversation

@mdheller

Copy link
Copy Markdown
Member

Summary

This PR prepares HellGraph for disciplined private iteration and later public review.

It adds:

  • MIT license
  • provenance boundary and clean-room posture
  • notice file for upstream/third-party attribution discipline
  • positioning ADR clarifying HellGraph is not a direct Blazegraph fork or drop-in replacement
  • hardened README language
  • stronger CI with rustfmt, clippy, workspace tests, and docs-integrity checks
  • spec traceability audit
  • kernel seam audit

Architectural position

HellGraph is positioned as an alpha local-first graph runtime kernel with RDF/SPARQL bridge compatibility. Blazegraph remains a behavioral oracle and RDF/SPARQL compatibility reference, not the native kernel or product boundary.

Follow-up work

The audits identify the next implementation PRs:

  1. add provenance refs to value envelopes and artifacts
  2. introduce spaces, schema packs, type IDs, and role specs
  3. add journal integrity negative fixtures
  4. create RDF bridge crate skeleton with projection loss classification
  5. create Cypher/GQL facade skeleton

Validation

CI now enforces formatting, clippy, workspace tests, required governance files, and positioning guardrails.

@mdheller
mdheller merged commit caa09d3 into main Jun 1, 2026
3 of 5 checks passed
@mdheller
mdheller deleted the hardening/license-provenance-traceability branch June 1, 2026 11:40
mdheller added a commit that referenced this pull request Aug 3, 2026
* docs(adr): ADR-0004 Crown — seat the Telos Layer over the Truth Engine

Seat the estate's constitutional layer per the owner's flow diagram
(Telos Layer: objectives+constraints -> Truth Engine: falsifiable,
auditable), consume-not-fork over already-merged pieces:

- Keter (Crown) objective = welfare-annealing WEA-1 (economic-prophet
  PR #59), NOT control-max; constraints non-domination/consent/dignity.
- Da'at = policy weights/thresholds (omnirisk/outcome-pricing, the-assay
  grades, counter-test-gate); it CANNOT assert truth.
- Truth Engine = ts/src/discourse.ts + spec 14 + SILENT epistemic
  firewall (evidence-intake-kernel #2/#3) + Noetica counter-test
  detectors (PR #570) + Truth = Law x Evidence.

Add scripts/check-constitution.mjs (deterministic, stdlib-only) + a
fixtures corpus as the teeth, wired into CI. It enforces the cross-layer
invariants no single discourse.ts function sees, both directions:
- REJECTS Da'at asserting a POS/true verdict (D1, = firewall
  affirming-the-consequent guard).
- REJECTS a control/domination Keter telos as unconstitutional (K1,
  SILENT-vs-welfare inversion).
- REJECTS a TruthRecord with no TestObligation / no Witness /
  single-valued+atemporal; ADMITS a falsifiable, witnessed,
  multi-valued+temporal+adversary-aware record.
- Refuses a degenerate corpus so D1/K1 can't be silently removed.

Records two follow-up gaps under this constitution: Hygiene runtime
(no CTEST runner / no passport producer / LOGFALL id drift) and
XSEDE-PEP -> estate program-execution-plan.

* ci(crown): run build-and-verify-dist + constitution on ubuntu-latest (self-maintaining)

build-and-verify-dist is the only REQUIRED check on main and was pinned to the
self-hosted pool, which is currently online-but-not-dispatching (idle runners,
queued jobs) — stalling every PR incl. this constitutional ADR. It is a plain
node build (checkout/setup-node@20/npm install+typecheck+test+build+dist-verify)
with no self-hosted dependency, so it runs identically on GitHub-hosted runners
and is no longer blocked by the runner backlog. Same for the stdlib constitution
validator. This is the Day-2 self-maintaining fix: deterministic required checks
must not depend on a flaky pool.
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