Trust, shown.
Institutions ask for certifications. We are a young firm and we will earn those in time. Until then, and after, we do something rarer: we show you the actual proofs. Every claim below can be checked by your own engineer against your own room file.
The laws of the system
Your room is one HTML file encrypted with AES-256-GCM. The key is derived from your passphrase with 310,000 rounds of PBKDF2, in your browser. We never see the passphrase, we hold no copy, and there is no recovery door for anyone, including us. This is not a policy. It is arithmetic.
The sealed file: nobody opens it but you. Your working answers: they reach us, your advisor, sealed in transit, and the room shows you this on screen. Everyone else: never. Prefer us blind too? The Silent Room turns the sync off.
The five standard apps and the export are free forever, by law of the system. If we disappeared tomorrow, your room still opens, still computes, and still exports everything. We keep clients by being worth keeping.
Every number the system produces can be recomputed with a pencil from formulas printed inside the room itself. No model computes your score. Nothing that touches your numbers is a black box.
Every realised euro in your ledger is signed by a named person, and cryptographically sealed with a key generated in your own browser that never leaves your machine. A tampered line fails its own verification.
How we prove it to ourselves, daily
The system ships with a battery of automated gates, nearly fifty of them, run before anything moves. They boot a real room and attack it: they plant canary values and prove none appear in anything that leaves; they verify a certificate carries no scores, no seat answers, no evidence text; they prove a room without consent refuses to hand a fund anything beyond the summary; they prove the staging folder cannot carry an internal file even by accident. When a check fails, nothing ships. We would rather show you this list than a badge, because a badge is an audit of last year and a gate is an audit of this morning.
The server’s conduct
The server stores sealed blobs it cannot read, never writes over a client’s data folder, and serves rooms only by exact name. Sync payloads are encrypted before they leave your browser. There is no analytics inside any room, no third-party script, no call to anyone but us.
The evaluation terms
Some rooms are issued before a mandate exists: the starter room from the wizard, and the demonstration rooms we send to prospects. Those copies are governed by four short terms, stated here in full because a term that hides in small print is not a term.
An evaluation copy is issued to the company named at issue, for that company’s own evaluation of the instrument, and for nothing else. It may be read by the company’s officers and advisers. Reverse engineering, systematic extraction, republication and competitive analysis are not licensed, and passing a copy onward does not carry the licence with it.
The KPI atlas, the benchmark tables and the calibration data inside the full room are databases in which Makers of New has made a substantial investment of collection, verification and presentation. They are protected by the sui generis database right of Directive 96/9/EC across the European Union, alongside copyright in the surrounding work. Extraction or re-utilisation of a substantial part, by hand or by machine, is an infringement of that right independent of any contract.
Issued copies are individually marked. Each evaluation room carries an issuance mark, recorded in our log against the request that produced it, and the mark survives copying. If a copy of our work surfaces where it should not be, we can read the mark and name the issuance it left with. This is stated openly: a mark you have been told about is a fence. It is not a trap.
All rights not expressly granted are reserved. Clients under mandate hold their rooms under their engagement letter, not under these terms; nothing here narrows what a paying client receives, and nothing here limits rights a client has by law.
The certificate, as a standard anyone may implement
The certificate is an interoperability standard that happens to be sold inside a product, and a standard nobody else can implement is a file format with ambitions. So the specification is published here and anyone may build against it, including people who compete with us. That is not generosity: a standard is worth something exactly in proportion to how many parties require it, and a party that requires it is worth more to us than a party that admires it.
A signed JSON record carrying forty named fields, all of them company-level aggregates, names, counts, bands, flags or dates. No per-question score, no seat answer, no evidence text, no turnover or EBITDA as figures. The field list, the plain-English label for each one and the seven categories that may never appear are readable inside every room, on the page that shows a company what crosses.
A hash chain back to a genesis, a kernel version stamp, the quarter it closed, and a signature. A receiving system can verify a certificate offline with no call to us: that is the whole point of the design and it is the property a standard needs to survive its author.
Two things, both narrow. Do not call something a MakersOS certificate if it carries a field the contract forbids, because the value of the object is what it refuses. And do not present a figure derived from one as though it came from the published model unless it did. Beyond that, build what you like, charge what you like, and compete with us using it.
The field list, the validation rules and a worked example are available on request today, by email, from a person. There is no portal and no developer site, because two implementers do not need one and pretending otherwise would be the most obvious kind of theatre. When there are five, there will be a page.
The measure that matters here is not downloads. It is whether anybody who is not us ever requires a certificate: a fund asking its portfolio for one, an adviser making it a condition, a lender accepting it. Until that happens this is a well-specified file, and we will say so.
Our own record, kept the way we ask you to keep yours
This instrument asks a management team to write down what a move will be worth before making it, and then to keep the miss beside the hit for as long as they hold the company. It would be an odd thing to ask and not do. The same ledger is kept here, in public, and it opens honestly: it is empty of outcomes today. Predictions signed under mandate since the kernel froze on 16.08.2026 are the first entries, and the earliest cannot land until a quarter closes. A record that arrived pre-filled would tell you only that somebody wrote it backwards.
Every prediction we sign for a client, with the euro figure, the date and the quarter it is expected to land in. When that quarter closes the landed figure goes beside it and the difference is classified the same three ways the rooms use: execution gap, model error or external shock. Model error is the one that matters to you, because it is the only category that says the instrument was wrong and the world was fine.
Nothing is removed once entered, including the entries that would be more comfortable gone. A prediction that succeeded does not drop out for being old news, and one that missed does not get re-dated forward until it looks better. Both are how a track record becomes a brochure, and the second is written into our own engineering notes as a defect to guard against, because we made it once internally and caught it.
No client is named without a signature saying we may. The euro figures, the dates and the classifications stand on their own; a record that needs a logo to be believed is not a record.
First publication is due at the close of the first mandated quarter under the frozen kernel. Until then this section says what it will contain and shows nothing, which is the only honest state for a ledger with no closed quarters in it.
Whether a room stays a single file, decided
A sealed file that runs with the network unplugged removes the largest objection procurement has, and it caps the one thing that compounds, because a hosted fleet learns from every room and a file learns from none. Both are true, and leaving the tension undecided means it gets decided by default, badly, one feature at a time.
The room stays a single sealed file, and that is not provisional. What a client receives opens with no server, no account and no network, and it will keep working the day we stop trading. Nothing on the roadmap may require a connection for a room to compute, and any surface that would has to degrade to the file.
The learning arrives through the certificate. The room stays shut. A certificate carries aggregates a company consented to send, never answers. It is slower than telemetry and it is the only version a management team opts into honestly, which makes it the only version worth having.
Reviewed on 28.02.2027, at the close of the second mandated quarter, against one question: has any client asked for something a sealed file genuinely cannot do. If the answer is still no, the decision stands another year. A decision without a review date is a habit.
What we do not have yet, said plainly
No SOC2, no ISO 27001, not yet. We are one firm in Luxembourg with a small fleet and a published architecture, and certifications will follow the fleet. If your procurement needs more today, we will walk your security team through the room file line by line, in person. So far, nobody has finished that walk unconvinced.
The mechanism, end to end
The same fourteen dimensions and the same published arithmetic run through every stage. What changes is the verb: and where your data lives. Free tools store on your device, never with us; the paid instruments live on your record, synced only through the operator’s judgment.
Fourteen questions, sixty seconds, free. Your answers become your baseline.
Never asks again: every lever starts where your answers left it, each tagged yours. Price a decision before making it.
Ten business days with management: the fourteen per seat, plus the three maturity scans, digital & data, culture, cyber, thirty-six anchored questions: returning the Confidence-to-Invest index. Every ASSUMPTION becomes a measurement.
Your private instrument: the staircase, the value tree, the program, every answer priced, synced only through the operator, re-issued each quarter. Numbers age and expire; predictions are registered before outcomes.
asks → moves → measures → commits · one kernel · the model published at makersofnew.com/model · nothing asked twice, nothing stored without consent, sealed end to end, certified at every release