Access

Structural access and governance

The normative specification, its implementations and its protocols form an open system available to the scientific and industrial community. This page sets out the scope of application, the underlying licensing models, and the transfer frameworks for commercial use.

Immediate public uses

Independent implementation of the normative contractThe specification is frozen, version-numbered and public. You write your implementation, you run it, you compare a fingerprint: if it matches, it is conformant, and you can demonstrate that to a third party without going through me. This is the primary mode of use, and it requires no agreement.

Available

Replaying a computation identically, years laterAn execution fingerprint attests that a computation ran exactly as stated, without depending on a trusted infrastructure or on particular hardware. Useful wherever an automated decision has to be justified after the fact.

Available

Deciding before execution whether reduced precision is safeA criterion checkable upstream, rather than a trial followed by a comparison. Three of the deposited documents address this question, with their domain of validity and their measured rates.

Deposited

Arbitrating between two implementations that divergeThe structure exports to a standard exchange format of the field, while the normative arithmetic serves as the numerical reference. The bridge is built and passes its conformance tests.

Bridge tested

Licences and conditions

Element	Regime	Access
Normative specification, documents, figures, result sets	CC BY 4.0	Public, unconditional
Code of the public reproduction package	AGPL-3.0	Public, unconditional
Commercial use of the substrate	Separate licence	By agreement
Demonstrator, interfaces, partner documentation	Controlled	By agreement
Plasticity rules, cognitive orchestration, learning parameters	Confidential	Not disclosed

The last row calls for a word of explanation, because the question always comes up. Everything needed to judge a result is public: protocol, frozen data, fingerprints, ablations, declared scope. What stays closed is what would allow the result to be rebuilt identically without having done the work. It is the only genuinely transferable element of this programme, and that is why it is not published.

Why the specification, by contrast, is open

An execution contract is worth something only if others can conform to it. A specification kept secret would serve no one, starting with me: it is because a third party can implement it independently and check its fingerprint that the contract carries evidential value.

Contacting me

For a technical question, a request for a protocol, a commercial use or access under agreement, write to me. This work is done outside working hours, and I sometimes reply a few days late.

Get in touch