Contact · first conversation
Contact
A question, an idea to explore or something that remains unclear? You can write to us from there.
You are writing to Abdelaziz Skiredj
What would you like to clarify?
An idea still taking shape, a technical question or an uncertain outcome: start in your own words. A few lines are enough.
Author references and citations
Abdelaziz Skiredj. Affiliation written in the runtime citation: TENIR Labs. Public email for this site: skiredj@tenirlabs.cc. ORCID: 0009-0003-2678-4069. Code: github.com/skiredj-prog.
Cite
For the working paper “Governing the Unobserved”, the RELEASES file asks for the version DOI when a precise text matters, and the concept DOI for the latest version. Version 7.1: 10.5281/zenodo.23314839. Concept: 10.5281/zenodo.23270928. The paper’s status is a working paper with bounded empirical evidence. It should not be cited as a certification.
For the software, identifiers diverge in the tree of 19 October 2026. The README and pyproject.toml of tenir_governance display 10.5281/zenodo.21277138. CITATION.cff in the same tree says version 5.5.0, DOI 10.5281/zenodo.21264803, and a hyphenated repository URL. tenir-gov cites 10.5281/zenodo.10823456 for 5.0.0. tenir-governance cites 10.5281/zenodo.21268929. Until those files agree, cite the repository, the commit, and the file the identifier came from.
Cercle Inverse, apart
Cercle Inverse — Vision & Structure Document v1.1, by the same author — describes an intellectual and human ecosystem: crossing complexity, crises, and reconstructions. Its mission is written there on three axes: rebuild, clarify, transmit. Its pillars — anchoring, Project Phoenix, Strategist-Architect, cycle — and its Studio and Foundation entities are not TENIR components, and they are not repositories on this map. The genesis narrative kept by the prior rendering line crosses the name at the moment when “Phoenix” is no longer enough. That crossing explains an origin. It does not import the vision into the canon, nor into KB3.
An independent specification
“Independent architecture — Value trajectories and passage control”, specification v2 of 2 October 2026, says so in its opening: it depends neither on a TENIR-Gov engine, nor on a score formula, nor on CES states, nor on a ledger type. Its object is a value trajectory across authority domains, and a passage as the decision unit at the boundary. In its own vocabulary it replaces “Realm” with “authority domain”. It can be read beside REG. It is not a chapter of REG, and adapters toward TENIR-Gov are a later possibility there, not a definition.
Those two documents are not in the public repositories cloned for this site. They are cited because they were provided as authorial sources.
This site
To report a misreading: the email above, or an issue on the repository concerned. A correction of definition is not a silent edit of this site, and not a change to the runtime. KB3 is the enacted rendering line; it renders meaning and does not create it. It is not a new constitution, and it is not in the code. A change that touches posture, the authority hierarchy, or scope belongs to a governance act, not to this page. The enactment is set out on the Status page.