Software sources · Map · 19 October 2026
Repositories
Seven public repositories, read on 19 October 2026. One of them, this one, was empty on that date. The others are not seven copies of the same software: doctrine, standard, runtime, and schemas did not share the same age or the same authority.
Sources and reading context
trees cloned on 19 October 2026; namespace policy v2
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
| Repository | Role | Marker that was read | Open first |
|---|---|---|---|
| tenir_governance | Active runtime. Membrane, budget, backends, ledger, composition. | pyproject.toml 5.6.1; changelog: not a publication. Commit of 19 October 2026. Apache-2.0. Beta classifier. |
CHANGELOG, README |
| reg-conformance | Suite and texts of the REG standard. Neutral as to mechanism. | Commit of 19 October 2026, message v0.5.0. Apache-2.0. | README, spec.md, RFCs |
| tenir-conformance-s1-g1 | S1 G0+G1 laboratory harness. Not a production validation. | Version 0.1.0. No LICENSE file in the cloned tree. | README, STATUS, G0 S1 |
| tenir-governance | Snapshot of the R5 line. Default branch master. |
Version 5.0.0, commit of 18 July 2026: IronOmega R5 baseline. Apache-2.0. | README |
| tenir-gov | Same family, described on GitHub as IronOmega 5.0.0. | Version 5.0.0, 29 June 2026. Apache-2.0. Code under r5_hardened/IRON_OMEGA_R5. |
README |
| tenir-schemas | JSON Schema and OpenAPI bundle for an analysis engine, February 2026. | v1.0.0. Some schemas are stubs. No LICENSE in the cloned tree. The $id values point at skiredj-prog.github.io, which was empty on the date of this reading. |
index, OpenAPI |
| skiredj-prog.github.io | GitHub Pages target. Empty at the reading of 19 October 2026. That is no longer the state of the repository. | No files on that date. | This site’s README explains how to publish the build there. |
How they fit
KB3 does not live in these repositories. It is the enacted doctrinal rendering line, a document layer outside the code. The runtime should align to it; it does not constitute it. Specialized services or applications wrap or extend KB3 and must not redefine it. KB2 is the prior rendering line, for continuity. The namespace policy remains the versioning note. None of those texts is “the” meaning carried by the code, and this page names no path as a KB3 module. reg-conformance carries the standard and the suite. tenir_governance is the most recent runtime of the IronOmega / 5.x line. The tenir-gov and tenir-governance repositories are earlier states of that line, not forks of a different product: the second was initialised, on 18 July 2026, as the v5.0.0-IronOmega-R5 baseline. The S1 harness tests operational definitions against a laboratory membrane; it may call the scoring engine without certifying the runtime. tenir-schemas is earlier: its TauResult carries a distance, an epsilon, and a continuity status of OK, FRAGILIZED, or BROKEN. That is not the TAU bundle carried from the prior rendering line, nor the manuscript’s Autonomous Unit. The statuses OK, FRAGILIZED, and BROKEN are not the postures NORMAL, CAUTION, and HOLDING-FIRST.
Author named in the pyproject.toml files and the citations: Abdelaziz Skiredj. Public email for this site: skiredj@tenirlabs.cc. The affiliation “TENIR Labs” and ORCID 0009-0003-2678-4069 appear in the CITATION.cff of tenir_governance. The DOIs written there do not all agree with the README or with the package version. See the Status page before citing an identifier.