For the operational summary of how the corpus governs itself — what cogentia.js does, how continuations work in practice, what the audit trail contains — see the methodology page.
The corpus
The work spans five repositories, each producing research-grade documents that cross-reference each other:
- MareNostrum — strategic framework, CXU specification, DHITL (Democratic Humans in the Loop), Mediterranean solar commons, circuit-to-packet transition theory
- FractaVolta — physical infrastructure layer: EPN, PGN, DC-native nodes, IPN, Mariani Village
- Cogentia — cognitive infrastructure tooling: cogentia.js, Cogentia Commons methodology, continuation protocol
- inseme — platform and COP runtime: Cognitive Orchestration Protocol, briques, applications
- barons-Mariani — political/institutional framework: Plan 2038, Discours de la seconde méthode
Each repository carries a research/index.md (this is FractaVolta's) and a research/corpus-status.md. Together they constitute the navigable map.
Foundational papers by layer
Energy substrate
- The Unconscious Grid — store-and-forward as the repressed solution to energy sovereignty
- DC-Native Energy Packet Networks — 48V SELV node architecture
- Packetized Gravity Networks — hydraulic exergy
- The Packet Transition: A Lateral Reading — phronèsis, amathia, transition taxonomy
- The Packet as Evolutionary Attractor — complexity-theoretic framing
Compute substrate
- CXU Specification — Compute eXergy Unit pricing primitive
- Inference Packet Networks (v2.0, 2026-05) — packet logic applied to inference continuity
Cognition layer
- Agent-Resumable CLI — externalized judgment, continuations, provider-neutral resumption
- The COP Manifesto — TCP/IP for intelligences
- COP Architecture — full protocol specification
- Cogentia Commons Working Paper — methodology for distributed knowledge production
Civic layer
- DHITL — Democratic Humans in the Loop — the axiom: AI may participate in epistemic production; living persons alone govern
- Discours de la seconde méthode — methodology rules (publish process, objections as first-class, machine-readable structure, corpus as evidence)
The methodology
The corpus follows the second method:
- Publish the process, not only the result. Continuations make the process inspectable — where the system asked, what alternatives existed, who answered, how it resumed.
- Every objection is a first-class contribution. Falsifiable claims, marked-unfalsifiable feelings of certainty, requests for specifics — all are typed, all are recorded, none are erased.
- Structure for machine readability from the start. Stable identifiers, schemas, canonical URLs, append-only audit logs.
- Let the corpus be its own evidence. The repositories demonstrate the method on themselves: cogentia.js scans for unanchored claims; continuations process those decisions; the audit trail is part of the proof.
- Encode the boundary in the architecture (Rule 0). Epistemic participation vs political governance: AI agents may supply judgment, but binding decisions require signed human accountability.
The continuation protocol
cogentia.continuation.v1 is the operational realization of cop/continuation (COP's foundational continuation primitive). It is a typed, validated, provider-neutral resumption point for CLI tools.
The soundness test is binding:
Can Claude be replaced by a human, or by another agent, without modifying
cogentia.js? If yes, the protocol is sound. If no, the protocol is contaminated.
The protocol is implemented in scripts/cogentia.js as of v0.5.0. Subcommands: continuation emit, inspect, resume, fail, abort, queue, schema. See the paper for the full design.
Heraclitean follow-up: every resume that closes a continuation (success or abort) emits a dormant successor. History never 100% ends; the only constant is change.
How to contribute
The corpus is open source under CC BY-SA 4.0 (research) and MIT (code). Three ways to engage:
As a contestant
- File an objection on any paper as a GitHub issue or pull request.
- Per Rule 2, your objection becomes part of the record. We will either convert it to a falsifiable claim, mark it as a feeling-of-certainty (with attribution), or request the specifics that would make it testable.
- A continuation will be emitted for the conversion. You can watch the audit trail in
.cogentia/continuations/.
As a contributor
- Fork any repository.
- Add to the research index following the canonical patterns (front-matter with
canonical_url, the.cogentiaignorefor operational artifacts). - Run
cogentia.js scanto verify your additions are anchored. - Open a PR.
As an extender
- Write a new brique for inseme (see BRIQUE_SPEC).
- Write a new continuation profile on top of
cop/continuation. - Replicate the EPN / PGN / IPN architecture on a different territory.
Toolchain
cogentia.js— the Cogentia Commons CLI. Multi-repo scan, link validation, canonical URL stamping, continuation protocol. Installation: clone the cogentia repo, runnode scripts/cogentia.js help.- inseme + COP — the deployable platform. Installation: clone the inseme repo, see the README for the Turbo monorepo setup.
.cogentia.json— per-corpus registry of repositories (created bycogentia.js add)..cogentiaignore— per-repo ignore patterns for operational artifacts that shouldn't be flagged as unanchored claims.
Contact
📧 jhr@baronsmariani.org 🌐 FractaVolta on GitHub · research index
All papers: CC BY-SA 4.0. All software: MIT.