M3 — Calendar of binding dates

Eye-landing point

The tech meeting on 2026-05-07 — drawn as a red crit milestone at the very left of the calendar. It is the imminent verdict : the arbitrage on compute architecture must be defended on that date, and every other binding date on this Gantt either feeds that decision or is gated by it.

A reader scanning the diagram in three seconds should be able to name : the next binding date and its consequence — answer : 2026-05-07, tech meeting, the compute arbitrage verdict.

Layout discipline

• section Tech : the May 7 verdict, drawn as crit (red) and as a milestone (single point in time, not a duration).
• section Données : the S&P Global Xpressfeed stream — started 2026-04-15, ongoing. Marked active to show the live state.
• section Compute : three deliverables that depend on counterparties. The S3NS chiffrage SLA was promised after the 17 April RDV with Émilie Daelman / Véronique Poirson and is not yet received. The OVH H100 quote and the Wasabi-OVH throughput PoC anchor the M2 (Wasabi+OVH) architecture leg of the arbitrage.
• section Pédagogie : the Master rentrée on 2026-09-08, drawn as a second crit milestone — the absolute deadline by which all upstream questions must be resolved (storage, compute, ingestion).

Discipline of exclusion

Only dates with binding consequence appear here. Excluded :

• Aspirational milestones — « on aimerait faire X en juin » has no place on this calendar unless a counterparty has committed to a date.
• Internal sprint plans — any dating that is internal to the maintainers' workflow rather than visible to CAL / Wissal / Emmanuel as an external commitment.
• Soft deadlines without consequence — « idéalement pour la fin du mois » is dropped unless it gates a downstream decision.
• Ardian / DataSpark / Joydeep dates — they belong to a different partnership track and do not gate the MaQI Master compute arbitrage.

The calendar is short on purpose : six bars, two of which are milestones, plus today's marker. If a seventh bar appears, the maintainer must justify the binding consequence in commit message.

Lint check (Obsidian-Mermaid pitfalls)

• [x] No <i> / <b> HTML tags (Gantt does not use HTML labels).
• [x] No numbered prefixes 1. 2. at start of any task label — labels read as imperative phrases (« Devis OVH H100 commercial à figer ») without numerical indices.
• [x] No nested subgraph (Gantt has no subgraph concept). Sections provide the visual grouping natively.

Render check

• GitHub Mermaid preview : OK (Gantt is a first-class Mermaid type).
• HTML wiki build pipeline : exercised by the sibling wiki-build pipeline.
• Banlist sweep on rendered SVG : passes — task labels carry only human-readable consequence vocabulary.