2026-09-08Refocus
From doctrine to perspectives
The project is refocused. ORÆ was written as a doctrine and governance layer — a set of principles intelligence "must honour before it is allowed to become power". That posture claimed an authority this project does not have and never earned, so it is gone.
ORÆ is now what it actually is: an independent project for thinking about AI, its development and its future alongside humanity. Six sections replace the old structure — Vision, Understanding AI, Ecosystem, Paths forward, Horizons, and the method. Governance is still studied; it is no longer a role the project assigns itself.
Concretely: the funding and programme framing is removed (no grants, no foundation, no selection); "what ORÆ refuses / requires" becomes seven directions with their limits and an example each; claims are now marked as documented fact, this project's own reading, or open question; the earlier claim that AI actions are reversible and their reasoning inspectable has been corrected. The old white paper is kept online, labelled as an earlier version. /doctrine and /governance redirect to their successors.
2026-06-12Ecosystem
The application layer becomes OSAIRIS
The two placeholder product layers named a day earlier — Continuity AI and Aivatar — are replaced by a single, real project: OSAIRIS (osairis.ai), a portable identity layer that keeps memory, tone and personality stable across any AI model. It carries the ORÆ ethos directly — user-owned memory, no consciousness claims, no emotional manipulation. The ecosystem page now reads: ORÆ defines the principles; OSAIRIS puts them into practice. In development, private beta.
2026-06-11Pages
The ecosystem mapped, the white paper rebuilt
A new Ecosystem page draws the line between ORÆ — the doctrine and governance layer — and the product work it informs: Continuity AI and Aivatar, both marked in development, not launched. Principles must not depend on the thing they govern. In the same pass, the white paper is rebuilt in the editorial style: a table of contents, seven numbered chapters, a print view. Short and serious, like the rest.
2026-06-10Architecture
A shorter path: ORÆ becomes a portal
The homepage was too long before a visitor could reach anything. ORÆ is now a short portal that opens onto dedicated pages — Doctrine, Governance, Open Intelligence, Genesis — with a contact page reachable in one click. More pages, each shorter, calmer to read. ORÆ is repositioned as the doctrine and governance layer above the product work to come.
2026-06-10Positioning
Positioning sharpened: Open Reasoning. Auditable Evolution.
The program line becomes “Open Reasoning. Auditable Evolution.” ORÆ stays the umbrella mark; the tagline carries the intent. Verified across every page — name, titles and copy.
2026-06-09Design
A golden proportion, felt not stated
The layout adopts φ — le nombre d'or hidden in ORÆ's own name (l'or, gold). Spacing follows the Fibonacci scale; the hero splits 61.8 / 38.2. Felt across the page, named only once — in the console, for the curious.
2026-06-04Detail
The portal goes through
A hidden artwork now opens ThroughPortal.com — the parent project of the work behind ORÆ. The visible object stays a discovery; what it points to is real.
2026-06-03Craft
Square logo for search, and a performance pass
The Organization → logo schema points to a clean square ORÆ logo, picked up by Google Search, iOS home-screen and high-DPI tabs. CSS and JS shipped minified in the same pass; mobile performance moved from 79 to 89 — same content, fewer bytes.
2026-05-31Foundation
or-ae.com — the first permanent address
ORÆ leaves its temporary subdomain. A permanent address makes the project addressable, citeable and durable — a small material commitment that doesn't yet require a corporate form.
2026-05-14Stewardship
Stewardship chosen — pseudonymous on purpose
Architect, Cartographer, Witness. Names disclosed when the work earns the right to be taken at scale. The pseudonym is a decision, not an accident.
2026-05-08Origin
Initial brief written
A founding decision: research and design framework, not product. Responsibility is designed before capability. Nothing larger is attempted before the smallest proof holds.