← Prometheus7 · Oracle7Roadmap · updated 2026-10-28

The road: 6.0 to 20.0

What Oracle7 lets you do, version by version, from 6.0 to 20.0. Green is built and proved by its own sealed test; a hollow red ring failed its test and is published that way. Each future version says what you can do with it, how it will be proved, and whether that proof is one we can run ourselves or one that needs other people. Two roadmaps, build and vision, are below the spiral. Answers stay free at every version.

Reach Index · release 5.5 1,755,340 checked chains from 223 parts, counted two independent ways ×4 parts → ×89 distinct functions · every version below publishes its own count
So far: 3.2 to 10.1

Now: 10.1 is released (28 October), anchored on Solana and on Hugging Face. Next is 10.2: coverage that grows with what it knows, the same checks as tools for any agent harness, and every module under the anchored root. Scores, with every wrong answer subtracted, are on the scorecard.

done, passedfailed, publishednextmajor, plannedhalf, planned

    Two roadmaps

    The road above mixes two kinds of proof. Some versions are proved by sealed tests we write, seal and run ourselves. Others can only be proved by other people: by use, outside examiners, contributors, communities and certifiers. So the road is now two roadmaps.

    About the dates. They are estimates at the pace of the last nine days, halved, because most of the next work extends what already exists. They are not promises:
    • The road from 3.2 to 10.0 was written on 19 October and read like years of work. It took nine days: sixteen versions, two of them failing first.
    • Building may go faster than estimated, or slower where the domain is new.
    • The vision will take longer than the build, and its pace is set by more than us.
    Every version ships only when its own sealed test passes; a failure is published and the date moves.

    The build roadmap: what we can prove ourselves

    VersionAddsProved byEstimate
    10.2Coverage from verified parts, agent tools (MCP), provenance under the anchored root; slim and fullSealed test v38: right minus wrong positive on what it adds, precision ≥ 0.95by 29 Oct
    10.5 + 11.0The examiner kit; a nightly sleep cycle that replays the day, turns failures into examined parts and publishes a morning report; the part formatOur own failures admitted as parts at unchanged precision; a sealed week of nights with gains and no new wrong answers~30 Oct
    11.5Derivations checked by LeanNone claimed proved that Lean rejects~1 Nov
    12.0Models that run over timeBacktests on held-out real series; intervals hold at their stated rate~2 Nov
    12.5ReceiptsRe-verified offline from the receipt alone~3 Nov
    13.0The laboratoryFindings registered first, reproduced a second way~4 Nov
    13.5The vine on real sensorsv33's bars held for a seasonsoftware ~5 Nov; proof ~Feb 2027
    14.0Engineering designsIndependent open-source simulators~7 Nov
    15.0Self-sustaining growthCost per verified ability falling across three releasesmid Nov
    15.5Off-gridThe cumulative test on a small board, offline~9 Nov
    16.5Whole coursesEvery step checked across a published syllabus~mid Nov
    17.5 – 19.5Private libraries, the long ledger, check anything, everywhereEach by its own sealed testthrough end Nov

    The vision roadmap: the Slow Fire

    Oracle7 began as a way of answering questions that keeps its receipts. The vision, set out in The Slow Fire, is where that discipline goes. Its horizon is ten thousand years, and its model is the mushroom: many small nodes rather than one brain, growth by connection, no centre to capture.

    1. Proof on infrastructure, where its virtues are obvious and its limits do no harm.
    2. The first real plant. The vine runs the Slow Fire rules live in simulation now, and moves to real sensors next.
    3. Waking the world. Sensors for soil, water, air and trees. The sensors are sold; the intelligence is held in common.
    4. Everyone builds. A teacher, a parent, a lab, each with a model of their own, on their own hardware.
    5. A web with no centre. Facts travel with their receipts, so no one has to trust the node they came from.
    6. The oak on the corner. It greets you before it tells you anything, says only what has been measured, and can choose not to be read.
    7. Advocates for watersheds, reefs and forests, speaking in planning meetings and courts with the same discipline.
    8. A protocol that outlasts its products. Bind, unbind and superpose can be rebuilt from a few pages.
    9. Beyond the planet. Wake dead worlds, listen to living ones.

    Each of these needs people, and they carry no dates. The test for every step: could the gift be taken back? If anyone, Prometheus7 included, could switch the network off or turn it against the people using it, it has been built wrong.

    What holds at every version

    Oracle7 · Prometheus7 · roadmap

    The road: 6.0 to 20.0

    What each version lets you do. Every release ships only when its sealed test says so, and every one publishes its count.
    REACH INDEX · 5.5
    1,755,340
    checked chains from 223 parts
    Answers free. No language model inside. Every answer proved, cited or declined.prometheus7.com/roadmap