DyReP
System and evidence

Evidence register · live

What can be shown. With date and limit.

This page shows the current measurement status of DyReP. Other pages refer to it instead of stating a status themselves.

Current
17
measurement within the agreed shelf life
Expired
0
re-measurement needed
Not yet measured
0
no valid source or measurement
Candidate
1
built or prepared, but not yet confirmed as current operation

Per evidence entry

Component
The public name of the system component.
Claim
Exactly what has been shown.
Measured on
Date and time of the observation.
Coverage
For example test environment, test case file, production connection or real working situation.
Source
A readable source name, for example DyReP Gateway production measurement or DyReP release decision · 25 September 2026.
Limitation
What the measurement does not establish.

Core and execution

DyReP · Engine · Gateway · current operation · access control
Gateway and Engine readyCURRENT
source status
live reading · valid for 24 hours
measured on
· 1 hour old
coverage
production environment · catalogue active · bindings on the expected build
source
DyReP Gateway production measurement

Measured on via gateway.dyrep.org/gereed: catalogue 1.22.0 active, as the only active catalogue, 14 bindings on the expected build. This is a snapshot, not a continuous reading; 24 hours after the measurement it counts as out of date.

Snapshot, not a continuous reading.

Engine test suiteCURRENT
source status
local suite run · valid for 14 days
measured on
· 22 hours old
coverage
817 of 822 passed · 0 failed · 5 skipped · engine 159c469 (Gateway pin)
source
Full engine test suite, 30 September 2026

A passing suite proves the tested cases, not production use.

From knowledge to proof of executionCURRENT
source status
live in production, synthetic pilot object · valid for 30 days
measured on
· 1 hour old
coverage
approved knowledge → Pack → Engine → two different results from one permitted knowledge state, each with its own recorded proof of execution → read back and recomputed → a later knowledge change does not silently alter earlier results · independently reviewed
source
Golden Witness in production, 1 October 2026

Synthetic pilot object. Revoking a session has only been shown in a test environment, not in production. A source change does not yet signal earlier results, and the knowledge does not yet contain interdependencies.

Access controlCURRENT
source status
test case file · valid for 30 days
measured on
· 17 days old
coverage
read with own identity allowed · other identity refused · second identical request no second execution · read done in 5.7 s
source
DyReP access measurement · 14 September 2026

Proves this one read and the access control, not a complete client workflow.

Knowledge

Knowledge base · source submission · admission · approval · validity period of the judgement · change impact · snapshot
Source submission via Claude and ChatGPTCURRENT
source status
live, test files · valid for 30 days
measured on
· 2 days old
coverage
file through the submission window in Claude or ChatGPT → straight to storage, not through the model → virus scan → registered as a source, with a source hash equal to the hash the window declared
source
Control measurement of source submission, 28 September 2026

Submitting and registering is not inclusion in or approval of the knowledge. The ChatGPT model does not send files itself; the submission window does. Test files.

From source to reviewed seed batchCURRENT
source status
live, synthetic test source · valid for 30 days
measured on
· 2 days old
coverage
submitted with a dedicated submission login → seed by the operator → human review per candidate (13 of 13 rejected) → batch confirmed → task completed, 0 included · also from ChatGPT: operator starts the seed, 3 of 3 rejected, receipt
source
Control measurement seed route, 28 September 2026

Proves the route and the human review, not inclusion of knowledge. One synthetic test source.

Separate rights for submissionCURRENT
source status
live, test accounts · valid for 30 days
measured on
· 2 days old
coverage
a dedicated submission account only submits sources · seeding and review are done by another account · the submission account has never started a seed task
source
Control measurement of accounts and tasks, 28 September 2026; knowledge intake evidence record in the canon

All accounts see the same tools; the server decides per call. Refusals for the expert account are proven in tests only. No production authority.

Revoking a sourceCURRENT
source status
live, test source · valid for 30 days
measured on
· 2 days old
coverage
a registered source revoked · with time and the reason in the person's own words · the registration is kept
source
Control measurement of source registration, 28 September 2026

Revoking takes a source out of use; it does not correct knowledge that has already been included. One test source.

Approval of knowledgeCURRENT
source status
live, synthetic data · valid for 30 days
measured on
· 6 days old
coverage
from under review to approved only through a recorded human decision · evidence entry · closed execution with a traceable record · an expired decision is not applied
source
DyReP closure evidence knowledge approval, 25 September 2026

Synthetic data; no production authority.

Change impactCANDIDATE
source status
function present · valid for 30 days
coverage
dependencies of a source across several steps

Candidate until a measurement with a source has been designated.

No designated source: this entry cannot carry a status.

Packs

Seed · Expert · GEO
Seed PackCURRENT
source status
live, synthetic data · valid for 30 days
measured on
· 7 days old
coverage
source → candidate → human admission decision → recorded entry under review, with origin and evidence entry
source
DyReP Witness B, 23 September 2026

Admission is not approval of the knowledge. Synthetic data; no production authority.

Expert PackCURRENT
source status
live, synthetic real-world measurement · valid for 30 days
measured on
· 0 hours old
coverage
case creation · document processing · source validation · intake · analysis · human judgement on exactly one result version · governed representation · result + Result Passport, executed within one continuous synthetic workflow
source
Full real-world workflow closure evidence, 1 October 2026

Proves that the Expert Pack methods can be executed together in this synthetic workflow. No real client data and no substantive validation of a financial, legal or financing judgement.

Connections

Claude/Cowork · ChatGPT/DyReP app · other connected environments
Claude / CoworkCURRENT
source status
live, test case file · valid for 30 days
measured on
· 19 days old
coverage
intake · analysis · judgement · create case file · submit document
source
Expert Pack partial trials, 9–12 September 2026

Says nothing about whether the professional method is correct.

ChatGPT / DyReP appCURRENT
source status
live, trial profile · valid for 30 days
measured on
· 4 days old
coverage
OAuth client DyReP – ChatGPT · 261 successful tasks since 17 September 2026, each with a receipt in the gateway:production chain
source
DyReP control measurement of ChatGPT calls · 26 September 2026

Synthetic trial data in a trial profile: proves call, identity and receipt, not production use with real client data.

Expert work

Case file · intake · analysis · human judgement · full real-world workflow
Full real-world workflowCURRENT
source status
live, synthetic real-world measurement · valid for 30 days
measured on
· 0 hours old
coverage
one new synthetic case file through case creation → multi-file upload with type gate → extraction → human extraction review → intake → analysis → human judgement on exactly one result version → governed representation → result + Result Passport; lineage via analysis → review → representation
source
Full real-world workflow closure evidence · 1 October 2026

Synthetic case file; no real client data and no financial, legal or financing judgement. For this trial, representation lineage is proven through the exact analysis result → human review → receipt predecessor; direct binding to case-file extractions is not a criterion of this trial.

Analysis and human judgementCURRENT
source status
live, synthetic test case file · valid for 30 days
measured on
· 19 hours old
coverage
three source files read → each source validated by a person → analysis in three versions → human judgement bound to exactly one version (revised twice, then accepted) → earlier versions and judgements are kept; unknown data stays unknown
source
Control measurement expert case file, 30 September 2026

Synthetic test case file; not a real-world measurement and not a financial, legal or financing judgement. A governed representation result, including product and Result Passport, can now be read live through the Gateway; the separate full real-world workflow was measured in PW-001.

Website

Contact · public measurement layer · representation
ContactCURRENT
source status
production · valid for 30 days
measured on
· 3 days old
coverage
NL 14-09 · EN 24-09 · one submission on repetition · storage in the EU 28-09
source
Production measurement contact form with storage in the EU, 28 September 2026

Proves receipt and storage in the EU; not the handling of replies by email.

GEO

Baseline measurement · diagnosis · any re-measurements
Baseline measurementCURRENT
source status
live baseline measurement · valid for 30 days
measured on
· 23 days old
coverage
36 answers · ChatGPT, Google AI Mode, Perplexity
source
GEO baseline measurement, 8 September 2026

A baseline measurement is not a measurement of effect.

Ground rules

  1. 01

    No source, no status.

    An entry without a designated evidence source is marked Not yet measured.

  2. 02

    Measurements can expire.

    A snapshot does not remain current simply because it was accurate when recorded. The register entry shows when re-measurement is needed.

  3. 03

    A test stays a test.

    A test case file does not become a real client case through wording.

  4. 04

    One green entry proves only that entry.

    It does not establish client deployment, routine use or market impact unless those have been measured explicitly.

Test DyReP on one real result.

Start with a result →

Describe one recurring task. That is enough to begin.