%id
Identify
Without a name, how do we know which thing this is?
Content forms its address. Values, roots, and commits can be identified by their own structure. A name is an entry point, not an identity.
In n/, that addition is written &. It does not concatenate text. It lets two independently valid programs converge into one value: compatible information combines; contradictions keep their cause.
Each file knows only half. oo places both in one universe and converges them with lattice meet. Reverse the file order and the answer stays the same.
server: { host: "127.0.0.1" }server: { port: 8080 }{
host: "127.0.0.1"
port: 8080
}oo run server.n deploy.n --observe serverIf you know CUE: the resemblance is an ancestry we acknowledge, not a rival we hide. n/ begins with lattices and unification, then asks about durable identity, history, observation, and exchange across machines.
These are not three parallel features. They are three hands grown from one question. Mathematics is not a fourth hand; it is where the other three are tested.
Without a name, how do we know which thing this is?
Content forms its address. Values, roots, and commits can be identified by their own structure. A name is an entry point, not an identity.
Without running the whole world first, how do we know what it is?
Evaluation follows the path being observed. What was not requested remains lazy; when the view is incomplete, the result must say so honestly.
When two structures meet, who decides the result?
The lattice laws decide convergence. Compatible constraints become more precise; incompatible ones yield caused bottom instead of a silent overwrite.
Before theory and implementation can support a design, the clearest thing available may be a philosophical hypothesis. n/ writes it down first, then lets mathematics, the engine, and the record of failure test it.
State the unproven sentence clearly enough to guide a design.
Let it lead to lattices, caused bottom, call-by-observation, and content identity.
Submit every claim to the specification, probes, conformance vectors, and a real engine.
Do not erase mistakes from history; record what the correction actually moved beside the code.
The tablet below is not an answer. It is a primary record of what the project wrote down before it knew whether the answer would hold.
As above (Top _), so below (Bottom _|_);
as in the void of the whole, so in the truth of the atom.
To work the one miracle — convergence.
All the universe is Combo — a field the wellspring of the possible, an atom the fruit of the existent.
By meet, truth is purified; by join, all things unfold.
The Ouroboros devours its own tail: its father is definition, its mother convergence.
Herein its power — if it can be observed, it is already real.
Every arc leaves a work order, probes, acceptance evidence, and a story commit. The point is not performative humility. It is making the cost of a disproved claim traceable.
The 1 result claim(s) on this page were executed by oo v0.26.1. Without a receipt, this line does not appear.
The same name once produced one answer when read bare and another through projection. The previous probe asked only whether evolve reported an error; it never observed the path that failed. The repair and the blind probe remain together in the commit.
Read the full story commit →The landing page has made its case. From here, choose what you want to do; unfinished inner pages will not pretend to be documentation.
Install the reference engine and begin by composing two real files.
Five-minute Quick Start →§Syntax, semantics, implementation contracts, and conformance requirements share one code of law.
Open the specification →H*From the whitepaper to the obstruction ladder, with theorem, reduction, and correspondence marked separately.
Enter the research repo →gitStory commits record what each arc believed, which measurement overturned it, and what the correction cost.
Read the history →The specification, engine, and research all form in public on GitHub. Start with a counterexample, a probe, a specification question, or a view none of us has considered.
Bootstrap governance is still converging. GitHub is the physical substrate and the specification is the law; we do not present structures that have not grown yet as finished.