DyReP

System and evidence

How DyReP works — and what has been demonstrated.

DyReP consists of components, each with its own task and limit.

Here you see the stable structure. The current status, measurement date and technical source come from the evidence register.

System map

Underlying infrastructure: data, state and storage — in the current implementation partly through Supabase.

  1. ORGANISATION / AI ENVIRONMENT
  2. ↓
  3. GATEWAY / MCP
  4. ↓
  5. ENGINE ← PACK · way of working · contract
  6. ├─ uses KNOWLEDGE BASE
  7. ├─ uses PERMITTED ACTIONS
  8. └─ waits where needed for HUMAN JUDGEMENT
  9. ↓
  10. REPRESENTATION
  11. ↓
  12. RESULT
  13. ↓
  14. RESULT PASSPORT (where needed)
01

DyReP

What is it?
The working layer between your organisation and AI.
What does it do?
For a concrete work request, it brings together knowledge, way of working, permitted actions, human control and the result.
What can be shown?
CurrentGateway and Engine ready
CurrentEngine test suite
CurrentFrom knowledge to proof of execution
CurrentAccess control
From the evidence register · Core and execution →
Limit
DyReP does not automatically make an AI result correct in substance.

As a harness

For work where mistakes carry weight, DyReP can act as a harness: the fixed boundary around AI that determines which knowledge and actions are permitted and where a person has to decide.

02

Knowledge base

What is it?
The managed knowledge that DyReP can use.
What does it do?
Distinguishes the source, its origin and status, proposed content and approved knowledge. It can show which knowledge, publications and representations depend on a source before a change is made.
Short path
Source → proposal → review → approved knowledge → use in the work.
Change impact
If a source changes, the knowledge base can show which statements, publications and result forms depend on it, including indirect dependencies.
What can be shown?
CurrentSource submission via Claude and ChatGPT
CurrentFrom source to reviewed seed batch
CurrentSeparate rights for submission
CurrentRevoking a source
CurrentApproval of knowledge
CandidateChange impact
From the evidence register · Knowledge →
Limit
A stored document is not automatically valid knowledge for every application. Change impact shows the consequences; adjusting or withdrawing remains a human action.
03

Gateway

What is it?
The controlled entry point to DyReP.
What does it do?
Enforces limits on identity, profile, project, method and access to permitted actions.
What can be shown?
CurrentGateway and Engine ready
CurrentEngine test suite
CurrentFrom knowledge to proof of execution
CurrentAccess control
From the evidence register · Core and execution →
Limit
The Gateway connects and limits. It deliberately contains no professional logic.
04

MCP

What is it?
A standard protocol (Model Context Protocol) that lets an AI environment use DyReP tools.
What does it do?
Lets an AI environment find tools, carry out tasks and get status or results back, within the limits of DyReP.
What can be shown?
CurrentClaude / Cowork
CurrentChatGPT / DyReP app
From the evidence register · Connections →
Limit
MCP does not decide which knowledge applies or who may decide. It is the connection, not the control.
05

MCP Apps

What is it?
An interactive DyReP interface inside an AI environment.
What does it do?
It can, for example, show a source submission as a panel next to the conversation.
What can be shown?
CurrentClaude / Cowork
CurrentChatGPT / DyReP app
From the evidence register · Connections →
Limit
A visible panel does not yet prove a complete professional way of working through that AI environment.
06

Engine

What is it?
The execution core of DyReP.
What does it do?
Carries out a method within fixed contracts and limits which actions may be used.
What can be shown?
CurrentGateway and Engine ready
CurrentEngine test suite
CurrentFrom knowledge to proof of execution
CurrentAccess control
From the evidence register · Core and execution →
Limit
The Engine is not the knowledge base, not the user interface and not the human decision-maker.
07

Packs

What are they?
Application modules with a fixed version, on top of the generic Engine.
What do they do?
For each application, they set out methods, schemas, required actions and result forms.
Examples
Seed · Expert · GEO
What can be shown?
CurrentSeed Pack
CurrentExpert Pack
From the evidence register · Packs →
Limit
A Pack is not where professional knowledge is managed.
08

Permitted actions

capabilities

What is it?
What AI and tools may do within DyReP.
What does it do?
For example reading, analysing, storing or calling a connected system, each time only with the right authority.
What can be shown?
CurrentGateway and Engine ready
CurrentEngine test suite
CurrentFrom knowledge to proof of execution
CurrentAccess control
From the evidence register · Core and execution →
Limit
An action that has not been set up cannot be carried out. That says nothing yet about the quality of what is carried out.
09

Human judgement

human review

What is it?
An explicit decision point at which DyReP waits for an authorised person.
What does it do?
Links a professional judgement to the relevant subject, step and authority. The record identifies who made the judgement, when, under which version of the way of working and how long it remains valid.
What can be shown?
CurrentFull real-world workflow
CurrentAnalysis and human judgement
From the evidence register · Expert work →
Limit
Human judgement does not prove that every human decision is correct in substance. An expired judgement is not applied again; it has to be given again.
10

Representation

What is it?
The layer that presents the same applicable foundation in a suitable form.
What does it do?
Produces, for example, an expert view, a client proposal, a decision note or an execution instruction.
Principle
Form, order and detail adapt to the recipient.
What can be shown?
No register entry yet.To the evidence register →
Limit
Representation must not add facts, certainty or authority that are not in the foundation.
11

Result Passport

What is it?
The traceable account of how a result came about.
What can it contain?
  • work request;
  • way of working and its version;
  • knowledge used and its status;
  • human decisions and their validity period;
  • technical references to the execution (run and receipt references).
What can be shown?
No register entry yet.To the evidence register →
Limit
Where a Result Passport is used, it makes it possible to check how a result came about. It does not make the content true by itself.
12

Supabase

What is it?
Part of the current data and storage infrastructure.
What does it do?
In the current implementation it supports, among other things, state, database functions, storage, receipts and migrations.
What can be shown?
CurrentGateway and Engine ready
CurrentEngine test suite
CurrentFrom knowledge to proof of execution
CurrentAccess control
From the evidence register · Core and execution →
Limit
Supabase is current infrastructure, not the definition of DyReP.

Six questions to check

The system map shows where the limits are. These six questions show how DyReP deals with them.

  1. 1.Can unapproved knowledge simply get into a result?

    No. A supplied source is not automatically valid knowledge. DyReP keeps source, status and approved knowledge apart. What of this can be shown is in the register.

  2. 2.Who has the final say?

    Where professional judgement is needed, an authorised person decides. DyReP waits until that judgement has been recorded.

  3. 3.Can I see afterwards what happened?

    Yes, where the application calls for it. The Result Passport brings together the work request, the knowledge used, the way of working and the relevant decisions.

  4. 4.What has actually been measured?

    Demo, test, live connection and real-world use are different levels of evidence. The register keeps them apart.

  5. 5.Where is my data stored and who can access it?

    We agree storage location, access and processing with you in advance, for each First Route and each connection.

  6. 6.What happens when a source changes?

    The knowledge base shows which knowledge, publications and forms rest on that source. An authorised person decides what is adjusted or withdrawn. What of this can be shown is in the register.

View the evidence register with date, source and limit

What complete means

From source to result, without a gap.

Complete means: no step from source to result without provenance, status and judgement. It does not mean everything is already set up for every organisation.

  1. 01SourceCurrent
  2. 02knowledge baseCurrent
  3. 03way of workingCurrent
  4. 04permitted actionsCurrent
  5. 05human judgementCurrent
  6. 06representationCurrent
  7. 07resultCurrent
  8. 08Result PassportCurrent

The limit for each component is set out above; the current status is in the register.

Would you like to test this structure on one result of your own?

Start with a result →

Describe one recurring task. That is enough to begin.