VIRIDISSECURITY
Request assessment

Proof-carrying agent resilience

Know what survivesbefore you optimize it.

Viridis compares agent architectures under compromise, outage and recovery using formal invariants, declared evidence and signed decision receipts.

Request an assessmentInspect the research
Published open preprint10.5281/zenodo.21855705
DECISION KERNEL / 01NON-ACTUATING
MANDATORYVIABLE?HOLD ON UNKNOWN
AUTHORITYSAFETYRECOVERYEVIDENCE
DisturbanceDeclared
UncertaintyHold
ExecutionDisabled
FORMAL INVARIANTSDECLARED DISTURBANCESCOMMON-MODE ANALYSISSIGNED RECEIPTSNON-ACTUATING

What customers buy

A defensible architecture decision.

Most security products find patterns after a design exists. We help teams choose the architecture that remains viable before performance and deployment pressure make the choice expensive.

01

Agent Resilience Gate

Compare two agent or MCP architectures under declared compromise, outage and recovery conditions before committing to the faster design.

View offering
02

Proof architecture review

Map authority, dependencies, fallback paths and proof obligations to the exact system boundary your team owns.

View offering
03

AI control-boundary review

Test tool, retrieval, memory and action boundaries against instruction injection and unsafe authority transfer.

View offering
04

Verified vulnerability research

Move from source-grounded hypothesis to reproducible evidence without promoting scanner output into a security claim.

View offering

The proof chain

Architecture evidence, not a generic risk score.

The kernel orders authority, safety and mandatory viability ahead of nominal performance. Unknown mandatory evidence produces HOLD.

  1. 01

    Bind authority

    Name the owner, system boundary, protected obligations and allowed evidence.

  2. 02

    Map dependencies

    Trace agents, tools, providers and recovery paths to their shared roots.

  3. 03

    Apply disturbances

    Compare mandatory viability, containment and recovery before nominal speed.

  4. 04

    Issue the receipt

    Preserve inputs, uncertainty, limitations and the non-actuating decision.

Research translated into product

Proof states your team can distinguish.

A theorem can prove an abstract model. A compiled rule can detect a pattern. Customer-system evidence must still bind the model to the real architecture. Viridis keeps those claims separate.

Open the research and proof atlas
DECISION RECEIPTED25519 / HASH-BOUND
Architecture boundaryDeclared
Mandatory uncertaintyFails closed
Deployment authorityNot granted
input_sha256 → decision_sha256 → signature

Design-partner assessment

Bring two architectures and one decision that matters.

We return the authority map, disturbance comparison, common-mode analysis, limitations and signed advisory receipt.

Request a resilience assessment