System structure
THE FOUNDRY
Development and validation
Assessment, strategy, policy, controls, constrained code generation, verification, and deployment turn an expert method into a versioned operational artifact.
THE INSTRUMENT
Operational interface
A case-centered application gathers relevant evidence, presents approved authority when it governs, records human decisions, and creates the operational record through normal use.
CAUSAL SCIENCE
Impact and ROI measurement
The Measurement Contract defines the intended effect and comparison before release, drives instrument telemetry, and permits attributable outcomes and ROI only when its evidence conditions are met.
Intended applications
Operational instruments are intended for bounded workflows with identified owners, defined authority, multiple evidence sources, consequential decisions, and formal recordkeeping requirements.
Illustrative areas include:
- regulatory and compliance reviews;
- grant and procurement administration;
- requirements analysis and policy implementation;
- internal control testing; and
- other case-based processes with documented human decisions.
These are reference categories rather than claims about a customer, employer, or production deployment. A specific instrument is defined from the participating organization’s authorized materials and operating context.
The governed foundry
Seven composable planes transform an authorized method into a deployable instrument and a measurable intervention. Each plane has narrow authority and explicit things it may not do.
01 / CAPTURE
Capture the expert method
Adaptive questions and source analysis identify the case, workflow, authoritative language, evidence, decisions, data boundaries, acceptance criteria, and unresolved rulings.
02 / AUTHORIZE
03 / CONTROL
Make controls executable
A tailored NIST 800-53 Control Passport converts applicable obligations into implementation requirements, tests, evidence, exceptions, and monitoring duties.
04 / CONSTRUCT
Build inside the contract
The coding agent receives the authorized instrument specification, approved packages, prohibited capabilities, required tests, and deployment conditions. It does not receive an open-ended prompt.
05 / VERIFY
Test behavior and boundaries
Static analysis, dependency controls, functional tests, isolated execution, policy-adaptive semantic checks, and artifact verification assess the candidate independently.
06 / OPERATE
Release the exact artifact
Only the signed artifact that passed every mandatory gate can deploy. Identity, decisions, control evidence, runtime health, and outcomes stay attached.
07 / EVALUATE
Estimate effect and ROI
The Measurement Contract governs the outcome definition, causal diagram, intake fields, rollout, estimators, refusal conditions, cost model, and permitted claim level. Results inform the next authorized version.
Assessment and instrument specification
Questions are composable because expert methods differ. A pack can encode a regulated intake, requirements analysis, readiness assessment, program evaluation, or another consequential workflow.
Its output can include a BRD. The primary artifact is an Instrument Specification:
Operation
Case identity, actors, workflow states, evidence sources, data minimization, derived measures, human decisions, corrections, and closure conditions.
Assurance
Control profile, acceptance tests, negative tests, audit events, artifact lineage, deployment gates, monitoring, and reassessment triggers.
Impact
Intended outcome, estimand, exposure, comparison strategy, observation window, required covariates, subgroup analysis, cost model, assumptions, and claim threshold.
Two governing artifacts travel with every instrument
CONTROL PASSPORT
Can it operate as intended?
The Control Passport links the tailored NIST SP 800-53 profile to implementation requirements, tests, evidence, exceptions, approvals, and monitoring duties for the exact artifact.
MEASUREMENT CONTRACT
Did it produce the intended effect?
The Measurement Contract pre-registers the intervention, outcome, causal diagram, required fields, rollout, estimators, diagnostics, refusal thresholds, costs, and the level of claim the evidence can support. The analysis cannot silently relax it after seeing results.
Division of responsibility
The system separates language generation from institutional authority.
Models interpret
After Elasticsearch returns passages within tenant, authority, and version filters, models may extract structured facts, summarize retrieved evidence, answer bounded framework questions with citations, propose a permitted next step, generate candidate code, and apply semantic safety checks.
Deterministic systems enforce
They validate identity, derive scores, enforce state transitions, protect data boundaries, hash events and artifacts, run tests, and determine deployment eligibility.
People remain accountable
They confirm identity, answer consequential gates, resolve policy ambiguity, authorize exceptions, issue dispositions, and own the outcome.
Open foundations and professional operating infrastructure
The long-term company model keeps portable instrument specifications, event schemas, control mappings, causal measurement protocols, and reference validation tools open. The commercial foundry provides private organizational integration, identity, collaboration, governed construction, secure deployment, impact evaluation, monitoring, and support.
Candidate workflows
Causalytics is considering design partnerships for regulated case workflows that currently span policy documents, reports, spreadsheets, and manual records.