v1.1.0 — Multi-Entity Joint Deployer Reference

What is new

Contract First extends the single-deployer Article 10 mapping (v1.0.0) with the multi-entity joint deployer pattern. Single-deployer YAML breaks the moment a subsidiary runs a platform the parent procured. v1.1.0 ships the structure that handles it.

Added

• contracts/energy_balance_v0.5_multi_entity.yaml — joint deployer reference contract with deployer_arrangement, per-entity Article 3(8) authority analysis, and Article 26 obligation matrix
• docs/multi-entity-pattern.md — full pattern document covering the dilution problem, the CJEU analogy (C-210/16, C-25/17, C-40/17), the four-block composable pattern, SQL implementation, three twelve-month failure modes, and limitations
• .github/ISSUE_TEMPLATE/multi_entity_correction.md — issue template for joint-deployer YAML corrections
• README "Multi-Entity Implementation" section with CJEU triology reference

Changed

• Regulatory timeline corrected throughout repository: Annex III enforcement 2 December 2027 (extended from 2 August 2026 via Digital Omnibus), Annex I enforcement 2 August 2028
• Narrative shifted from "August 2026 enforcement" to "runway not relief" framing
• CITATION.cff bumped to 1.1.0 with multi-entity keywords

Legal grounding

The joint deployer doctrine rests on three CJEU joint controllership cases applied by analogy: Wirtschaftsakademie Schleswig-Holstein (C-210/16), Jehovah's Witnesses (C-25/17), and Fashion ID (C-40/17). The principle survives translation: authority plus decision rights equals joint deployer status under AI Act Article 26.

Audience

Senior architects at group structures preparing the multi-entity case. Privacy and compliance officers who need technical artifacts not policy PDFs. Consultants building governance practices for mid-market clients with subsidiary structures.

Not legal advice

The CJEU analogy is doctrinal reasoning, not a substitute for qualified counsel review of a specific organisational structure. Consult a qualified lawyer for AI Act compliance opinions.

v1.0.0 - Eight weekends. Full Article 10 mapping. Ship.

The full v1.0.0 release of Contract First.

What this release contains

• Complete EU AI Act Article 10 mapping for all 8 sub-clauses — see docs/article-10-mapping.md
• Full 8-weekend build-in-public journey, documented
• 39.5M source rows → 20.7M fact table, star schema with 6 dimensions
• 24 automated quality tests, all passing
• 9 DAX measures serving 7 Power BI pages
• YAML data contract v0.4 with GDPR Article 30 and data lineage
• Custom Power BI theme with colorblind-safe teal palette

Who should care

• Data engineering leads preparing for August 2, 2026 enforcement
• Privacy officers who need technical artifacts, not policy PDFs
• Consultants building governance practices for SME clients
• Anyone who has asked "what does Article 10 compliance actually look like in code?"

Highlights from the build

• 46% of Eurostat source data is structurally missing. Treating NULLs as zeros overestimates totals by 88%. Quality tests catch this.
• Germany renewable energy: 10.8x growth from 1990 to 2024, demonstrated with a 5-line SQL query and zero DAX.
• Star schema eliminated ~40 DAX measures that a flat model would require.

What is next

• April 21–May 12: EU AI Act deep-dive series (weekly)
• Updates to article-10-mapping.md when Digital Omnibus trilogue concludes (April 28)
• Case studies from implementation engagements (Q2–Q3 2026)

Full changelog: see CHANGELOG.md

If this project saved you time on Article 10 research, a star helps others find it.