AEO-01Profile Passport
Identity and maturity.
Names the profile, source jurisdiction, source state, mapper status, verifier status and legal claim boundary.
Public inspection room online
Machine-readable regulation · source-bound profiles · public claim boundaries
Public law should not become private JSON.
ActProof Events is a public evidence discipline for machine-readable regulation.
It records the path from official source material to operational profiles: what was pinned, what was mapped, where judgement entered, what can be hashed, and what must remain challengeable.
01 / Doctrine
Unignorable 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.
That negative capability is the trust mechanism. The site refuses legal certainty where only provenance, reproducibility and reviewability can be shown.
Somebody has built a public evidence discipline for machine-readable regulation.
The discipline is sterile by design: fewer claims, fewer colours, fewer decorative gestures. Source, profile, judgement and boundary are treated as inspectable public objects.
Every page has one job. Every status colour has one meaning. Every strong claim is paired with a refusal.
02 / Object system
The site is made of evidence objects.
Instead of loose marketing sections, ActProof presents repeatable inspection objects. The same objects can appear on the website, in GitHub, in grant review, and in future profile packs.
AEO-02Source Bundle
Pinned official artefacts.
The source files a profile claims to use, named and hashed so reuse can be checked locally.
AEO-03Mapper Workpaper
Visible transformation.
Shows how source fragments became operational fields and where human judgement entered.
AEO-04Claim Boundary
The refusal layer.
Separates reproducibility and provenance from legal approval, compliance, currentness and supervisory acceptance.
AEO-05Gap Report
Adoption surface.
Compares private schemas with source-bound public profiles without turning ActProof into a closed SaaS platform.
AEO-06Challenge Record
Public contestability.
Wrong source, unsupported mapping, currentness issue, overclaim or omission: every profile can be disputed.
03 / 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
04Actionsobligations
05Profile fieldsJSON
06Judgementreview
07Traceabilityworkpaper
08Verificationreuse
04 / Boundary
Every technical claim is bounded.
Compliance systems become dangerous when they make private interpretation look like 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
05 / Rooms
Enter through evidence, not persuasion.
Each page is a room in the inspection sequence. Catalogue identifies objects. Mapper explains transformation. Verify checks files. Guide and Review make public scrutiny easier.
ROOM-01Catalogue
Inventory.
Which profiles exist, what maturity state they are in, and what can actually be inspected.
Open catalogue →ROOM-02Mapper
Workpaper.
The source-to-profile transformation bench, including interpretation decisions.
Inspect mapper →ROOM-03Verify
Local check.
Hash profile and source artefacts locally. No upload. No backend. No legal approval.
Run verifier →ROOM-04Review
Reviewer path.
A guided route for funders, standards people, implementers and public-interest reviewers.
Start review →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.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.