1.7.0live
Profile-view export
Generate a browser/API/agent-ready profile-view JSON projection from the canonical catalogue entry.
Release tracker / public capability ledger / agent-readable roadmap
What is shipped, what is planned, and what the library does now.
This page keeps ActProof honest by separating shipped package capabilities from future utility.
The release log mirrors the public PyPI release history. The feature tracker explains what the installed actproof-events library and the public site surfaces can actually do today.
Latest PyPI1.8.1 · Jun 6, 2026
Release statetrust metadata live
Feature policyplanned ≠ shipped
Agent surfaceJSON · NDJSON · .well-known
01 / Shipped now
Live capabilities, not roadmap promises.
The useful distinction is not “interesting” versus “not interesting.” It is shipped versus planned. This page keeps that line visible for humans and agents.
1.8.0live
DORA required-field source binding
15/15 required DORA initial-notification fields template-field bound, with source atoms and derivations.
1.8.0live_in_package_static_on_site
Pre-validation primitives
Lint/prevalidate report shapes and expose profile data to agents through static JSON and NDJSON surfaces.
sitelive_on_site
Agent discovery surface
.well-known cards, llms.txt, OpenAPI, MCP-oriented manifests and static NDJSON feeds.
1.8.1live
Profile completeness model
Declare what the profile models, what it is not exhaustive of, and what challenge types are allowed.
1.8.1live
Source-atom coverage
Compute which recorded source atoms are used by fields, required-field bindings, contextual bindings or left unused.
1.8.1live
Field-ID non-universality policy
ActProof field IDs are stable profile-local identifiers, not universal market names. Mapping must use source basis, not names alone.
02 / PyPI release history
Release log sourced from PyPI.
PyPI lists actproof-events 1.8.1 as the latest release, released on Jun 6, 2026.
The table below is a static site snapshot of the public PyPI release history. It is not a live PyPI proxy; PyPI remains the release-provenance source.
| Version | Date | Status | Site interpretation |
|---|---|---|---|
1.8.1 | 2026-06-06 | latest | Trust metadata release: profile completeness, source-atom coverage, field-ID non-universality and mapping guidance. |
1.8.0 | 2026-06-06 | shipped | Field-level source binding release for the DORA initial-notification profile. |
1.7.0 | 2026-06-06 | shipped | First-class profile-view export and validation release. |
1.6.1 | 2026-06-05 | shipped | Schema-valid catalogue fix after the yanked 1.6.0 release. |
1.6.0 | 2026-06-05 | yanked | Yanked on PyPI because catalogue schema validation failed; fixed in 1.6.1. |
1.5.0 | 2026-06-04 | shipped | Earlier catalogue/specification package release. |
1.5.0rc1 | 2026-05-23 | pre-release | Pre-release candidate. |
1.4.0rc1 | 2026-05-19 | pre-release | Pre-release candidate. |
03 / What the library does
The current installed package is a source-bound profile utility layer.
Installed from PyPI, actproof-events provides the catalogue, schemas, DORA profile-view export, source-binding inspection and trust metadata commands. The public website exposes the same profile as JSON and static agent streams.
| Capability | Since | Status | What it gives users |
|---|---|---|---|
| Profile-view export | 1.7.0 | live | Generate a browser/API/agent-ready profile-view JSON projection from the canonical catalogue entry. |
| DORA required-field source binding | 1.8.0 | live | 15/15 required DORA initial-notification fields template-field bound, with source atoms and derivations. |
| Pre-validation primitives | 1.8.0 | live_in_package_static_on_site | Lint/prevalidate report shapes and expose profile data to agents through static JSON and NDJSON surfaces. |
| Agent discovery surface | site | live_on_site | .well-known cards, llms.txt, OpenAPI, MCP-oriented manifests and static NDJSON feeds. |
| Profile completeness model | 1.8.1 | live | Declare what the profile models, what it is not exhaustive of, and what challenge types are allowed. |
| Source-atom coverage | 1.8.1 | live | Compute which recorded source atoms are used by fields, required-field bindings, contextual bindings or left unused. |
| Field-ID non-universality policy | 1.8.1 | live | ActProof field IDs are stable profile-local identifiers, not universal market names. Mapping must use source basis, not names alone. |
pip install actproof-events actproof-events export-profile-view op:eu.dora.ict_incident_notification_initial.v1 --out dora.profile-view.json --validate actproof-events explain-field op:eu.dora.ict_incident_notification_initial.v1 classification_criteria_triggered actproof-events source-atom-coverage op:eu.dora.ict_incident_notification_initial.v1 actproof-events profile-completeness op:eu.dora.ict_incident_notification_initial.v1
What changed in 1.8.1
The missingness question is now inspectable.
Source-atom coverage shows which recorded source atoms are used by fields and which remain unused. The profile completeness model says what the DORA profile models, what it does not claim to cover, and what kinds of challenge are allowed.
04 / Planned next
Future utility, explicitly not live yet.
These items are useful, but they should not be described as shipped until implemented and exposed through the package/site data. In particular, schema comparison must remain candidate mapping for human review, not an authoritative match engine.
1.8.x/1.9.0planned
Challenge records
Machine-readable records for missing-field, wrong-source, weak-derivation, outdated-source and ambiguous-mapping challenges.
1.9.0planned
Candidate schema comparison
Compare an external schema or field list to ActProof as candidate mappings for human review, never authoritative matches.
1.9.0planned
External schema mapping records
Persist reviewed mappings between external system fields and ActProof field IDs with source evidence and review state.
futureplanned
Official text fragment sealing
Move from locator-bound provisional atoms to verified official text fragment hashes where feasible.
futureplanned
Native MCP runtime
Move beyond static MCP-oriented manifests into a real MCP Streamable HTTP runtime when the hosted execution layer is ready.
05 / Boundary
The tracker is part of the trust model.
If it is not listed as shipped here, ActProof should not be described as doing it.
This page is deliberately conservative. It helps reviewers, agents and implementers distinguish source-bound profile capabilities from future workflow ambitions.
The tracker can show
- which package version is current on PyPI
- which capabilities are live in the library or site
- which planned features remain future work
- which boundaries protect users from overclaiming
The tracker cannot show
- that planned features are already implemented
- that the profile is legally complete or regulator-approved
- that external schemas are correctly mapped
- that ActProof replaces legal, audit or supervisory review
Track the object before trusting the claim.
Use the release JSON, roadmap JSON and package commands to inspect what ActProof can do now.