Research methods · Evaluation workflow
How LARI research is tested and reviewed.
This six-step workflow describes how experiments are framed, checked, documented, and approved. It is the research method—not LARI’s technical architecture.
State a question and observable outcome
Define behavior in checkable terms, including success, failure, and inconclusive outcomes.
Build or select a candidate behavior
Keep candidate behavior distinct from existing infrastructure and authored procedures. Reusing a pre-existing routine alone does not show that a capability was learned.
Compare against a baseline
Record the starting behavior and environment so readers can see what changed and which controls separate the candidate’s effect.
Verify scope, transfer, and failure cases
Test the conditions named by the claim. Identify fixtures, fresh-process checks, unseen cases, and important paths that remain untested.
Retain or reverse the change
When persistence or rollback is part of a study, measure those operations directly. Do not assume one surface’s result applies to every path.
Publish only an approved record
An authorized reviewer checks public wording, measurements, provenance, privacy, and limitations. Only allowlisted fields enter the static snapshot.
A passing workflow does not establish that every kind of learning, verification, persistence, or rollback works generally.
Explore approved results
Architecture, with evidence attached.
Lari Live shows only records that pass review and approval.
Open Lari Live →
Discuss this page
Read and join this page’s discussion here. Sign in to GitHub when you want to reply or react.
Loading discussion from GitHub…
The embedded discussion could not be loaded. Browse discussions on GitHub ↗