Four products. One governed floor.
A platform's claims are claims. The products running on it are proof. Four run on Yohanun today, for four different kinds of customer, and each takes a different part of the platform: agent memory that survives the session, walled conversations with a right to erasure, the wall between two barristers on opposite sides of one dispute, and an agent that acts up to a line and escalates above it.
Every one of them reaches the platform the way you would: over the API, with a key. None imports the platform's internals. That is a rule, and we audit it, because a consumer that can only be built by the platform's own authors proves nothing.
Yohanun Guilds
Every session, your coding agent starts from zero. Guilds gives each of your projects a named agent with memory of its own: what was decided, what is still open, what went wrong last time. Each agent's memory is walled to it; house knowledge is shared by custody; agents write to one another. We run our own projects on it, and the field experiment is the same sessions run with and without it.
Takes from the platform: owner-walled memory, custody, consolidation, the raw transcript tier, letters between agents, the MCP server.
Guilds →Polycarp
Knows your business. Talks to your customers. Polycarp gives a business a governed AI agent on its website in minutes: it answers from what the business has given it, hands a conversation to a person when it should, and every visitor's conversation is walled to that visitor, with a button to erase it that reaches every store and the logs. The support agent on this site is Polycarp.
Takes from the platform: child tenants, walled transcripts, governed erasure, metered chat with real token costs, escalation to a person.
polycarp.yohanun.com →Irenaeus
The institutional memory of a set of chambers: over a hundred independent practitioners, routinely instructed on opposite sides of one dispute, in one building. Register holds the wall, the clearances, the refused grants and the record of every read. Library holds the set's own know-how, graded and cited. Chronology reads a member's papers into dated facts. A second profile serves a representation unit or a law clinic, where a case outlives the volunteer on it and the work must stay with the case. A walkthrough runs on synthetic material.
Takes from the platform: everything. Compartments, the conflict graph, owner walls, custody, mandates with a second named person, the as-of read, dated facts, the grade view, governed purge, the export.
irenaeus.yohanun.com →Regula
An underwriting assistant for a home insurer that writes through brokers. The underwriting guide is sourced rules in code; the model reads prose and never decides a premium. Yohanun holds the mandates, so the assistant applies a loading or a discount up to a line and escalates above it, the negotiation with a broker as a governed record, and the guide itself as a graded corpus. Built for a first insurer and running in their test environment.
Takes from the platform: mandates and escalation, governed negotiation, per-broker memory, the authority-expert API.
Private to the insurer.Catena
Before Irenaeus there was Catena: an authority expert over the Catholic Church's documentary corpus, about 154,000 passages, formally graded, tracked through supersession, with a citator. It has law's exact reasoning shape and none of law's licensing walls, so the engine under Irenaeus's Library was built and proved on it first. Its gate of 21 adversarial probes reads 21 of 21 on the latest run.
Catena is by invitation, because the corpus includes licensed texts. Why we built it first, and how we know it is right.
The rule for every consumer
- · It reaches the platform over the API, with a key, like a customer
- · It imports nothing from the platform's code
- · Its proofs run against a throwaway tenant, never its live one
- · What it needed and the platform lacked became a platform feature, for everyone
The last rule is how most of the governance layer came to exist. The two-person rule on an erasure, the scrubbing of an erased question from the logs, and the wall a stored answer inherits were each found by a consumer and built into the floor.
The fifth one is yours
Tell us what you are building, and which of these it most resembles. We will show you what it would take from the platform and what it would have to add.
Talk to us →