VIRIDISSECURITY
Request assessment

Research and proof atlas

Research you can inspect. Proof states you can distinguish.

Viridis turns formal security research into bounded architecture evidence without claiming that an abstract theorem certifies a customer system.

Published open preprint · August 2026

Robustness Before Performance: A Governed Decision Kernel with Formally Verified Release Boundaries

A domain-independent, non-actuating decision architecture for comparing systems under mandatory disturbances. The archived release binds the paper to its implementation, proof environment, provenance and exact checksums.

Published record
10.5281/zenodo.21855705
Formal release
27 Lean theorems · 19 review checks · zero proof holes
Version and license
1.0.0-formal · CC BY 4.0
Execution authority
None
Read the paperView Zenodo recordDownload PDF
© 2026 Justin D. Hart. Published as an open preprint under CC BY 4.0. Zenodo publication is a citable archival record; it is not peer review, empirical validation or security certification.

Canonical citation

Hart, Justin D. (2026). Robustness Before Performance: A Governed Decision Kernel with Formally Verified Release Boundaries (1.0.0-formal). Zenodo. https://doi.org/10.5281/zenodo.21855705

The proof atlas

Formal obligations organized around buyer risk.

These families shape reviews and evidence requests. Their status is preserved individually; a proof about an abstract model is not proof that a customer implementation satisfies it.

01

Authority and composition

  • Attribution conservation
  • Envelope closure
  • Composability attribution
  • Scoped approval monotonicity
02

Tool and data boundaries

  • RAG noninterference
  • Context-taint dominance
  • Secret non-observability
  • Purpose-bound data use
03

Recovery and containment

  • Control-loop stability
  • Rollback compensation completeness
  • Blast-radius containment
  • Fail-closed escalation
04

Evidence and governance

  • Receipt-bound determinism
  • Evidence completeness
  • Audit-ledger tamper evidence
  • Evidence freshness windows

Claim firewall

One word should never hide five different states.

Viridis reports the strongest supported state and no stronger. A theorem does not authenticate inputs, prove deployment, establish authority or demonstrate a paid outcome.

  1. 01

    Formally proved

    The abstract statement is machine checked.

  2. 02

    Compiled

    A proof kernel or detection package builds and passes its gate.

  3. 03

    Empirically validated

    Authorized evidence supports the real-system mapping.

  4. 04

    Deployed

    The control is verified on the named running system.

  5. 05

    Commercial

    A buyer has paid for or signed the delivered outcome.

Apply the architecture

Turn the paper into a decision about your agent system.

Bring two candidate architectures, their mandatory obligations and the disturbance you cannot afford to ignore.

Request an assessment