AEO-01Profile passport
Identity and maturity.
Names the profile, source jurisdiction, source state, mapper status, verifier status and claim boundary.
Public evidence layer / regulated acts / machine-readable profiles
Public evidence for machine-readable regulation.
ActProof is a public evidence infrastructure for regulated machine-readable acts.
It turns source text, profile fields, evidence labels, receipts and verification boundaries into inspectable objects, without claiming to certify legal compliance.
In plain words
A new EU rule comes out. Somewhere, a person opens a long PDF, full of articles and sub-paragraphs, and tries to turn it into a simple list of what their company actually has to report. By hand. Or, more and more, with AI. Then the next company does the same thing. And the next. Thousands of people, redoing the same homework, and no two readings can be checked against each other.
ActProof does that work once, in the open. It turns each rule into a plain, machine-readable list: what must be reported, what evidence supports it, who may see it, and how it can be checked later. Every field is tied back to the official source text, with a receipt anyone can check. It does not tell you whether you are compliant. It gives people and software one shared, checkable version of what the rule says.
CatalogueSource-bound profiles
Receipt layerCanonical JSON evidence objects
VerifierLocal hash and profile checks
Next profileNIS2 Article 23 incident reporting
01 / Doctrine
Institutional by being narrower than the market wants.
ActProof does not prove compliance. It proves what a machine-readable profile claims, where it came from, and where judgement entered.
The refusal is the trust mechanism. Provenance, reproducibility, source binding and reviewability are useful because they do not pretend to replace legal judgement.
A public evidence discipline for machine-readable regulation.
The work is deliberately narrow: fewer claims, stronger bindings, no unbounded assertions. Source, profile, judgement and boundary are treated as public objects, each one inspectable on its own terms.
This is not a compliance product. It is an inspection surface for regulated acts as they are converted into machine profiles.
02 / Public object system
Evidence is held as discrete objects.
Each regulated act is expressed as a set of repeatable inspection objects rather than prose. The same objects travel without change: into GitHub, into grant review, into bank implementation workpapers, and into future profile packs.
AEO-02Source bundle
Pinned official artefacts.
Lists the files a profile claims to use, with hashes so reuse can be checked locally.
AEO-03Mapper workpaper
Visible transformation.
Shows how source fragments became operational fields and where interpretation entered.
AEO-04Claim boundary
The refusal layer.
Separates reproducibility from legal approval, compliance, currentness and supervisory acceptance.
AEO-05Canonical receipt
Stable evidence object.
Produces a deterministic record that can be signed, timestamped, anchored and later checked.
AEO-06Challenge record
Public contestability.
Wrong source, unsupported mapping, currentness issue, overclaim or omission: the object can be disputed.
03 / Registry state
Current and near-term regulated act profiles.
This registry records what exists, what is next, and what remains under review. Naming the boundaries of the catalogue is more credible than presenting it as complete.
04 / Chain
From legal source to operational JSON.
The core story is not automation. It is restraint. Public source material is not swallowed by software; the conversion path remains inspectable.
01Official sourcepublic text
02Pinned artefactshashes
03Fragmentscitations
04Profile fieldsJSON
05Receiptcanonical
06Verificationpublic check
05 / Boundary
Every technical claim is bounded.
Compliance systems become dangerous when private interpretation is presented as public truth. ActProof makes the boundary explicit.
This layer can show
- official source artefacts named and hashed
- field provenance, mapper notes and reproducibility
- schema divergence against a public reference profile
- where interpretation entered the machine profile
This layer cannot show
- legal approval or supervisory acceptance
- that a filing, firm or vendor is compliant
- that a mapping is legally complete without review
- that pinned sources are automatically the latest legal state
06 / Adoption bridge
Private schemas can be compared to public evidence.
The practical bridge is a source-bound schema gap report.
RegTech teams, internal compliance groups and implementers can compare their private DORA, NIS2, EUDR or GDPR schema against a public ActProof profile and see what matches, diverges or overclaims.
SCHEMA GAP REPORT reference: eu.dora.major_ict_incident.final_report.v1 compared: vendor_dora_incident_v3.json matched fields: 37 missing source-bound fields: 06 vendor-only fields: 11 interpretation-required: 04 unsupported legal claims: 02 result: review required, not failure
Why this matters
ActProof can be adopted without becoming the system of record.
It can remain a public evidence layer that other tools, vendors and institutions inspect, challenge and build against.
Make machine-readable regulation inspectable before it becomes infrastructure.
Inspect the source chain, run the local check, read the boundary, challenge what looks wrong, or compare a private schema against a source-bound public profile.