Vulcan Cranium
The larger body of thinking, expression, architecture and public-facing work. Not a software product masquerading as a philosophy.
A developing body of ideas, governed artifacts, and practical systems for preserving human intent, examining claims, and working across AI engines—without surrendering ownership of the thinking.
Vulcan Cranium is the umbrella. SpocksBrain provides governed persistent context. TruthBand explores claims and evidence. They belong together without being interchangeable.
The larger body of thinking, expression, architecture and public-facing work. Not a software product masquerading as a philosophy.
A portable, artifact-centered method for carrying identity, decisions, continuity and context across execution hosts.
Evidence-first examination: surface claims, separate observations from inference, preserve meaningful disagreement and make reasoning inspectable.
An AI model executes. A governed context system establishes what is authoritative, what is provisional, and what survives a particular conversation or vendor.
A public paraphrase of the publication architecture's framing—not a claim that AI inference can be perfectly preserved or that hosts behave identically.
Governance defines the system. Applications, interfaces, and dynamically composed components can extend its realization without replacing that authority.
Ideas, decisions and context need not disappear with a chat session.
Version, source, status and provenance can be examined explicitly.
Context can be assembled for different compatible AI hosts.
TruthBand's emphasis is not which conclusion is fashionable. It's whether evidence supports a conclusion, whether the reasoning survives scrutiny, and what remains unknown.
Capture the claim accurately. Distinguish an observed fact from a characterization of it.
Trace evidence, sources, context, contradictions and the steps between premise and conclusion.
Test competing interpretations against the same standards. Preserve unresolved questions rather than hiding them.
Search the vocabulary, then open any card for a real explanation, example, key distinction, and connections to related concepts. These are public-facing interpretations, not internal artifact exports.
The publication architecture contemplates distinct audience-facing forms, not a single giant manual. Readers should be able to recognize what matters to them without being told how to think.
Why this exists; a clear statement of purpose.
What it is. Decide whether it is for you.
Accessible starting points on the reader's own terms.
Applying the principles to real working systems.
Design, extension, governance and stewardship.
Published references and attribution are distinct from private project brains, operational context and personal artifacts.
The pattern applies beyond a philosophical discussion: document a thought, establish its place, test the implications, and make the resulting knowledge reusable without confusing a sketch with a decision.
Its public presentation is plain HTML, CSS, and JavaScript. Its source can be archived in Git and deployed to a different host. The site is a view onto selected concepts—not the governing system itself.
A richer public reference index, diagrams, selected releases, verified demonstrations, and source-linked publication pages can be layered onto the same site without changing hosts.