Regulatory knowledge layer
SempliGo
Regulation, finally organized to be understood. And put to use.
A knowledge base that collects, qualifies, and maintains rules, technical standards, and authoritative sources over time. Not a document archive: a verifiable layer that preserves origin, context, time, relationships, and evidence.
- What applies
- Why it applies
- When it changes
Rule A · 6 dimensions
Illustrative- Source
- Authority
- Context
- Time
- Relationships
- Evidence
01The problem
The problem isn’t finding the law.
It’s knowing which rule matters.
For whom, under what conditions, at what point in time. Every business operates within regulations, decrees, technical standards, guidelines, and sector-specific provisions that change and overlap.
- 01Which source takes precedence?
- 02Which entity does it apply to?
- 03Which version was in force?
- 04What evidence is required?
- 05What changes when the context changes?
Documents
Static, scattered sources
Conflicts
Overlaps and precedence
Silos
Different vocabularies across legal, compliance, and IT
Time
Amendments and transitions
From documents to usable knowledge
- Document
- Qualify
- Context
- Links
- Verify
- Use
02Anatomy of a rule
Six dimensions.
One requirement.
A rule taken out of context can lead to the wrong conclusions. SempliGo treats every requirement as a knowledge object: what it says, where it comes from, how much weight it carries, whom it applies to, when it applies, what it connects to, and how compliance is demonstrated.
Article 12 · Obligations
04As of the date of application, 03providers of systems in the specified category that exceed the applicable size threshold 02shall 06retain the technical documentation and make it available upon request, 05in accordance with Article 9 and the related technical standard.
Select a highlighted passage or a dimension to see how SempliGo qualifies it.
03 / CONTEXT
Context
Who and what does it apply to?
Defines the scope: role, sector, company size, activity, data processed, and conditions of applicability.
- Ontology property
- scope_predicates · organizational_filters
- Example structure
- Entity · sector · size · activity · threshold
03Temporal intelligence
Rules change.
History shouldn’t disappear.
An audit of a past decision must be able to reconstruct the framework in force at that moment. A new version does not erase the previous one. Move the slider.
Decision made here → which rule applied at that moment?
2026 · RULE STATUS
Applicable
The rule can be assessed against the entity and the moment of the decision.
04Relationships
No rule
stands alone.
Rules, technical standards, exemptions, amendments, and cross-references form a network. SempliGo makes those relationships explicit instead of leaving them buried in separate documents.
Primary legislation
Rule A
SempliGo graph
relationships · precedence · time
- Standard BTechnical standard
- Guide CGuideline
- Rule DAmendment
- 01
Read
Authentic sources and metadata
- 02
Understand
Requirements, conditions, thresholds
- 03
Structure
6-dimension matrix and relationships
- 04
Verify
Provenance, time, evidence
- 05
Use
Discovery, audits, professional systems
Readable by people. Readable by systems.
SempliGo users don’t need to know anything about ontologies or formats. Beneath the surface, however, the same knowledge retains properties, relationships, time windows, and verifiable references.
Requirement · Rule A
IllustrativeRetain technical documentation
- Applies to
- Providers in the specified category, above threshold
- Weight
- Binding obligation
- Status today
- Applicable
- Linked to
- Article 9 · technical standard
- Source
- Official text, verified version
- How it is demonstrated
- Documentation available upon request
05SempliGo × IRIS Discovery
Knowledge meets
organizational context.
SempliGo is the regulatory matrix IRIS Discovery runs on: EU, national, and regional sources, kept up to date. Discovery models the organization; SempliGo states what the rules require.
What the organization is
IRIS Discovery
Processes, roles, systems, flows, assets, and evidence.
What the rules require
SempliGo
Source, authority, context, time, relationships, and evidence.
- What applies
- Why it applies
- What evidence is required
- What changes next
06Trust and principles
A plausible answer
is not enough.
In regulated environments, you must be able to trace back to the source, reconstruct the timeline, and show the evidence that supports the conclusion.
Source certainty
Every requirement stays linked to its authoritative source and its provenance.
Temporal precision
You know which regulatory state was relevant at the moment in question.
Chain of evidence
Requirement, citation, and evidence stay linked in a verifiable record.
Five rules for regulatory knowledge
- 01
Source first
Knowledge must always be traceable to its origin.
- 02
Context first, then the answer
Applicability comes before the conclusion.
- 03
Time matters
Regulatory validity is a temporal property.
- 04
Evidence, not assumptions
A conclusion must be able to show what supports it.
- 05
Human authority
Technology prepares knowledge and verifiability; professional authority remains human.
Future direction
A knowledge base for professional AI.
SempliGo can become the reference layer for future business and legal advisory systems: systems that start not from generic knowledge, but from approved, contextualized, and verifiable sources.
This is a development direction for the project, not a promise of autonomous decision-making.
The rules already exist. SempliGo makes them computable.
Not to replace professional interpretation, but to give people and systems a regulatory foundation that is structured, contextual, time-aware, and verifiable.