Builder useSchema alignment
Compare a private schema against a public profile.
Detect missing required fields, vendor-only fields and unsupported assumptions before enterprise review.
Audience fit / market slot / adoption path
For teams that need regulation to become inspectable infrastructure.
ActProof is for people building, reviewing or operating machine-readable regulatory workflows where field-level source traceability matters.
It is not another GRC dashboard. It sits beneath dashboards, agents and reporting systems: a source-bound profile layer that tells users where each field came from, what evidence it expects, and what the system refuses to claim.
Primary userscompliance · regtech · audit · AI tools
Useful whenfield provenance matters
Not useful whenyou want legal sign-off
Adoption pathinspect → lint → compare → integrate
01 / Compliance and regulatory teams
For teams that need a draft report checked before it becomes expensive.
Use ActProof when the question is: “Which required fields are missing, which fields are interpretive, and what evidence should be behind them?”
DORA reporting creates structured fields, templates and timing obligations. The market is already crowded with workflow tools, but compliance teams still need a source-bound layer beneath the workflow: a way to see field origin, evidence expectation and readiness before formal verification or submission.
Good fit
- pre-submission completeness checks
- DORA initial-notification readiness review
- internal report-shape linting
- evidence expectation visibility
- handoff from compliance to technical teams
What it does not replace
- legal review
- NCA filing systems
- incident response platforms
- institution-specific policy decisions
- final supervisory interpretation
02 / GRC and regtech builders
For product teams that need public regulatory field grounding.
Use ActProof when your product has DORA fields, but your buyers will ask where those fields came from.
Most platforms can create input forms. Fewer can show whether a field is template-cell bound, only contextually derived, or still provisional. ActProof can act as a reference layer: compare your schema, explain a field, or use the generated JSON to feed your own frontend.
Builder useField docs
Generate field-level documentation.
Use source atoms, derivation notes and review gates to explain fields in product documentation.
Builder useAPI grounding
Give agents a safe source object.
Expose ActProof profile data through REST or MCP instead of asking a model to infer regulatory structure from prose.
03 / Audit, assurance and review teams
For reviewers who need the mapping to be challengeable.
ActProof is useful when a reviewer does not want to accept a regulatory profile on trust. The profile can be inspected as a set of objects: source atoms, field derivations, review status, evidence labels, hashes and non-claims.
01Check profile identityact_id · version
02Inspect source atomsCELEX · ELI
03Review derivationsdraft · reviewed
04Challenge mappingsnot accepted blindly
05Verify hashesreproducible
06Record boundaryno overclaim
04 / AI-agent and MCP implementers
For teams that need compliance agents to call bounded tools, not improvise regulatory answers.
The agent should not guess where a field came from. It should call the source-bound profile.
ActProof fits teams building compliance copilots, internal review agents or AI-enabled reporting assistants. The package exposes explain, coverage, lint and prevalidation surfaces that make regulatory context callable rather than hidden in prompt text.
MCP TOOL PATH 1. explain_field_source → why this field exists, source atoms, review status 2. source_coverage → required template-field coverage, optional contextual derivations 3. lint_report → missing required fields, unknown fields, high-attention fields 4. prevalidate_report → blocked / attention_required / ready_for_preverification boundary: pre-validation only; not compliance certification
Why it matters
Agent safety starts with bounded tools.
MCP creates a standard way for AI systems to connect to tools and data sources. ActProof provides a regulatory grounding tool surface where every answer can point back to the profile object and its source atoms.
05 / Public-interest maintainers and standards groups
For people who want regulatory mappings to be reused, not privately re-invented.
ActProof can support open profile work where many organisations would otherwise recreate the same regulatory map in private. A profile can remain open, challengeable and versioned while still being useful to commercial systems.
06 / Who this is not for
Not every buyer should use ActProof directly.
This page should filter as much as attract. ActProof is infrastructure for source-bound regulatory profiles and pre-validation. It is not a replacement for the operational systems around it.
Use ActProof if
- you need field-level provenance
- you build or review regulated reporting tools
- you need agent-callable regulatory context
- you want machine-readable profiles with explicit non-claims
Do not use it as
- a legal opinion
- a GRC system of record
- a supervisory filing channel
- an incident-response workflow platform
- a promise that a filing is accepted or compliant
Field names
Field names are not universal.
ActProof field IDs are canonical inside an ActProof profile, not universal names for every bank, vendor or regulator-facing system. The point is to map external schemas against a source-bound reference, not force the market to adopt ActProof names.
If the field matters, the source basis should be inspectable.
Start with the live DORA profile, then choose the path that fits your role: lint a draft, compare a schema, verify a profile, or build against the JSON.