PR-01Source primacy
The source stays above the schema.
Profiles remain subordinate to official source material. The profile is a derived object, not the law.
Principles / Refusals / Public-rule discipline
Evidence before certainty.
A machine-readable rule profile is only trustworthy when its source chain and judgement points remain visible.
ActProof is designed around a narrow public role: make profile provenance inspectable, reproducible and challengeable. It does not replace legal judgement.
01 / Doctrine
The public-rule machine layer should not become private infrastructure.
When legal obligations are converted into machine-readable formats, hidden interpretation can become operational power. ActProof’s role is to keep that conversion inspectable.
PR-02Traceability
Every important field needs a provenance story.
Where did it come from, what fragment supports it, and where did judgement enter?
PR-03Contestability
Wrong mappings must be easy to challenge.
Open source is not enough. The profile must invite source, fragment, interpretation and currentness challenges.
02 / Refusals
The refusal layer is the trust layer.
ActProof stands out by refusing claims many compliance products are tempted to make.
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
NO-01No legal certification
Hashing is not approval.
A profile can match its source bundle and still require legal review.
NO-02No latest-law assumption
Currentness must be checked.
Pinned artefacts show what was used, not that nothing changed after pinning.
NO-03No vendor neutrality illusion
Private schemas are not public law.
They can be compared to source-bound profiles, but they do not define the public reference.
03 / Maturity
Profiles advance by evidence state, not optimism.
The maturity ladder makes early-stage work honest and stable work recognizable.
0Candidatesource identified
1Draftfields proposed
2Source-boundfragments linked
3Mapper-reviewedworkpaper visible
4Verifier-readyhash checks pass
5Challenge-testedexternal issues recorded
6Stableversioned governance record
04 / Challenge
Every public profile should be disputable.
Challengeability is a design requirement, not an afterthought.
Source challenge
The cited official source is wrong, incomplete or unsuitable.
Fragment challenge
The cited fragment does not support the field.
Interpretation challenge
The profile adds meaning not present in the source.
Overclaim challenge
The profile implies legal certainty it cannot support.
Currentness challenge
The source has changed or a newer official artefact exists.
Omission challenge
A necessary source-supported element is missing.