Ormature
The refusal is the Charter's, not the model's.
Most organisations already have the rules. They are in kickoff notes, in a programme office's standing instructions, in the email where somebody finally said what "gate" means here. What they do not have is one place those declarations live, inherit, and get checked against. So a project reports a budget nobody tracks, an operating company keeps its own calendar, and the contradiction is found in a review six months later — if at all.
Ormature reads the material an element is opened from, proposes what it declares, and lets a person confirm it key by key. From then on the organisation is held to it.
What it does
- Intake from material — a brief, a set of notes, an email: the model proposes the rules, fields and open questions the material contains, quoting the passage each rests on. A proposal that quotes nothing is refused. Nothing is declared until someone confirms it.
- A Charter that inherits — every element takes what is declared above it and overrides only where it says so. What is in force at any element, and who declared it, is shown, not inferred.
- Updates checked against it — a staff update that states something the Charter does not track is refused by the Charter, not by the model, and forwarded as an ask to whoever owns that declaration. A decline is remembered; the same ask comes back as a pushback or a reconsideration, never as a fresh question.
- Governance as the organisation's own data — who may open a project, who may decide, and how far a leader's reach goes are declared by the organisation. Two seeded organisations run two different policies through the same code, and an audit names the gaps.
- Every model call metered — priced under the rate card it was made under, attributed to the element and purpose that claimed it, and shown beside the measured figures for each unit and model.
Why it is not embedded on this page
Ormature is something an organisation runs, not a tool you call once. A session is a structure being built up, a queue being cleared, a Charter changing shape under decisions — across many screens and many calls. Each visitor gets a private sandbox in Ormature's own database, with its own AI spend cap and a guided tour through two organisations. That does not fit in a panel, and it does not fit the SkillEra token model — so it runs on its own site, behind a password.
Access
Invite only while it is in prototype. If you run a programme office, a portfolio, or an organisation where the rules live in too many places — or you build governance tooling and want to argue with its assumptions — ask for access and say a little about what you would put through it. The password comes with the invitation. The prototype is seeded with two organisations and a ten-stop guided tour, so there is something to do from the first screen.