OSCILLA®

OSCILLA — THE PLATFORM RECORD

Changelog.

Every model version, console feature, API change and fix, in the order it shipped. Releases are dated, tagged by kind, and kept — nothing here is quietly edited afterwards.

Oscilla-1.2 — longer proofs, steadier citations

OSCILLA-1.2 MODEL 05 NOV 2026
  • NEWProofs hold together past 40 steps; the counter-example search now runs alongside the proof from step four, not after it.
  • NEWUnits and frames are declared in the premises and enforced by the checker.
  • CHANGEDRuns are described as attacked, depth 8, survived — the word “verified” is retired.

Console 2.3 — run replay and cited steps

CONSOLE 2.3 PLATFORM 29 OCT 2026
  • NEWRun replay: any run, replayed case for case, including the searches that attacked it.
  • NEWCitations inline in the run view — every claim carries its source where it is read.
  • CHANGEDThe audit ledger exports in one file, signed, readable without the console.
JUN AUG OCT NOV
FIG. — RELEASES PER MONTH, ALL KINDS · DEMO DATA

API — pinned model versions

API 2026.10 API 21 OCT 2026
  • NEWPin a model version per key: model: "oscilla-1.2" in the run request. Pinned versions never move under you.
  • NEWEvery response carries the exact version and the search depth that attacked the proof.
  • DEPRECATEDThe unversioned latest alias retires on 01 FEB 2027; pinned keys are unaffected.

Oscilla-1.1.1 — three quiet corrections

OSCILLA-1.1.1 FIXES 14 OCT 2026
  • FIXEDCitation checks now catch a source that supports a neighbouring claim but not this one — the three corrections of the title.
  • FIXEDA replay edge case where searches with identical seeds diverged on tie-breaks.
  • FIXEDLedger exports no longer drop the final entry of a run that ended mid-search.

Console 2.0 — VPC deployment and the audit ledger

CONSOLE 2.0 PLATFORM 06 OCT 2026
  • NEWDeploy the console and the runner inside your own VPC; runs and ledgers never leave your network.
  • NEWThe audit ledger: every run, step, check and citation in one append-only record.
  • CHANGEDAccess is per-project with named roles; the shared workspace key is retired.