Policy v2 · 4 April 2026
Versions
A platform version does not replace a doctrinal version. No profile, product, or extension imitates a canonical line.
Sources and reading context
TENIR Versioning, Namespace and Governed Extension Policy v2; KB3, status note of 14 April 2026; KB2, artifact 00, prior rendering line
Simplified public rendering, read on 19 October 2026. KB3: enacted, active doctrinal rendering line. It renders meaning; it is not the code, and not a constitution. KB2: prior rendering line. This site certifies no implementation. Read the detailed status →
On this page
The note of 4 April 2026 is active. It supersedes the earlier naming policy where developer surfaces were not yet named. It protects semantic integrity across canon, knowledge base, profiles, platform, products, and the developer ecosystem.
Namespaces
| Namespace | Reserved for | Given examples |
|---|---|---|
| Canon | Constitutional framework versions | TENIR 2.0, later TENIR 2.1 |
| Knowledge base | Document rendering, outside the code | KB1.1, historical; KB2, prior line; KB3, enacted and active |
| Profiles and modules | Specialised doctrine that does not replace the canon | Agentic governance, metabolic, rhizomatic, each v1.0 in the examples |
| Platform | Implementation releases | K+4 RC, TENIR2C |
| Products | User-facing surfaces | Lens / Studio, Engine API, Governance, Reports |
| Developer Platform | Ecosystem contracts | Contract Registry, portal, sandbox, kits |
| Partner extension | Third-party integrations under explicit governance | Named examples: UM6P bundle connector, governance export bridge |
Prohibitions
- No overlay, module, profile, product, developer surface, or partner extension imitates a canonical version line.
- No public API or portal implies semantic authority it does not hold.
- No extension suppresses, where relevant, the compliance class, the active profile, the contract version, or authority limits.
A change of definition, equation, posture semantics, collapse logic, hierarchy, stage order, ethical policy, or constitutional scope requires a major canon bump. The prior rendering line specifies that ethical policy means the binding rules of truth, provenance, non-manipulation, transparency, do-no-harm posture, and responsibility. KB3 does not redefine that list. A change that would touch posture semantics, the authority hierarchy, determinant logic, minimum required outputs, or profile boundaries is not a rendering patch: it is escalated.
The Developer Platform follows contract semver: major when a public contract breaks, minor when it extends without breaking, patch for a clarification. A silent break is prohibited. A deprecation window must be published.
Historical resolution
| Label | Treatment |
|---|---|
| v1.x | Canon history, legacy |
| KB1.1 | Historical rendering |
| KB2 | Prior rendering line. Continuity only. Not active. |
| KB3 | Enacted, active doctrinal rendering line, the owner’s declaration of 19 October 2026. No signed record in the files provided. Not a canon version, and not a code module. |
| Informal “v3” | Deprecated as a canonical reference. Became a profile. |
| K+4 RC | Implementation line. Chassis, not semantic sovereignty. |
| TENIR2C | Review branch / platform line |
| IronOmega, 5.0.0 through 5.6.x | Names of the code line in the repositories. They belong to the platform namespace. They are not TENIR 2.0. |
Compliance classes named by the prior rendering line, kept because KB3 requires them to stay visible and does not rename them: Canonical 2.0, Legacy processable, Profile-governed, Simplified public-facing, Illustrative only. This site is simplified public-facing. The architecture drawing, the control-plane demo, and the interactive walkthrough are illustrative only. KB3 is not the Canonical 2.0 class: it is the enacted, active doctrinal rendering line, outside the code. Enactment is the owner’s declaration of 19 October 2026. The files provided with that declaration contain no signed record under 00_GOVERNANCE/04_DECISIONS_AND_RATIFICATIONS. KB2 is no longer an active rendering line.
Specialized services and applications wrap or extend KB3. They build on that line and must not redefine it: no new posture vocabulary, no authority they do not hold, no version line that imitates the canon. TENIR-Gov, in the platform namespace, the IronOmega line, is an implementation that should align to KB3. It is not KB3, and this page points at no source file as a KB3 module.
What the repositories are entitled to say
Every exposed surface should declare, where relevant, the doctrinal or spec version, the product version, the contract version, the compliance class, the active profiles, and the authority it does or does not carry. The files that were read do not all do this. The pyproject.toml of tenir_governance says 5.6.1. The changelog says that entry is not a publication and that a PyPI package must not be inferred from it for 5.6.1. The published package is 5.6.0. CITATION.cff and .zenodo.json still carry 5.5.0, and the citation points at the hyphenated repository. The README of the same tree still describes an earlier line and a test count that is no longer the 5.6.0 changelog’s count. Two SSRN working papers are listed on the Publications page: TENIR-Gov: A Constitutional Membrane Architecture for Governance Homeostasis in AI-Enabled Operational Systems and Tenir: A Counter-Pressure Architecture for Safe Agentic AI Under Irreversible Constraint. They are not platform versions, and they are not KB3.
The prior rendering line also names a portfolio: Lens as a reading instrument, Engine API as a traceable diagnostic core, Governance as a control plane, an agentic profile, and an institutional programme in which UM6P is cited as a possible setting for pilots. The designated reading case is the public Anthropic Economic Index corpus. Nothing in the cloned repositories records a deployment, an agreement, or an endorsement by those third parties. The February 2026 schemas describe an analysis API whose hosts are examples (api.tenir.example.com).