Research through operation

Do not take our word for it. Run the work.

VALO Research starts with a hard operational need, builds and tests an operative system, captures evidence, and transfers what survives back into reusable products and methods.

Governance belongs to Heimel.Heimel is the authority infrastructure for consequential action. VALO Research develops, tests and operates systems that may use Heimel; VALO itself is not the governance layer.
01

Need

A real workflow, decision, failure mode or economic unit that must be handled.

02

Build

Compose the contracts, capability, evidence and control primitives required for the work.

03

Execute

The work runs through an operative path rather than a slide or policy document.

04

Prove

Decision, effect and outcome evidence remain inspectable and replayable.

05

Transfer

What survives becomes reusable contracts, products and operating knowledge.

Operating model

VALO is shown through the work it can carry.

The public surface starts with operational systems, cases, executable demonstrations and the evidence they produce. Governance and authority are a separate infrastructure concern handled by Heimel.

VALO Research → Work → operative systems → evidence

Research becomes valuable when it survives changed state, negative conditions, real execution boundaries and contact with actual outcomes.

Evidence → learning → VALO

Passes become reusable. Failures change the model. Unknown remains unknown.

Portfolio is proof.Every operative surface should demonstrate a claim, generate evidence, or expose a failure boundary.
Live and executable proof

Start with a claim you can test.

Each surface states what it proves and what it does not.

Interactive simulation
EXECUTABLE AUTHORITY

Same agent. Same credentials. Authority changes.

Heimel/REHT recomputes the decision against current authority at consequence time.

Proof target: permission held earlier is not final permission at execution time.
Run Executable Authority →
Interactive simulation
TAVLER × VALO

Compliance state becomes an execution boundary.

An AI-prepared GDPR disclosure is not enough. Recipient, identity and authority must still be valid when the action would create effect.

Proof target: compliant preparation cannot bypass consequence-time handlingsrett.
Run the GDPR execution demo →
Implemented test surface
GCU INVOICE RECONCILIATION

Treat completed work as the unit.

The pilot tests a work contract across execution, completion evidence, metering and downstream settlement.

Proof target: preserve one work-unit identity across different execution mechanics.
Inspect the GCU primitive →
Conformance evidence
PUBLIC + TRADES PACKS

Failure conditions are first-class tests.

Case transitions and bounded operational jobs are exercised against negative conditions.

Proof target: invalid work stops before consequence rather than becoming an audit finding afterward.
Open scenarios →
Research discipline

Build. Break. Measure. Transfer.

VALO does not claim strength from architecture diagrams. A claim earns its place by surviving falsification, execution and replay.

Work first, evidence second, primitives third.
Drill down

The primitives underneath the work.

Only after the visitor understands the work do we expose the underlying control and economic primitives.