An organization can run Konneal as a managed deployment delivered by Ribose, or assemble it from the open-source packages. Both paths start from the assets the organization already owns, and the sections below describe each in turn.
Match your organization to what it already has; the engagement steps are the same for all three profiles.
Metanorma
Your library's clause structure, typed tables and formulas carry the grounded answering surface, held to the gates, with identifiers served through slug codecs until a formal scheme is declared.
Declare the profile, run the annealment passes, deploy under your brand.
+ Pubid+ Relaton+ Glossarist+ Lutaml
Each shape imports into the profile and raises its features: Pubid brings native identifier steering and citation formatting; Relaton brings edition governance and the citation graph; Glossarist brings terminology binding across registers and languages; Lutaml brings served model objects.
The same passes pick each dataset up where it stands.
+ Primmel
The execution plane turns on for every publication family that carries models: verdicts with the standard's own violation wording, counterfactuals, and certificates of absence.
Models join the model plane; the verdict engine serves them.
If your organization does not yet author in Metanorma, the lattice starts at authoring —metanorma.org ↗is where that begins.
Each step is measured, and each outcome — profile, corpus, deployment — belongs to your organization.
01
We fill in the ladder together: what your organization already has, and what each asset already gives your members.
02
Publications, identifiers, terminology, models, thresholds. The profile is a declaration your organization owns.
03
The annealment passes run over your corpus, and the golden suites measure the result against your own documents before anything ships.
04
Your publications, your terminology, your frontend — with the gates running on every change thereafter.
When the corpus is already authored, the path from a blank directory to a serving deployment is four commands. Every file the scaffolder writes is ordinary, reviewable code.
01
npm create @konneal/publisher my-sdo -- --with-site
An interview asks for the publisher's facts — id, name, domains, identity issuer, first dataset — then writes the whole skeleton: profile/*.yaml (the single edit surface), the ten-line worker entry that injects the profile into the engine, the Cloudflare wiring, the profile codegen, and (with --with-site) a minimal Astro+Vue frontend consuming @konneal/client. Every file is ordinary, reviewable code; the scaffolder never runs again.
02
cd my-sdo && npm install && node scripts/gen_profile.mjs
profile/corpora.yaml names the corpus repository; profile/prompts.yaml carries the publisher's voice (identity, refusal, citation examples), so questions about the publisher itself are answered from the profile and never refused. Every profile edit regenerates a committed TypeScript module; a drift test keeps both sides honest.
03
python -m ingest.cli parse && …embed && …graph && …upsert
The engine's Python CLI parses the corpus along its own clause structure, embeds it via the same binding the server uses, builds the graph projection — the registry, the concepts, and the citation edges from the bibliographies — and upserts the Vectorize index. One-time cost, bounded by corpus size.
04
cd site && npm install && npm run build && cd .. && npm run deploy
The frontend's entire answer-contract surface — the SSE ask client, the markdown renderer, citation chips, typed blocks — comes from @konneal/client. What remains is the publisher's own: theme tokens, page chrome, conversation state. Deploy the Worker; it serves site/dist as its assets.
The packages are published to npm under the @konneal scope —@konneal/engine ↗, @konneal/client, @konneal/create-publisher and @konneal/ui-starter — and the sources live atgithub.com/konneal ↗, all BSD-3-Clause.
Konneal is developed and delivered by Ribose Inc. Contact Ribose to arrange a managed deployment for your organization, beginning with the inventory review and the profile declaration.
www.ribose.com ↗The fastest way to understand what a deployment does is to question a live one. Ask it about a clause, ask it for a verdict, and follow a citation into the original document.
ai.oimlsmart.org ↗