One-page ledger report
A concrete executive-readable output connecting intent, evidence, commitment, constraints, and outcome.
Open PDF →
Public resource index
Go deeper without losing the path.
Start with the practical motion, follow the route appropriate to your question, and use the deeper library only when you need to inspect how a claim is known.
Start and evaluate
See the product motion first.
Overview deck
A short buyer-facing PDF explaining the problem, operating model, representative scenarios, pilot motion, and current maturity.
Open PDF →Quickstart for analysts
Fill one JSON or CSV template, run one command, and inspect a plain-language readout.
Open quickstart →Governance console
A static bounded demo of ready, constrained, blocked, missing-evidence, and review-action states.
Open console →AI Worker Assurance console
A fixture-backed UI applying the same evidence, ledger, readiness, review, and proof path to two distinct public-chatbot evidence packs.
Open assurance console →Buyer FAQ
Plain answers about workflows, evidence, commitment boundaries, starter inputs, and current maturity.
Open FAQ →Discovery intake
A bounded conversation about workflow samples, evidence sufficiency, responsibilities, and pilot scope.
Open the first-review path →Pilot starter material
A controlled handoff for approved reviewers running a sample evidence bundle and inspecting its outputs.
Request controlled access →Technical Foundation
Inspect architecture, boundaries, and proof.
Architecture
The implementation-facing system truth behind ingestion, governed semantics, evaluation, and readouts.
Open architecture →Semantic boundary
The canonical separation of evidence, interpretation, semantic state, and representation.
Read the public explanation →Telemetry layering
Execution, transport, canonical trace, enrichment, and interpretation layers.
See the public architecture →Evidence of Thinking Matrix
How corrections, constraints, reframes, commitments, and resolutions become reviewable evidence.
Request controlled access →Adapter evidence contract
What sources must provide, preserve, or leave adapter-local before promotion.
Request controlled access →Implementation scope matrix
Implemented, canonicalized, provisional, and excluded scope with precise limitations.
Request controlled access →Claim-to-proof map
Public claims mapped to demos, fixtures, tests, regressions, milestones, and limitations.
Request controlled access →Technical vocabulary
QTF, PEI, semantic boundaries, and status discipline within the Epistema architecture.
Open Technical Foundation →Strategic Asset
Inspect category, value, and commercial context.
Ecosystem position
Where Epistema sits relative to governance suites, observability, compliance, and audit systems.
Read the strategic position →Governance patterns
Public-source cases mapped to missing evidence, unclear authority, and delayed calibration.
Open patterns →CIO brief
Why outputs becoming commitments before workflow readiness creates executive exposure.
Open PDF →Commercial pilot material
The controlled pilot document set, data and IP posture, and bounded engagement skeleton.
Discuss a pilot →Product surface
Workflow Value Ledger, governance console, evidence intake, and executive-readout boundaries.
Review the public product boundary →Company foundation
Founder context, public IP position, principles, and the relationship between research and product.
Open company foundation →Research provenance
Background that produced the product—not a parallel product claim.
Explanatory Power thesis
The human-agency thesis: AI should increase explanatory power rather than hide commitments.
Read the public foundation →Research program
How research, architecture, implementation, and commercial pressure-testing inform one another.
Read the company foundation →Operational pathology
A research note mapping public AI and automation patterns into lifecycle and ledger evidence.
Open PDF →Principles
The constitutional commitments behind evidence, human judgment, correction, and controlled uncertainty.
Read the public principles →