actproof-events / export-profile-view

Generate the same DORA JSON yourself.

The DORA profile page is powered by a JSON projection generated from the actproof-events package.

The canonical object is the catalogue entry inside the package. The website publishes a browser-ready profile view so humans, systems and AI agents can inspect the same profile data, including field-level source bindings and 2.x bank-operability metadata for all required DORA fields.

Open generated JSON →Download JSON ↓Inspect fields →PyPI ↗

Install the package.

The public export lives inside actproof-events. A website script is no longer the authority for building the JSON.

python -m pip install actproof-events

Generate the profile-view JSON from the CLI.

This command exports the DORA initial-notification profile into the same kind of JSON consumed by this website.

actproof-events export-profile-view \
op:eu.dora.ict_incident_notification_initial.v1 \
--out dora.profile-view.json \
--validate

For a compact machine-oriented file:

actproof-events export-profile-view \
op:eu.dora.ict_incident_notification_initial.v1 \
--compact \
--out dora.profile-view.json \
--validate

Or build it from Python.

The Python API gives implementers the same projection builder without copying website code.

from actproof_events.exports import build_profile_view, write_profile_view

view = build_profile_view(
    "op:eu.dora.ict_incident_notification_initial.v1"
)

write_profile_view(
    "op:eu.dora.ict_incident_notification_initial.v1",
    "dora.profile-view.json",
    validate=True,
)

What the export contains

A rich public projection, not a second canonical object.

The generated file is meant to be useful immediately in compliance interfaces and review tooling while keeping the catalogue entry as the source of truth.

IdentityProfile and catalogue hash

act_id, display name, version, regulatory citation and catalogue_entry_hash.

BoundariesNon-claims and claim flags

Machine-readable limits prevent the projection from being mistaken for legal approval.

Fields27 field rows

Required status, disclosure tier, mapping type, interpretive load, evidence labels and source-basis scope.

MetricsCoverage summary

Field source basis, evidence scope, assessment scoring and disclosure-tier coverage.

Projection hash

The file carries a reproducibility hash.

profile_semantic_hash is the version-independent reproducibility hash for the profile semantics. profile_artifact_hash is the release-specific hash that retains package-version provenance. profile_view_hash remains as a compatibility alias for the semantic hash. None of these is a receipt hash.

Canonical objectCatalogue entry

The receipt-facing binding remains catalogue_entry_hash.

Generated objectProfile view

The browser-ready JSON is a public projection generated from package services.

Schemaactproof.profile_view.v1

The package ships spec/schemas/profile_view.v1.schema.json.

Use the generated projection anywhere inspection is needed.

The same export can back a static website, regulator-facing audit pack, compliance UI, internal API, MCP server or field-mapping review tool.

Return to field browser →Open JSON →GitHub ↗

Source binding

Validate field-level source bindings.

actproof-events validate-source-bindings op:eu.dora.ict_incident_notification_initial.v1
actproof-events explain-field op:eu.dora.ict_incident_notification_initial.v1 classification_criteria_triggered

The 1.8.x source-binding line gates on 15/15 required DORA fields being template-field source-bound. Optional fields carry experimental contextual derivations but do not count toward the required-field release gate.