DORA PROFILE / FIELD INSPECTIONsource-bound profile · field status · coverage metricsbounded claim: no legal advice · no compliance certification
DORA / Article 19(4) / Initial notification

Show me the fields.

This page turns the DORA initial-notification profile into a human inspection surface.

Click any field to see its status, mapping type, source-basis scope, evidence labels, disclosure tier and boundary. The page is generated from the actproof-events package, not hand-entered HTML.

Data provenance

Generated from the public actproof-events package.

This page consumes /assets/data/dora.profile-view.json, a browser-ready projection generated from the installed package service layer. It is not the canonical catalogue entry; the canonical binding object is the catalogue entry hash.

Packageactproof-events

Loading provenance...

Canonical bindingLoading catalogue hash...

sha256(raw catalogue entry JSON file bytes)

Coverage metrics

What is mature, and what is still provisional.

Coverage metrics prevent overclaiming. They show whether a profile has field-level source derivations, field-level evidence labels, scored assessment rows and complete disclosure tiers.

Interactive profile

Required and optional reporting fields.

Rows marked interpretive are the places where judgement concentrates. Rows marked act fallback use act-level source bindings until Mapper-generated field derivations are available.

FieldReq.StatusMappingSourceDisclosure
Loading profile fields...
Boundary

The page shows profile evidence, not legal approval.

ActProof shows what a machine-readable profile claims and where it came from. It does not certify legal compliance and is not legal advice.

Field-level derivations are shown when the Mapper has produced them. Until then, the page marks source basis as act-level fallback. This is intentional: the inspection surface shows maturity honestly instead of presenting provisional coverage as complete.

Make the profile inspectable before it becomes infrastructure.

Use this page as the human-facing front door, then let the API and MCP server expose the same profile to software and compliance agents.