The Oracle7 Build Constitution

What this is

The Oracle7 build constitution is the set of rules every Oracle7 build is made to. There are nine. The first is that Oracle7 is built to receive: wherever it meets something, it takes it in, checks it under its law and grows from it. Each rule has a check, and every sealed test answers those checks. 10.5 is the first build made to it.

1. Built to receive

We have everything we need. It just has to, again, be connected up properly, and it has to be designed properly in order to receive. Ben Horn, 2026-10-30

Oracle7 meets the world at its edges: a question, a fact someone tells it, a correction, an example, a reading it isn't sure of yet. Built to receive means each of those edges is a tip that takes something in.

• A question it can't answer yet gives a hole, which says what kind of thing is missing. The next turn can fill it.
• A fact or a correction becomes a claim that goes through check.
• An example feeds the learner.
• A reading it isn't sure of is offered, marked as held back.
• Sleep digests what came in, and what proves itself joins the network.

Everything received goes through the law. A claim someone hands it stays a claim until it is proved or cited, and the same checks apply to what comes in as to everything else. The pieces for all of this exist in Oracle7 today, so the work is connecting them.

2. Terms

Oracle7 is described in its own terms, used here as follows.

Receive

Taking something in at an edge, under the law.

Store

What Oracle7 holds, named and addressable.

Lighting

The words of a question light what matches across the stores, addressed on the Tree of Life scaffold.

Shape

The structure of a reading: its steps and how they join.

Judge

The check that each word of the question is accounted for in the steps of the answer.

Hole

A typed gap in a reading. It says what kind of thing is missing.

Part

A unit admitted by examination, such as a specialist, formula or organ.

Law

Every answer is proved, cited or declined.

3. The articles

Each article ends with a check. Every pre-registration answers each check for its build. If a build can't meet an article, the measured reason is written down before the seal and Ben Horn decides. The layer 0 constitution, which governs how Oracle7 is as a self, stays in force unchanged. This one governs how Oracle7 is built.

Article 1. It is built to receive

Every place Oracle7 meets something is a tip that takes something in, as set out in section 1. What exists is connected first.

Check. Every new or changed stopping point says what it takes in and where that goes.

Article 2. The law holds

Everything received goes through the law: every answer is proved, cited or declined. Reach is not answer. A sealed test is pre-registered and run once, its failures are published, and every change to a check is stated. A claim about what Oracle7 does is tested on the release before it is said. Each release ships the records its changelog points to. A check that refuses true answers is a defect in the check, and it is measured and reported as one.

Check. A sealed run, a published verdict, every changelog claim tested, every file the changelog names in the pack.

Article 3. It grows as a network

The compounding growth is only added with specialists as a specialist adds a capability in a certain area and allows for more combinations overall. 2026-10-23

Oracle7 is a mycelium. Tips sense, hyphae fuse where they meet, it digests outward and absorbs, grows where there is food, and retracts from dead ends with receipts. The network is the intelligence, and releases are its fruiting bodies. Growth is measured as reach from combinations, against the number of parts.

Check. A growth claim reports reach from combinations. A new part says what it connects to.

Article 4. One Oracle7

A version is everything before it, plus its own addition. New capability plugs into the head, under its gate, through the one front door. Designing starts from an inventory of the released pack: head runtime, chat, ego and emotion, social, specialists, organs.

Check. The capability ledger has a row for the version, and every earlier row still says it is in the head.

Article 5. It is described in its own terms

Everything here is brand new in regards to what I'm building. 2026-10-30

Oracle7 is designed and described in the terms of section 2. Terms from other fields (symbolic AI, semantic parsing, retrieval, language models) stay out of its design and description. There is no language model inside it, and public text says so. A form borrowed from another field is named and earns its place.

Check. The design note and public text use these terms. Any borrowed form, name or format in new work is listed with the reason it stays.

Article 6. It is measured by what it does with what it knows

The measure is capability per unit of knowledge. Comparisons with other systems are made on equal knowledge, with both given the same store. Benchmarks are outside examiners. The design comes from Oracle7.

Check. Every comparison states what knowledge each side had.

Article 7. It is built to the design

Each build starts with the mechanism in five lines of the designer's words, and the code's shape is checked against them. What can be learned or read from the store is learned or read. A defect is fixed as a class, at the one place every instance passes.

Check. The five lines are in the pre-registration. Any hand-written list about data is named and justified.

Article 8. Limits are measured

A limit is a measured number of the current build, plus the route that would move it. Every limit stated comes from Oracle7's own measurements.

Check. Every stated limit has its number and its route.

Article 9. What stays with the designer

Signing every release anchor on Solana, approving the running of contributors' code and any post to their threads, and changing this constitution or the frozen identity. Contributors are credited by name, and what they find is measured the same way as anything else.

Check. The record shows each of these approvals.

4. Starting measurements

Release 10.3.2 is where the work starts. A first audit of the slim tree, head w574, gave these starting points for the builds that follow. It was a first pass, using file reads, term counts and three runs with throwaway state.

• Taking in a fact. Asked the boiling point of a made-up substance, it declined. Told the value, it replied with six cited sentences on boiling points in general. Asked again, it declined again. 10.5 starts here.
• Held-back readings. On 1,428 development declines, the coverage stage finds 361 right and 79 wrong readings. At its threshold of 0.79 it uses 46: 44 right, 2 wrong. The other 317 right and 77 wrong are what 10.5 can offer as held back.
• Checks on how an answer was reached. Two owner-stage rules look at the shape of a reply. They hold back true answers such as 0 for more successes than trials. The next step is to check how the answer was reached.
• The reader's own steps. The reader's steps carry the function names of KQA Pro, an outside question set, and its tables are learned from that set's training data. Oracle7's own steps take their place, measured so that nothing is lost.
• Records in the pack. From the next release, each pack carries its sealed records and the files its changelog names. The capability ledger is brought up from 10.0.

5. Order of work

Verify

Release 10.3.2 passed sealed test v41, run once on each tree: 37 of 37 rows and 9 of 9 bars. python oracle7.py verify recomputes the root from a copy, and each root is anchored on Solana.

• Slim: root 6b89a634ecd4…, anchor, repository
• Full: root 414667ae5ed0…, anchor, repository