Two tracks, one method.
This is the overview and the standing discipline both research branches answer to—the one place the human-systems work and the machine-systems work are named together, kept in separate sentences, and held to the same order.
Two lines of research, held to one order.
The Immanence Project runs two lines of research that address technical and academic readers directly. AFCIS is the human-systems branch: the pedagogy, the field evidence, and the record that carries what a learner can actually do. Project Arkhan is the machine-systems branch: governance software that asks what an action is allowed to be before it asks what a system is capable of.
The two branches share one method, not one customer, one budget, or one claim. They are architecturally and narratively distinct, and on this site they never blend into a single sentence. What they inherit in common is the ordering discipline set out in The Method: a foundational claim is established before the claims that depend on it, and a later result never repairs an earlier one it was built upon.
For a reader coming to the human-systems work, the entry question is this: how does AFCIS contribute to the field? The Skills Gap tab is that question’s evidenced answer—it sets out the field problem the pedagogy is built to resolve, grounded in outside research rather than in our own assertions.
The Method — the shared root both branches inherit.
The dependency-first logic that comes first because nothing else is intelligible without it. Read this before either branch.
How does AFCIS contribute to the field?
The Method applied to learning, the field evidence it answers to, and the record that carries what a learner can do. Read in order—the theory, then its empirical ground, then the forward destination.
Pedagogy & Philosophy
The Hierarchical Pedagogical Model: The Method instantiated in a classroom as seven dependency-ordered layers, and the design logic beneath Catalyst.
The Skills Gap
The empirical field diagnosis AFCIS answers—why the communication and problem-solving gap is a translation and definition problem, not a motivation problem. The evidenced answer to the entry question.
Skill Wallets & the LER
The forward destination for the evidence students produce: the five conditions of a genuine Learning and Employment Record, built toward on open standards.
Admissibility before capability.
The machine-systems branch, parallel to AFCIS and sharing the method and nothing else. KCH is the governance technology; QAVL is the current focus; the governance kernel is the tested core.
KCH — Governance Technology
The Kernel-Cluster Hierarchy: a governance layer that coordinates policy, evidence, runtime, authority, memory, and audit, and returns a bounded admissibility verdict—without collapsing foundational requirements into a single score.
QAVL — Quantum-Advantage Verification
The current focus: a classical, hardware-free layer that decides whether a quantum-advantage claim is admissible against a fair classical baseline, and emits a reconstructable audit trail for every verdict.
The Governance Kernel
The tested core: capability is not authority, established structurally rather than promised. Also referred to as Arkhan AI, it is a governance simulator and buildable foundation, unpublished and seeking peer review.
We label assumptions as assumptions.
This section carries the hub’s honest limits, because the discipline it names is the limit. We label an assumption as an assumption. We do not dress a proposal as a proven result: where a claim is still a proposal or an open question, the page says so, in the words designed for it—“is designed to,” “aims to,” “early results suggest,” never “achieves,” “proves,” or “guarantees.”
When we are wrong, we retract rather than defend. Stating a limit is not a disclosure risk; it is a credibility asset and a standing rule. Every tab in this hub names plainly what its artifact does not claim, and no later tab is written to prop up a claim an earlier one has not earned. That restraint is the whole point: the work is built by necessity, and a claim earns its place only when the claims beneath it are established.
Where the work stands, stated honestly.
The education and pedagogy work—the Hierarchical Pedagogical Model—is being prepared for education-theory venues. It is a structural theory and a design claim; it has not produced pilot outcome data, and we do not present it as a proven empirical result.
Project Arkhan governance-kernel report — unpublished
The governance-kernel report is a completed internal artifact now being prepared for peer-review submission and actively seeking a venue. It is unpublished: it has appeared in no journal, conference, or peer-reviewed venue, and nothing here claims acceptance, review, or endorsement by any outside body. Its internal adversarial peer-review is a self-directed exercise that mirrors venue standards—not an actual external submission, review, or endorsement. Where a claim is still a proposal or an open question, we say so.
We build by necessity. A claim earns its place only when the claims beneath it are established. We would rather leave the work smaller and truer than dress a plan as more certain than it is.
The Immanence Project LLC · Denver, Colorado · Prepared in the structural mode of the Hierarchy of Concepts.