From a supplied source towards approved knowledge.
Sets out the steps for supplying, proposing, reviewing and releasing knowledge.
Evidence: The evidence register records current operation and its limitations.
Engine + Packs
The core stays generic. The application becomes specific.
The DyReP Engine (the execution core) carries out the work. A Pack describes how a particular application may run on it.
A Pack is not a bundle of prompts and not a knowledge base.
What a Pack sets out
The professional knowledge keeps coming from the knowledge base.
- which methods exist;
- which inputs and outputs are expected;
- which permitted actions (capabilities) a method needs;
- where human judgement is needed;
- which result forms are allowed;
- which version of the contract applies.
Packs that make the architecture visible now
A professional expert workflow.
Sets out methods and contracts for specialist case-file work, intake, analysis and human judgement.
Evidence: The evidence register records its components and real-world limitations.
Measuring how AI describes an organisation.
Sets out clearly scoped methods for baseline measurement, assessment and repetition.
Evidence: The evidence register records measurement results and the limits on effect.
Why Packs
Without Packs, every new application would have to change the Engine itself.
With Packs, the same core can carry several kinds of work, while method, version and limit stay visible for each application.
A Pack for your organisation
In an implementation, a dedicated Pack or Pack configuration can set out your organisation's specific way of working: methods, requirements, result forms and connections.
We do that only where the application is genuinely specific to your organisation. What turns out to be generic, we do not rebuild for each client.
The result decides whether a Pack is needed.
Start with a result →
Describe one recurring task. That is enough to begin.
View the technical evidence →