Skip to main content
Praxikon

Releases

What changed in each release

Anyone building on this data has to be able to see when something went out and what moved. Three counters move independently: the content, the shape of that content, and the API surface around it. This page states which of the three it was per release, and what that means for a citation you already wrote down.

Current release
2.8.0
Schema
1.5.0
API document
1.13.1
Register kept since
8 August 2026

What changed in each release

  1. ContentCurrently served

    The guidelines on Article 50 have an Official Journal reference, and three objects cite Article 4a instead of the deleted Article 10(5)

    The Commission guidelines on the transparency obligations of Article 50, adopted on 5 November 2026 as C(2026) 7702 final, were published in the Official Journal, C series, on 12 November 2026 as Communication C/2026/6005. Points (1) to (155) are the same as in the adopted text; a reference to a point is found under the same number. The change object on the adoption carries a version with that reference and the source now carries the Official Journal ELI. In addition a correction: the definitions of special categories of personal data and of personal data and the Article 10 obligation still named the deleted Article 10(5) as applicable law. That paragraph was removed by Article 1, point (9)(b), of Regulation (EU) 2026/1744; since 27 July 2026 the exception for detecting and correcting bias is in Article 4a. Its paragraph 1 applies to providers of high-risk AI systems; paragraph 2 is new and also applies, under the same conditions and safeguards and without creating an obligation, to providers and deployers of other AI systems and models and to deployers of high-risk AI systems. The published versions stay in place.

    dataset_version
    2.8.0
    schema_version
    1.5.0
    API document
    1.13.1

    Snapshot recorded (644 object versions)

    Compare this release object by object

    praxikon:sys:registry:release:2026-11-20-article-50-guidelines-official-journal

  2. Content

    The rules for AI regulatory sandboxes are in the graph, Annex I, Section B, names the right articles and the GPAI guidelines are cited in their adopted text

    On 10 November 2026 the Commission adopted Implementing Regulation (EU) 2026/2487, published on 11 November 2026 and in force from 1 December 2026. For all Article 57 AI regulatory sandboxes it governs application and selection (outcome no later than three months after the complete application, with an appeal under national law), costs (free of charge for SMEs, start-ups and public authorities, subject to exceptional costs), the sandbox plan, the written proof and the exit report (no later than 45 working days after participation ends). The graph did not know the act for nine days. A source and a change object are added, and the obligation, the action and the evidence of Article 57 carry a version that follows the regulation. In addition a correction: the guidance object on Annex I, Section A versus Section B, named for Section B the articles from before Regulation (EU) 2026/1744. Since 27 July 2026 only Article 6(1), Article 60a and Articles 102 to 112 apply there, and Articles 57, 58 and 59 only in so far as the requirements have been integrated in the harmonisation legislation. And a second correction: eight objects cited the guidelines on the scope of the obligations for providers of general-purpose AI models in the text of 18 July 2025, C(2025) 5045 final. The Commission formally adopted them on 19 November 2025 as C(2025) 7719 final, in which the paragraph numbers of Section 3.2 moved three places. The objects now cite the adopted text and its paragraphs (57) to (68).

    dataset_version
    2.7.0
    schema_version
    1.5.0
    API document
    1.13.1

    Snapshot recorded (640 object versions)

    Compare this release object by object

    praxikon:sys:registry:release:2026-11-19-sandbox-implementing-regulation

  3. Content

    Article 60: testing outside a sandbox also covers Annex I, Section A

    The Article 60 obligation described testing in real world conditions outside an AI regulatory sandbox as a regime for Annex III high-risk AI systems only. Article 1, point (24), of Regulation (EU) 2026/1744 replaced the first subparagraph of paragraph 1 and paragraph 2; since 27 July 2026 the high-risk AI systems covered by the harmonisation legislation of Annex I, Section A, are covered too. The third subparagraph of paragraph 1 was not amended. For products under Annex I, Section B, Article 60a applies (Article 1, point (25)): Member States may allow such testing within a framework of their own. The summary, the condition, the exception and the official fact now say so. The published version stays in place.

    dataset_version
    2.6.11
    schema_version
    1.5.0
    API document
    1.13.1

    Snapshot recorded (627 object versions)

    Compare this release object by object

    praxikon:sys:registry:release:2026-11-19-article-60-annex-i-section-a

  4. Content

    EN 18286 and Article 40(1): the presumption for Article 17 is not settled

    Five objects stated without reservation that EN 18286:2026 confers a presumption of conformity under Article 40(1). That paragraph names the requirements of Chapter III, Section 2; Article 17, the subject of the standard, sits in Section 3, and Regulation (EU) 2026/1744 did not amend paragraph 1. The new versions state the presumption to the extent the standard covers requirements that paragraph 1 names, and the coverage of Article 17 as an open point. The note on Article 41 read the conditions of paragraph 1 as fulfilled; that is not settled. Beside standardisation request M/613 the objects now also give Implementing Decision C(2025) 3871. The published versions stay in place.

    dataset_version
    2.6.10
    schema_version
    1.5.0
    API document
    1.13.1

    Snapshot recorded (626 object versions)

    Compare this release object by object

    praxikon:sys:registry:release:2026-11-19-en-18286-presumption-and-article-41

  5. Content

    Article 49(2): fewer data in the registration since the deletion in Annex VIII, Section B

    The editorial statement on Article 49(2) said what a provider relying on Article 6(3) puts into the EU database, but not that Regulation (EU) 2026/1744 has deleted points 7 and 9 of Annex VIII, Section B, since 27 July 2026 (Article 1, point (42); recital 22): the short summary of the grounds on which the system is not high-risk, and the Member States in which it was made available. The statement now says so, and that the Article 6(3) condition stays in the registration and the assessment must still be documented. The published version stays in place.

    dataset_version
    2.6.9
    schema_version
    1.5.0
    API document
    1.13.1

    Snapshot recorded (621 object versions)

    Compare this release object by object

    praxikon:sys:registry:release:2026-11-18-article-49-annex-viii-section-b

  6. Content

    Article 11: no deployer right to the file, and the form the Commission is to establish

    The Article 11 obligation said that buying organisations must be able to request the Annex IV file contractually and cannot meet their Article 26 duties without it. The Regulation gives the deployer no right to the technical documentation: the deployer works with the instructions for use of Article 13, and Article 26(1) refers to those instructions. The editorial statement now says so; the recommended action stays a contractual choice and says that the Regulation does not require it. The exception spoke of the form established by the Commission and of small providers; it now names SMEs, including start-ups, and small mid-cap enterprises, and the simplified form that the Commission is to establish under Article 11(1). The published version stays in place.

    dataset_version
    2.6.8
    schema_version
    1.5.0
    API document
    1.13.1

    Snapshot recorded (620 object versions)

    Compare this release object by object

    praxikon:sys:registry:release:2026-11-18-article-11-deployer-and-form-correction

  7. Content

    Article 63: SMEs instead of microenterprises

    Since 27 July 2026 the simplification of the quality management system in Article 63(1) applies to SMEs, including start-ups, that have no partner enterprises or linked enterprises, and no longer to microenterprises alone (Article 1, point (26), and recital 28 of Regulation (EU) 2026/1744). The obligation already said so in its summary, condition and official fact, but the action, the evidence object and three editorial sentences of the obligation still spoke of a microenterprise. They now say SME. The sentence that Articles 62 and 63 are the only two places in the Regulation where the size of an undertaking legally makes a difference is also removed; Article 11(1) and Article 99(6) take SMEs into account as well. The published versions stay in place.

    dataset_version
    2.6.7
    schema_version
    1.5.0
    API document
    1.13.1

    Snapshot recorded (619 object versions)

    Compare this release object by object

    praxikon:sys:registry:release:2026-11-17-article-63-sme-correction

  8. Content

    Article 4a: Article 2(7) stated correctly and the official Dutch text

    The Article 4a obligation said that Article 2(7) left the GDPR unaffected without reservation until 27 July 2026. The original text already made a reservation for Article 10(5); Regulation (EU) 2026/1744 moved that reservation, together with the basis, to Article 4a. The note and the official fact now say so, and the weighing of the two readings no longer leans on a reservation that would be new. The object also gives paragraphs 1 and 2 in Dutch in the official text, with "vooringenomenheid" instead of "vertekening". The published version stays in place.

    dataset_version
    2.6.6
    schema_version
    1.5.0
    API document
    1.13.1

    Snapshot recorded (616 object versions)

    Compare this release object by object

    praxikon:sys:registry:release:2026-11-13-article-4a-correction

  9. Content

    Four editorial corrections around Article 6(1a) to (1c)

    The official fact of the change object now says that Article 1, point (8), of Regulation (EU) 2026/1744 inserts three paragraphs into Article 6, and quotes the first two; before, it read as if there were only two. The note on the provision module now says that the definition object on Article 3, point (14), has given the amended text since 12 November 2026. The Dutch quotations of paragraph 1a and of Article 51(3) now spell efficiëntie as the source does. And the module cites the inserted paragraphs with their precise locator: Article 1, point (8), of the amending Regulation. The published versions stay in place.

    dataset_version
    2.6.5
    schema_version
    1.5.0
    API document
    1.13.1

    Snapshot recorded (615 object versions)

    Compare this release object by object

    praxikon:sys:registry:release:2026-11-12-article-6-paragraphs-review-follow-up

  10. Content

    Title and quotation on Article 6(1a) to (1c) corrected

    Regulation (EU) 2026/1744 inserts three paragraphs into Article 6. Paragraphs 1a and 1b set out when an AI system is a safety component; paragraph 1c provides that a third-party conformity assessment required solely due to risks other than risks to health and safety does not count for the condition in Article 6(1), point (b). The title of the change object said that all three paragraphs concern safety components and now names both subjects; the locator of the official fact now points to the two paragraphs it quotes. In addition, the provision module quoted the amended Article 3, point (14), in English with "risks to the health and safety"; the official text reads "risks to health and safety". The published versions stay in place.

    dataset_version
    2.6.4
    schema_version
    1.5.0
    API document
    1.13.1

    Snapshot recorded (612 object versions)

    Compare this release object by object

    praxikon:sys:registry:release:2026-11-12-article-6-paragraphs-wording

  11. ContentAPI surface

    The definition of safety component now includes the clause Regulation (EU) 2026/1744 added

    Regulation (EU) 2026/1744 amended Article 3, point (14): for the purposes of the definition, a component fulfils a safety function where its intended purpose is to prevent or mitigate risks to health and safety of persons or property. That amendment has operated since 27 July 2026. The definition object gave only the original text and now also gives that clause, with a locator in the amending Regulation. The published version stays in place. In addition, the OpenAPI document (1.13.1) now describes the profile field adverse_significant_decision as Article 86(1) does: a decision by the deployer on the basis of the output of a high-risk AI system in Annex III, other than point 2, with legal effects or a similarly significant effect that the person considers adverse to their health, safety or fundamental rights.

    dataset_version
    2.6.3
    schema_version
    1.5.0
    API document
    1.13.1

    Snapshot recorded (610 object versions)

    Compare this release object by object

    praxikon:sys:registry:release:2026-11-12-safety-component-definition

  12. Content

    The note on Article 86 now also names the exception in Article 111(1)

    The note on Article 86 says that Article 111(2) applies to a system already in use: the Regulation then applies only once its design changes significantly, and for systems of public authorities by 2 August 2030 at the latest. Paragraph 2, however, excludes the systems of paragraph 1. AI systems which are components of the large-scale IT systems listed in Annex X and were placed on the market or put into service before 2 August 2027 must, under paragraph 1, be brought into compliance by 31 December 2030. The note now says so too.

    dataset_version
    2.6.2
    schema_version
    1.5.0
    API document
    1.13.0

    Snapshot recorded (609 object versions)

    Compare this release object by object

    praxikon:sys:registry:release:2026-11-11-article-86-article-111-paragraph-1

  13. Content

    Two corrections from re-reading the review file: the date of 2026/2274 and the status of Article 49

    Two errors were found while updating the review file. The obligation for Articles 40 to 42 called Implementing Decision (EU) 2026/2274 a decision of 14 October 2026. It is of 12 October 2026 and was published in the Official Journal on 14 October 2026; the presumption of conformity runs from that publication, so the substance was right. The template with the legal text of Article 49 still said not yet applicable. Under decision D1 of 6 September 2026 Article 49 has applied since 2 August 2026, as the other Article 49 objects already said. Both objects gain a new version beside the published one.

    dataset_version
    2.6.1
    schema_version
    1.5.0
    API document
    1.13.0

    Snapshot recorded (608 object versions)

    Compare this release object by object

    praxikon:sys:registry:release:2026-11-11-review-findings-corrections

  14. Content

    The guidelines on Article 50 are formally adopted, also in Dutch

    On 5 November 2026 the Commission formally adopted the guidelines on the transparency obligations of Article 50 as Communication C(2026) 7702 final. The text of 20 July 2026 (C(2026) 5054 final) was the approval of the content. We compared both English texts sentence by sentence: the content and the numbering of points (1) to (155) are the same, the differences are editorial. Existing locators that point to a point of C(2026) 5054 final therefore stay as they are and are found under the same number in the adopted text. There is now also an official Dutch text. The guidelines remain non-binding (point 5). Two other Commission sources were re-verified on the same day without a change to any statement: the questions and answers on AI literacy (last updated on 20 October 2026, the opening sentence now follows the amended wording of Article 4) and the publication page of the guidelines on the AI system definition (only a typo corrected).

    dataset_version
    2.6.0
    schema_version
    1.5.0
    API document
    1.13.0

    Snapshot recorded (606 object versions)

    Compare this release object by object

    praxikon:sys:registry:release:2026-11-11-article-50-guidelines-adopted

  15. Content

    The guidance on AI agents separates the Article 50 duty from the advice in the guidelines

    The guidance on disclosure by AI agents said that an agent must disclose both that it is AI and on whose behalf it acts, and called that a twofold obligation. That went further than the law. Article 50(1) only requires that people are informed they are interacting with an AI system, unless that is obvious. That the agent also states on whose behalf it acts is asked by the Commission guidelines (point 31), which point 5 says are not binding. The label, summary and interpretation now say so, and the interpretation cites Article 50(1) and point 5 as sources.

    dataset_version
    2.5.1
    schema_version
    1.5.0
    API document
    1.13.0

    Snapshot recorded (605 object versions)

    Compare this release object by object

    praxikon:sys:registry:release:2026-11-06-ai-agent-disclosure

  16. API surface

    The GDPR obligations can be read through the API and the MCP tools

    The graph endpoints (`/api/v1/obligations`, `/api/v1/entities`, `/api/v1/changes` and `/api/v1/search`) now take the parameter `regulation`. Without it, or with `ai-act`, they serve the AI Act graph as before. With `gdpr` they serve the GDPR obligations graph in the same shape: obligation, action, evidence and source, with per statement the article and paragraph or point of Regulation (EU) 2016/679 and the sources the GDPR registers link to that article, under identifiers praxikon:eu:gdpr. That graph has its own dataset id, version 1.0.0 and a recorded snapshot. An `id` under praxikon:eu:gdpr is looked up in the GDPR graph without the parameter too. Every graph response names its graph in `meta.regulation`. The MCP tools get_obligations, get_graph_entities and search_implementation_graph take the same argument, and get_source_provenance works on a GDPR identifier. No field was removed or renamed and the AI Act graph did not move: dataset 2.5.0 and schema 1.5.0 stand where they stood.

    dataset_version
    2.5.0
    schema_version
    1.5.0
    API document
    1.13.0

    Snapshot recorded (604 object versions)

    No per-object comparison. This release did not move the content counter, so there is nothing to compare per object. What moved was the shape of the response or the surface around it, and that is described in the summary.

    praxikon:sys:registry:release:2026-10-27-gdpr-obligations-graph

  17. Content

    prEN 18229 follows the restructuring by CEN/CLC/JTC 21

    The CEN/CLC/JTC 21 work programme divides the AI trustworthiness framework into five parts: logging (part 1), transparency (part 2), human oversight (part 3), accuracy (part 4) and robustness (part 5). The graph still followed the older division. Corrected: the Article 15 object (now prEN 18229-4 and prEN 18229-5), the Article 14 object (prEN 18229-3, human oversight only), the stage of prEN 18229-1, the references in ISO/IEC 24029 and ISO/IEC 12792, and the count in Articles 40 to 42.

    dataset_version
    2.5.0
    schema_version
    1.5.0
    API document
    1.12.0

    Snapshot recorded (604 object versions)

    Compare this release object by object

    praxikon:sys:registry:release:2026-10-27-pren-18229-restructure

  18. Content

    Status sweep: outdated states in the graph updated, and the transparency code of practice has been found adequate

    After a reader report about EN 18286 the status statements in the graph were checked against the official sources. New: the change object on the adequacy of the transparency code of practice (Commission 8 July 2026, AI Board 9 July 2026) and the opinions on both codes of practice as sources. Later versions: ISO/IEC 42001 (EN 18286 is harmonised), the transparency code of practice, the Article 72 example (guidelines with a template by 2 September 2027) and Article 75 (the consolidated text exists). Corrections, also in the correction register: Article 57 (sandbox by 2 August 2027), Article 56 (the GPAI code was found adequate on 1 August 2025), the Q&A on the transparency code, the status of the high-risk classification guidelines (consultation closed on 23 July 2026) and the description of M/613 on prEN 18285. The default moment moves to 27 October 2026.

    dataset_version
    2.4.0
    schema_version
    1.5.0
    API document
    1.12.0

    Snapshot recorded (598 object versions)

    Compare this release object by object

    praxikon:sys:registry:release:2026-10-27-status-sweep

  19. Content

    EN 18286 is a harmonised standard, and the procedural rules for GPAI evaluations and fines are in the graph

    Implementing Decision (EU) 2026/2274 published the reference of EN 18286:2026 in the Official Journal on 14 October 2026; from that day the standard confers a presumption of conformity for the requirements it covers. Implementing Regulation (EU) 2026/1755 has governed since 10 August 2026 how the Commission evaluates general-purpose AI models and how it conducts fining proceedings. Both acts became a change object and a source. The standard object EN 18286, Articles 40 to 42, the definition of harmonised standard and Articles 99 to 101 gained a version dated to the act, beside their published version, which stays unchanged. The default moment on the legal axis moves to 24 October 2026, because both acts took effect after the old default of 8 August 2026.

    dataset_version
    2.3.0
    schema_version
    1.5.0
    API document
    1.12.0

    Snapshot recorded (587 object versions)

    Compare this release object by object

    praxikon:sys:registry:release:2026-10-24-implementing-acts

  20. Content

    The statement on the transparency code of practice now names the right paragraph of Article 50

    The statement on the Code of Practice on transparency of AI-generated content said that signatories can rely on it for Article 50(2), (3) and (5). That was wrong: paragraph 3 concerns emotion recognition and biometric categorisation, paragraph 4 deep fakes, and Article 50(7), as replaced by Regulation (EU) 2026/1744, concerns codes of practice for the detection, marking and labelling of artificially generated or manipulated content and names paragraphs 2 and 4. The statement now names paragraphs 2, 4 and 5. The correction of 5 October 2026 repaired the same error in the blog posts but missed this statement in the graph. The change object carries version 1.0.1 beside the published 1.0.0, which stays unchanged; anyone querying on an earlier known_at still gets what they got then. The error is recorded in the correction log.

    dataset_version
    2.2.2
    schema_version
    1.5.0
    API document
    1.12.0

    Snapshot recorded (581 object versions)

    Compare this release object by object

    praxikon:sys:registry:release:2026-10-20-transparency-code-paragraphs

  21. Content

    The note on Article 86 now says what applies to systems already in use

    The note on Article 86 said the right to an explanation applies from 2 August 2026 to systems already in use at that point. That was wrong: for a high-risk system already in use before the Annex III regime operates, Article 111(2) provides that the Regulation applies only once its design changes significantly, and for systems of public authorities by 2 August 2030 at the latest. The application date itself stays 2 August 2026, the text date from decision D1, and the practical date stays 2 December 2027. The new note names all three. The object carries version 2.0.1 beside the published 2.0.0, which stays unchanged; anyone querying on an earlier known_at still gets what they got then. The error is recorded in the correction log.

    dataset_version
    2.2.1
    schema_version
    1.5.0
    API document
    1.12.0

    Snapshot recorded (580 object versions)

    Compare this release object by object

    praxikon:sys:registry:release:2026-10-11-article-86-note

  22. ContentShape

    The provision layer is registered, and the application date no longer shares one field with the practical date

    Articles 43 to 49, 72, 73, 85 and 86 are named in none of the three points of Article 113, third paragraph, and therefore fall under the general application date in the second paragraph: 2 August 2026. That date now sits on the duty objects concerned, with the new field `timing_basis` stating what it rests on. The practical date, the day the Annex III high-risk regime gives a duty an object, sits beside it in the equally new field `high_risk_regime_from` rather than in the field a machine reads as the application date. The three objects whose content changed carry their published version unchanged alongside the new one: anyone querying on the old known_at still gets what they got then. Beyond that, outside the reach of the Union the engine now assesses nothing rather than reporting every duty as not indicated, and the Article 5 screening without a signal delivers the screening record as evidence of that conclusion. A dossier that assesses nothing outside the reach of the Union now also carries the source that statement rests on, Article 2 of the base regulation, and the published schema accepts that empty list only with that ground attached. Finally, the provision layer is registered: the dataset moves from twenty-seven to fifty-four obligation objects and from four to fourteen sources, with Directive (EU) 2019/1937 added. Three of the new objects gain a decision rule; the other twenty-four are declared, with a reason, as deliberately not assessed in every assessment, so absence never reads as an outcome.

    dataset_version
    2.2.0
    schema_version
    1.5.0
    API document
    1.12.0

    Snapshot recorded (579 object versions)

    Compare this release object by object

    praxikon:sys:registry:release:2026-09-06-application-dates-and-scope

  23. API surface

    Saying which duties were and were not assessed

    An assessment that runs five routes and then says nothing about the rest reads as a statement about everything. The manifest therefore now carries an assessment scope: per duty it says whether it was assessed and, if not, on what ground. A profile that sets `profile_version` to 2.0.0 makes the engine walk every registered duty; a profile without that field keeps exactly the original five routes and the same outcomes. A conditional outcome is now an answer shape of its own rather than a duty that quietly disappears, and an answer names its addressee. The manifest schema moves to 1.3.0 and the OpenAPI document to 1.12.0. No field was removed or renamed, no enum member was dropped, and the graph did not move: dataset 2.1.0 and schema 1.4.0 stand where they stood.

    dataset_version
    2.1.0
    schema_version
    1.4.0
    API document
    1.12.0

    Snapshot recorded (425 object versions)

    No per-object comparison. This release did not move the content counter, so there is nothing to compare per object. What moved was the shape of the response or the surface around it, and that is described in the summary.

    praxikon:sys:registry:release:2026-09-06-scope-and-conditional

  24. API surface

    A stable address for every published answer

    Alongside a free-form question, the answer endpoint can now retrieve an exact `answer_id` or canonical page path. Base answers and refinements carry the same language-independent identifier in the full and compact views. The OpenAPI contract now describes the actual response completely as three explicit shapes: compact, full and no match. No field was removed or renamed and the graph did not move.

    dataset_version
    2.1.0
    schema_version
    1.4.0
    API document
    1.11.0-beta.1

    Snapshot recorded (425 object versions)

    No per-object comparison. This release did not move the content counter, so there is nothing to compare per object. What moved was the shape of the response or the surface around it, and that is described in the summary.

    praxikon:sys:registry:release:2026-08-15-addressable-answers

  25. ContentShape

    The right that sits opposite the duty

    The knowledge base covered the deployer duties but not the right of the person being decided about. Article 86 is now an object of its own: anyone affected by a decision resting on the output of an Annex III system can request an explanation of the role of that system and of the main elements of the decision. It is the first object to carry a preliminary reading. That is new in schema 1.4.0: two fields saying that the text of a provision is settled while its application has not been decided anywhere, with a note stating what is open and which alternative reading is defensible. That note travels in the API, the MCP responses and the structured data rather than sitting as a footnote on a page. The object also carries the first known_at of its own: until now every published object carried the same moment, so a window on the knowledge axis could not separate two moments.

    dataset_version
    2.1.0
    schema_version
    1.4.0
    API document
    1.10.0-beta.1

    Snapshot recorded (425 object versions)

    Compare this release object by object

    praxikon:sys:registry:release:2026-08-14-article-86

  26. API surface

    The same answer, a tenth of the bytes

    The answer endpoint now takes `view=brief`. That form returns what an agent needs in order to act and to cite: the question, the likely role, the obligations with label, identifier, legal status and application date, the first actions, the required evidence, and one locator per obligation. It is the same answer from the same deterministic engine with the explanation removed, not a different conclusion. The full form stays the default and does not change; anyone who omits the parameter notices nothing. An unrecognised value falls back to the full form rather than returning an error, because a typo in a parameter that only governs size should not cost an answer.

    dataset_version
    2.0.0
    schema_version
    1.3.0
    API document
    1.10.0-beta.1

    Snapshot recorded (417 object versions)

    No per-object comparison. This release did not move the content counter, so there is nothing to compare per object. What moved was the shape of the response or the surface around it, and that is described in the summary.

    praxikon:sys:registry:release:2026-08-13-compact-answer-view

  27. API surface

    What we know a provision means

    Beside the layer that says what happened there is now a layer that says what a ruling does to a provision: interprets, narrows, broadens, confirms or contradicts. That relation is the point, because a ruling does not change the text of an obligation and does not move its date of application; it moves what we know about it, and that moment sits on the ruling as a date of its own. A manifest carrying a narrowed obligation therefore surfaces through `/api/v1/impact` without a single field of the graph having moved. There is no case law on the AI Act itself yet, and that is stated in words rather than left as an empty field: the seven recorded decisions are GDPR context and carry the relation "illustrates" only.

    dataset_version
    2.0.0
    schema_version
    1.3.0
    API document
    1.9.0-beta.1

    Snapshot recorded (417 object versions)

    No per-object comparison. This release did not move the content counter, so there is nothing to compare per object. What moved was the shape of the response or the surface around it, and that is described in the summary.

    praxikon:sys:registry:release:2026-08-13-ruling-register

  28. ContentShapeAPI surface

    Room for more than one regulation

    Every identifier now carries the legal order and the instrument it belongs to: `praxikon:eu:ai-act:obligation:article-11-technical-documentation` instead of the flat form before it. Without those two segments, Article 11 of the AI Act, of the GDPR and of a national implementing act would fight over the same key. The old identifiers keep resolving to exactly the same object, permanently, and every response names the canonical form of what you asked for plus the old form of every object.

    dataset_version
    2.0.0
    schema_version
    1.3.0
    API document
    1.8.0-beta.1

    Read this if you verify by hash

    The payload hash of every object carrying an identifier moved with it: the hash covers the whole payload, and the references sit inside it. Not one statement, source, date or status moved. That is a check rather than a promise: a release guard writes the current payload back into the old namespace and requires every field fingerprint to be exactly what the 1.1.0 snapshot recorded. If you verify by hash, read section 5.8 of the versioning policy.

    Snapshot recorded (417 object versions)

    Compare this release object by object

    praxikon:sys:registry:release:2026-08-13-identifier-namespace

  29. API surface

    Cheap polling, and one error shape

    The two endpoints a consumer is supposed to poll, the dataset description and the OpenAPI document, now carry an ETag and answer `If-None-Match` with a 304, as the graph endpoints already did. Alongside that: a status endpoint at `/api/v1/status` carrying the release, the object counts and the outcome of the last guard run, this changelog, and one error shape across every v1 endpoint. On request limits it now states exactly what is enforced and where nothing applies.

    dataset_version
    1.1.0
    schema_version
    1.2.0
    API document
    1.7.0-beta.1

    Snapshot recorded (417 object versions)

    No per-object comparison. This release did not move the content counter, so there is nothing to compare per object. What moved was the shape of the response or the surface around it, and that is described in the summary.

    praxikon:sys:registry:release:2026-08-13-api-hygiene

  30. API surface

    Whether what moved touches your dossier

    The impact feed at `/api/v1/impact` lays a manifest beside a window in the knowledge layer and reports, per touched object, the ground of the match. Not being able to see is never "no impact": an uncovered window comes back as a recommendation to recompute.

    dataset_version
    1.1.0
    schema_version
    1.2.0
    API document
    1.6.0-beta.1

    Snapshot recorded (417 object versions)

    No per-object comparison. This release did not move the content counter, so there is nothing to compare per object. What moved was the shape of the response or the surface around it, and that is described in the summary.

    praxikon:sys:registry:release:2026-08-13-impact-feed

  31. API surface

    What moved between two reference points, and which half mattered

    The regulatory diff became reachable at `/api/v1/diff`, with the snapshot register underneath it recording which object versions stood published per release. Every response carries the coverage of the recorded history, so an empty diff cannot be read as a quiet period.

    dataset_version
    1.1.0
    schema_version
    1.2.0
    API document
    1.5.0-beta.1

    Snapshot recorded (417 object versions)

    No per-object comparison. This release did not move the content counter, so there is nothing to compare per object. What moved was the shape of the response or the surface around it, and that is described in the summary.

    praxikon:sys:registry:release:2026-08-13-regulatory-diff

  32. API surface

    The dossier over the wire

    The Regulatory Manifest became reachable over HTTP, together with an endpoint that validates a manifest you already hold. Neither stores anything. No object was added and no payload moved, so only the API surface grew.

    dataset_version
    1.1.0
    schema_version
    1.2.0
    API document
    1.4.0-beta.1

    Snapshot recorded (417 object versions)

    No per-object comparison. This release did not move the content counter, so there is nothing to compare per object. What moved was the shape of the response or the surface around it, and that is described in the summary.

    praxikon:sys:registry:release:2026-08-13-manifest-over-http

  33. Shape

    When we last looked, and what we got wrong

    A review status on every object version, kept outside the payload hash so that a recheck cannot invalidate a citation, and a public correction register at `/api/v1/corrections`. Shape moved, content did not: no object added, no version appended, no payload touched, which is why `dataset_version` stayed at 1.1.0.

    dataset_version
    1.1.0
    schema_version
    1.2.0
    API document
    -

    Snapshot recorded (417 object versions)

    No per-object comparison. This release did not move the content counter, so there is nothing to compare per object. What moved was the shape of the response or the surface around it, and that is described in the summary.

    praxikon:sys:registry:release:2026-08-13-review-status-and-corrections

  34. ContentShape

    Who carries the duty, and who is only affected

    Five optional relation fields on the payload, populated on all 25 obligations, plus a `duty_holder` parameter and two supervisory actors. An obligation now states separately who the legal addressee is and who is practically affected, so a query about duties no longer returns duties resting on someone else.

    dataset_version
    1.1.0
    schema_version
    1.1.0
    API document
    -

    Read this if you verify by hash

    The payload hash of 25 obligations moved at an unchanged object version, because the hash covers the whole payload and those five fields were added. No existing field moved and no superseded version was touched. If you verify by hash, read section 5.6 of the versioning policy.

    Snapshot recorded (417 object versions)

    No per-object comparison. A release-to-release comparison needs a recorded snapshot on both sides, and 1.0.0 has none. The snapshot register started at 2026-08-13T00:00:00.000Z; what stood published before that date was not recorded and is not reconstructed after the fact.

    praxikon:sys:registry:release:2026-08-13-relation-model

  35. ContentShape

    First public release

    The implementation graph became public for the first time: published objects on two time axes, a primary source per statement, and a payload hash per object version to verify a citation against. It is also the knowledge date every published version has carried since, and therefore the floor of the knowledge axis.

    dataset_version
    1.0.0
    schema_version
    1.0.0
    API document
    -

    No snapshot. No snapshot is recorded for dataset 1.0.0. The register started at 2026-08-13T00:00:00.000Z and an earlier release cannot be reconstructed after the fact, because its payloads are no longer in the repository. That is a gap in the recorded history, not a statement that nothing moved.

    No per-object comparison. This is the first published release. There is no earlier state of the dataset to compare it against.

    praxikon:sys:registry:release:2026-08-08-first-public-release

What this history cannot show

  • content_releases_without_a_snapshot1.0.0 moved the content counter but has no recorded snapshot. Its payloads are no longer in the repository, so the record cannot be created after the fact. Section 5.6 of the versioning policy describes in words what moved, and that description is all there is.

The three counters

Content
The dataset version. Objects were added, or versions were appended to existing objects. Because the dataset is append only, such a release cannot change what an earlier pinned query returned.
Shape
The schema version. A field added, an endpoint added, a member added to an enum. Existing fields keep their name, their type and their meaning.
API surface
The version of the OpenAPI document. A route was added or a description became more precise. No object was added and no payload moved, so a citation does not have to be re-checked.

What belongs here and what does not

Yes: what we released
Every release of the dataset, of the schema or of the API document, with its date and what moved.
No: a change in the law
When the rules themselves move, that is a change object in the graph with its own source citation, not a release of ours.
No: our own errors
What we got wrong and repaired is in the correction log, with its date and its reason. A release and an error do not belong on the same pile.

For AI agents and integrations

The same history is available machine readable, from the same source as this page. The status endpoint additionally states which release is being served, how many objects it holds, and whether the release guards ran over exactly that content.