03 / Theses tested

Lenitnes

Pre-registration for software-change judgments

See it live

Lenitnes is a pre-registration machine for software-change judgments. Typed detectors watch commits; a versioned rubric scores each one; Hedera HCS notarizes the verdict before the outcome is knowable. The scorecard recomputes from the same tables the calls are written to, so the system cannot misremember its own performance.

What varies by vertical is only the corpus, the rubric, the grading authority, and the action a high-conviction call triggers. [markets] is graded by price; [research] is graded by the dated scientific record. Markets were Season 1 because they are the hardest oracle. Replays of halo2 and 3dClustSim calibrate the instrument; live scoring is the record.

Who it's for

Protocol teams, custodians, and market makers on the markets vertical; labs and scientific-software maintainers on the research vertical — anyone who needs a timestamped judgment on a commit before the outcome is knowable.

The problem

Software changes can move a price or invalidate a published result in hours. Judgments made after the fact can be spun. Pre-registering the call — before the outcome is knowable — is the only honest record.

Systems

GitHub, Hedera HCS, Consensus-critical protocol repositories, Scientific software repositories

What it can read

Public commits to watched [markets] and [research] repositories
Versioned rubric scores and detector output (v4 markets / v6 research)
Literature corroboration for research scoring — never as the primary signal

What it can write

HCS-anchored verdicts on every committed call
[markets] tracked positions — paper fallback, live venues behind a double kill switch
[research] integrity alerts — broadcast only after the HCS anchor succeeds

Approval gate

Markets execution is gated behind a double kill switch with paper fallback. Research broadcasts fail closed if HCS anchoring fails. The /scan leak-scan is a capability demo, not an enterprise write-path.

Live today

Public scorecards for both verticals, Season 1 [markets] closed record, a maturing [research] cohort, halo2 and 3dClustSim case studies, and a labeled /scan leak-scan demo.

Next step

Inspect the public scorecard, read the two founding case studies, or run /scan on a public repo. Enterprise leak-scan is a demo — book a walkthrough to talk about the direction.

Further evidence

Pre-registered software-change judgments · Commit-level market and research signal · On-chain thesis scorecard

Product subdomain: https://lenitnes.persidian.com. This page is the canonical Persidian entity reference.