TENIR Labs · Portfolio
REG+ & RFCs · Contracts and foundations
On this page
Framework and research
Under which conditions does a guarantee hold?
A stated guarantee does not yet tell us which configuration supports it or which tests can verify it.
- What you receive
- Specification and candidate profiles, attributable test outcomes and known gaps.
Explanation or demonstration on this site.
AVAILABLE RESOURCERead the REG standard
Open resource ↗Reference contracts, not deployment conformance
See whether it fits your situation
- This may help when…
- When checking an invariant, profile, test or the deployment conditions a guarantee depends on.
- What you need to start
- Versioned contract, assumptions/profile, implementation commit, manifest and applicable test evidence.
- What is examined
- RFC-0 to RFC-7, REG+ profiles, configuration compatibility, evidence contracts and scoped tests.
- The starting question
- A stated guarantee does not yet tell us which configuration supports it or which tests can verify it.
- How it connects to other approaches
- Supports Translation, Mediation, REG-ARCH and TENIR-Gov; released REG Conformance v0.6.1 has a separate product profile.
- Availability and maturity
- Public active repositories; catalogue reports 144 configurations, 42 structurally admissible—not demonstrated effective guarantees.
- Limits to keep in mind
- Structural admissibility is not effective conformance; lab tests are not certification; deployments require manifests.
- A possible next step
- Inspect versioned RFCs, profiles and test artifacts before drawing a conclusion.
Read sources and version references
Availability and limits above reflect the cited sources. Unverified artifact revisions remain identified.