System Requirements Document for cemia-solaire-ia

1. Introduction

CEMIA is a technical-industrial centre whose public story is told through a 90-second French short film. The product defined here is the working environment that produces that film: a protected web surface where the CEMIA Content Creator revises the existing scene-by-scene script (Scenes 1–5 plus the Outro, with their visuals, voice-over and on-screen text) and generates the finished video from the revised script.

The product intent is to turn the authoritative CEMIA script into a revisable, versioned artefact and then into a deliverable video that preserves the script's scene order, stated timings, French narration, on-screen text, and closing credit. The audience for the delivered film is engineers, industrial partners, students and institutional funders; the audience for the product itself is the single accepted active human role, the CEMIA Content Creator.

The film's subject matter is fixed by the source: a galvanized-steel parking ombrière with 37 bifacial solar panels and a 20 kW hybrid inverter, a 30 kWh LiFePO4 battery cabinet, a local AI compute room comparing DGX Spark, RTX 5090 and RTX PRO 6000 Blackwell against a retained architecture of 12 training workstations plus central and flagship stations, the local AI's private capabilities, and the fabrication workshop running from G-code to a finished physical part.

2. System Overview

The system is a first-party web application with application-owned identity. An anonymous visitor can read the public Landing surface explaining CEMIA's solar, local-AI and fabrication capabilities. A creator enrolls through Sign Up or verifies a returning account through Login. Once verified, the creator works in the Script Editor to revise the French scene-by-scene script, in the Video Studio to assemble and generate the short video from that revised script, and in Video Preview to review the generated approximately 1:30 film and decide whether to return to revision or regenerate.

The video generation step consumes the revised script and produces a durable deliverable bound to the creator's account, so the creator can leave and resume. The film itself is French, follows the fixed scene order and timings, and ends with the CEMIA logo, the name of Oussama Baccara and the centre's slogan.

Narrow exclusions: this product does not operate the ombrière, the inverter, the battery, the AI compute room or the workshop machines; those are described subjects of the film, not controllable systems. The product does not provide account administration, roles, permissions, team collaboration, publishing or distribution of the finished video, or any capability beyond revising the script and generating and reviewing the video from it.

2a. Product Interpretation and Delivery Boundary

The accepted work is a two-part deliverable: a revised script and a video generated from it. Both are durable, creator-specific artefacts, so the product owns identity: a creator establishes access through self-service enrollment and verifies a returning account to resume saved scripts, previews and generated videos. The Landing surface is anonymously reachable and carries no protected state; the Script Editor, Video Studio and Video Preview are protected and become usable only after identity is established.

The film's content is bounded by the source script. The product may revise wording, pacing and visual description, but it must preserve the scene order, the stated timings, the French language, the named technical figures, and the closing credit. Nothing in the current scope extends to distributing, publishing or hosting the film for external audiences, and nothing extends to controlling the physical installations the film depicts.

2b. Source Content Inventory

The authoritative content source is the CEMIA short-video script. Its verified factual content is preserved below.

Scene 1 — Énergie Solaire & Parking Ombrière (00:00–00:15)

• Visual: dynamic view of the galvanized-steel parking ombrière with its 37 bifacial solar panels; zoom on the 20 kW hybrid inverter.
• Voice-over / on-screen text: « Tout commence sur le parking : une ombrière solaire de 20 kWc produit jusqu'à 37 000 kWh par an. Raccordée à un onduleur hybride de 20 kW à transfert ultra-rapide (< 10 ms), l'énergie est directement injectée pour alimenter tout le centre. »

Scene 2 — Stockage par Batterie Lithium & Garanties (00:15–00:25)

• Visual: close-up of the LiFePO4 battery storage cabinet and its charge indicators.
• Voice-over / on-screen text: « Pour garantir zéro interruption, la batterie Lithium LiFePO4 de 30 kWh offre plus de 6 000 cycles de recharge et une autonomie d'environ 4 heures. L'installation est bâtie pour durer : 10 ans de garantie sur la structure de l'ombrière et 25 ans de performance sur les panneaux. L'impression 3D et les calculs IA ne s'arrêtent jamais ! »

Scene 3 — Salle IA Locale : Comparaison & Solution Choisie (00:25–00:45)

• Visual: fast animation comparing the cards/servers, then an overview of the training room (12 postes) and the central server.
• Voice-over / on-screen text: « Côté calcul, le CEMIA a comparé toutes les options :
  • Le DGX Spark (128 Go de mémoire unifiée) pour charger de très grands modèles d'IA (70B à 200B) à faible consommation.
  • La RTX 5090 (32 Go) pour la puissance brute de rendu et de création média.
  • La RTX PRO 6000 Blackwell (96 Go ECC) pour la stabilité industrielle 24/7 et la certification ISV. La solution retenue ? Une architecture polyvalente qui combine 12 postes de formation en RTX 5060 Ti / Ryzen 7 9700X, le serveur central DGX Spark et les stations Flagship RTX 5090 et PRO 6000. »

Scene 4 — Rôle & Polyvalence de l'IA Locale (00:45–01:05)

• Visual: screen capture showing the AI generating a 3D model, Python code and G-code, then a video render.
• Voice-over / on-screen text: « Que fait cette IA locale 100 % privée ? Elle assiste la conception mécanique 3D (conversion paramétrique et mises en plan automatique), génère du code de programmation et des scripts Python, exécute des simulations physiques, crée des contenus vidéo et génère directement le G-code pour les machines d'usinage. Tout cela en local, sans Internet et sans fuite de données ! »

Scene 5 — Atelier de Fabrication & Pièce Finie (01:05–01:20)

• Visual: rapid sweep of the workshop: FDM and SLA (8K) 3D printing, CO2 laser cutting, 3D scanner and Haas CNC machining centre.
• Voice-over / on-screen text: « Une fois le G-code prêt, direction l'atelier : imprimantes 3D à filament et résine 8K, découpe laser 90W, scanner 3D haute précision et usinage CNC Haas. Résultat : de l'idée au produit physique fini en quelques heures, sous un seul toit ! »

Outro — Conclusion & Slogan (01:20–01:30)

• Visual: CEMIA logo, the name of Oussama Baccara and the centre's slogan.
• Voice-over / on-screen text: « CEMIA : Souveraineté numérique, autonomie énergétique et excellence industrielle. Élaboré par l'Ingénieur Oussama Baccara & l'Équipe CEMIA. »

2c. Page Content and Component Coverage

Landing

• Information and state: anonymous public entry; presents CEMIA's three capability domains — solar energy and the parking ombrière, the local AI compute room, and the fabrication workshop — using the script's own figures (20 kWc, 37 000 kWh/an, 20 kW inverter with <10 ms transfer, 30 kWh LiFePO4, 6 000+ cycles, ~4 h autonomy, 10-year ombrière structure warranty, 25-year panel performance warranty, 12 postes, DGX Spark, RTX 5090, RTX PRO 6000 Blackwell, RTX 5060 Ti / Ryzen 7 9700X, FDM and SLA 8K printing, 90W CO2 laser, high-precision 3D scanner, Haas CNC). No protected state is shown.
• Primary action: proceed to Sign Up to begin revising the script; a returning creator proceeds to Login.
• Supporting actions: read the capability sections; follow the scene timeline strip as a table of contents for the film's six scenes.
• Domain entities: CEMIA capability domain, scene summary, headline figure.
• Component responsibilities: full-bleed dark hero with the ombrière photograph as ground and the oversized Saira Condensed uppercase headline; a single amber gauge parked at 37 000 kWh/an labelled « PRODUCTION ANNUELLE »; a teal arc reading « 20 kWc · <10 MS »; the squared amber CTA plate « RÉVISER LE SCRIPT » cut into the lower third; the CEMIA wordmark top-left; the persistent 72px left rail carrying vertical scene numbers 01–06 and a thin amber progress arc; ruled instrument plates for every specification figure with a 3px amber or teal category tick.
• States: loading — hero image and gauge arc resolve in place; empty — not applicable, the surface is static content; success — visitor reaches Sign Up or Login; error — hero image fails to load, the dark ground and headline remain legible and the CTA stays operable; recovery — retry the image load without losing the visitor's scroll position.

Sign Up

• Information and state: anonymous enrollment surface; collects the minimum identity information needed to create the creator's account; states that protected script and video work becomes available after enrollment.
• Primary action: submit enrollment to create the account.
• Supporting actions: move to Login if the creator already has an account.
• Domain entities: creator account, credential.
• Component responsibilities: ruled-underline inputs rather than boxed fields; a squared amber submit plate; inline validation messaging in Barlow 600 uppercase micro-labels.
• States: loading — submit plate shows an in-progress state and blocks duplicate submission; empty — fields blank with micro-label hints; success — account created and the creator proceeds to the protected Script Editor; error — invalid or already-used identity information is reported inline against the offending field with the entered values preserved; recovery — correct the field and resubmit without re-entering the rest.

Login

• Information and state: anonymous returning-verification surface; accepts the creator's credentials to restore access to saved scripts, previews and generated videos.
• Primary action: submit credentials to verify the returning account.
• Supporting actions: move to Sign Up if the creator has no account.
• Domain entities: creator account, credential, session.
• Component responsibilities: ruled-underline credential inputs; squared amber submit plate; inline failure messaging.
• States: loading — submit plate shows an in-progress state; empty — fields blank with micro-label hints; success — verified session and the creator resumes at the Script Editor with prior work intact; error — incorrect credentials reported inline without revealing which element was wrong; recovery — re-enter credentials and resubmit.

Script Editor

• Information and state: protected scene-by-scene workspace holding the revised French script; each scene carries its number, its title, its fixed timing chip, its visual description, its voice-over text and its on-screen text. The six scenes are Scene 1 Énergie Solaire & Parking Ombrière (00:00–00:15), Scene 2 Stockage par Batterie Lithium & Garanties (00:15–00:25), Scene 3 Salle IA Locale : Comparaison & Solution Choisie (00:25–00:45), Scene 4 Rôle & Polyvalence de l'IA Locale (00:45–01:05), Scene 5 Atelier de Fabrication & Pièce Finie (01:05–01:20), and the Outro Conclusion & Slogan (01:20–01:30). The scene order and the timing chips are fixed structure, not editable content.
• Primary action: edit a scene's visual description, voice-over text and on-screen text, and save the revised script.
• Supporting actions: select a scene from the ruled scene column; scrub the horizontal timeline strip to move between scenes; read the fixed timing chip for each scene; proceed to the Video Studio to generate the video from the saved script.
• Domain entities: script, scene, timing chip, visual description, voice-over text, on-screen text.
• Component responsibilities: two-pane split with the scene list as a ruled column on the left and the French voice-over text as an editable ruled block on the right; timing chips rendered as amber tabular numerals; the horizontal timeline strip mapping the six scenes as proportional blocks (15s / 10s / 20s / 20s / 15s / 10s) that doubles as the script's table of contents; the persistent left rail with scene numbers 01–06 and the amber progress arc.
• States: loading — scene list and editable blocks populate in scene order; empty — a scene with no revised text shows its source text as the starting value; success — the revised script is saved and the saved state is visible per scene; error — a save failure is reported without discarding the creator's in-progress edits; recovery — retry the save with the edits still present in the editor.

Video Studio

• Information and state: protected assembly workspace that consumes the saved revised script and produces the short video; shows the six scenes with their timings, the narration and on-screen text to be used, and the generation state of the film.
• Primary action: generate the video from the revised script.
• Supporting actions: review the scene-by-scene assembly before generating; return to the Script Editor to revise further; proceed to Video Preview when generation completes.
• Domain entities: revised script, scene, narration track, on-screen text, generated video.
• Component responsibilities: edge-to-edge dark generated-video panel with the film framed inside a thin bezel rather than a floating rounded card; ruled spec rows listing each scene's timing and content source; the timeline strip with the playhead moving linearly and each scene block illuminating its left tick as it activates; a 1px teal scan line crossing once on load and then holding still.
• States: loading — generation progress is shown against the scene sequence; empty — no generation has been run yet, and the workspace shows the saved script ready to generate; success — the generated video is available and the creator is offered Video Preview; error — a generation failure is reported with the failing stage identified and the revised script preserved; recovery — regenerate from the same saved script without re-editing it.

Video Preview

• Information and state: protected review surface for the generated approximately 1:30 video, presented in the fixed scene order with its French narration, on-screen text and the closing credit « Élaboré par l'Ingénieur Oussama Baccara & l'Équipe CEMIA. »
• Primary action: play and review the generated video.
• Supporting actions: return to the Script Editor to revise; return to the Video Studio to regenerate; scrub the timeline strip to inspect a specific scene.
• Domain entities: generated video, scene, timing, closing credit.
• Component responsibilities: the film framed edge-to-edge inside a thin bezel; the timeline strip as scrubber with amber timing chips; the persistent left rail with scene numbers 01–06 and the progress arc tracking the playhead.
• States: loading — the film frame resolves and the teal scan line crosses once; empty — no generated video exists yet, and the surface directs the creator to the Video Studio; success — the film plays through to the outro credit; error — playback failure is reported with a retry that resumes from the current position; recovery — return to the Video Studio to regenerate or to the Script Editor to revise.

3. Functional Requirements

FR-1 — Revise the CEMIA short-video script and produce a video from it (explicit) As a CEMIA Content Creator, I should revise the existing CEMIA short-video script covering Scenes 1–5 and the Outro, and produce a video from the revised script, so that the centre has an updated film presenting its solar, local-AI and fabrication capabilities.

• Trigger/input: the creator opens the protected Script Editor with the existing script loaded.
• Observable result: a saved revised script and a generated video produced from it.
• Access state: protected; requires a verified creator account.
• Failure/recovery: if saving or generation fails, the revised script is preserved and the creator can retry.
• Continuation: the creator reviews the generated video in Video Preview and either accepts it or returns to revise.

FR-2 — Preserve the scene structure and timings (explicit) As a CEMIA Content Creator, I should have the video follow the script's scene structure and timing — Scene 1 solar energy & parking ombrière (00:00–00:15), Scene 2 lithium battery storage & guarantees (00:15–00:25), Scene 3 local AI room, comparison & chosen solution (00:25–00:45), Scene 4 role & versatility of local AI (00:45–01:05), Scene 5 fabrication workshop & finished part (01:05–01:20), Outro conclusion & slogan (01:20–01:30) — so that the film matches the approved running order and ends at approximately 01:30.

• Trigger/input: the creator generates the video from the revised script.
• Observable result: the generated video presents the six scenes in the stated order with the stated timings and a total length of approximately 01:30.
• Access state: protected.
• Failure/recovery: if a scene's timing or order is violated, the generation is reported as failed against the offending scene and the creator can correct the script and regenerate.
• Continuation: the creator reviews the correctly ordered film in Video Preview.

FR-3 — Scene 1 content: solar energy and the parking ombrière (explicit) As a CEMIA Content Creator, I should be able to revise and generate Scene 1 showing the galvanized-steel parking ombrière with its 37 bifacial solar panels and a zoom on the 20 kW hybrid inverter, with voice-over and on-screen text stating that a 20 kWc solar ombrière produces up to 37 000 kWh per year and that, connected to a 20 kW hybrid inverter with ultra-fast transfer (< 10 ms), the energy is injected directly to power the whole centre, so that the film opens on the centre's energy source.

• Trigger/input: the creator edits Scene 1's visual description, voice-over and on-screen text in the Script Editor.
• Observable result: Scene 1 in the generated video carries the ombrière and inverter visuals and the stated figures.
• Access state: protected.
• Failure/recovery: if the scene's figures are altered or dropped, the creator can restore them from the source text and regenerate.
• Continuation: the film proceeds to Scene 2.

FR-4 — Scene 2 content: lithium battery storage and guarantees (explicit) As a CEMIA Content Creator, I should be able to revise and generate Scene 2 showing a close-up of the LiFePO4 battery storage cabinet and its charge indicators, with voice-over and on-screen text stating that the 30 kWh LiFePO4 lithium battery offers more than 6 000 recharge cycles and about 4 hours of autonomy for zero interruption, that the installation carries a 10-year warranty on the ombrière structure and a 25-year performance warranty on the panels, and that 3D printing and AI calculations never stop, so that the film establishes continuity of supply and durability.

• Trigger/input: the creator edits Scene 2's visual description, voice-over and on-screen text in the Script Editor.
• Observable result: Scene 2 in the generated video carries the battery cabinet visuals and the stated figures and warranties.
• Access state: protected.
• Failure/recovery: if the scene's figures are altered or dropped, the creator can restore them from the source text and regenerate.
• Continuation: the film proceeds to Scene 3.

FR-5 — Scene 3 content: local AI room comparison and chosen solution (explicit) As a CEMIA Content Creator, I should be able to revise and generate Scene 3 with a fast animation comparing the cards/servers followed by an overview of the training room (12 postes) and the central server, with voice-over and on-screen text presenting the comparison — DGX Spark (128 Go de mémoire unifiée) for loading very large AI models (70B to 200B) at low consumption; RTX 5090 (32 Go) for raw rendering and media-creation power; RTX PRO 6000 Blackwell (96 Go ECC) for 24/7 industrial stability and ISV certification — and stating that the retained solution is a versatile architecture combining 12 training workstations on RTX 5060 Ti / Ryzen 7 9700X, the central DGX Spark server and the Flagship RTX 5090 and PRO 6000 stations, so that the film explains the compute decision.

• Trigger/input: the creator edits Scene 3's visual description, voice-over and on-screen text in the Script Editor.
• Observable result: Scene 3 in the generated video carries the comparison and the retained architecture with all stated specifications.
• Access state: protected.
• Failure/recovery: if a compared option or the retained architecture is altered or dropped, the creator can restore it from the source text and regenerate.
• Continuation: the film proceeds to Scene 4.

FR-6 — Scene 4 content: role and versatility of the local AI (explicit) As a CEMIA Content Creator, I should be able to revise and generate Scene 4 with a screen capture showing the AI generating a 3D model, Python code and G-code and then a video render, with voice-over and on-screen text stating that the 100 % private local AI assists 3D mechanical design (parametric conversion and automatic drawing generation), generates programming code and Python scripts, runs physical simulations, creates video content and generates G-code directly for machining machines, all locally, without Internet and without data leakage, so that the film states what the local AI does and why it is private.

• Trigger/input: the creator edits Scene 4's visual description, voice-over and on-screen text in the Script Editor.
• Observable result: Scene 4 in the generated video carries the listed AI capabilities and the local, no-Internet, no-data-leakage statement.
• Access state: protected.
• Failure/recovery: if a listed capability or the privacy statement is altered or dropped, the creator can restore it from the source text and regenerate.
• Continuation: the film proceeds to Scene 5.

FR-7 — Scene 5 content: fabrication workshop and finished part (explicit) As a CEMIA Content Creator, I should be able to revise and generate Scene 5 with a rapid sweep of the workshop — FDM and SLA (8K) 3D printing, CO2 laser cutting, 3D scanner and Haas CNC machining centre — with voice-over and on-screen text stating that once the G-code is ready the work goes to the workshop with filament and 8K resin 3D printers, 90W laser cutting, a high-precision 3D scanner and Haas CNC machining, and that the result is from idea to finished physical product in a few hours under one roof, so that the film closes its production story.

• Trigger/input: the creator edits Scene 5's visual description, voice-over and on-screen text in the Script Editor.
• Observable result: Scene 5 in the generated video carries the workshop equipment list and the idea-to-finished-product outcome.
• Access state: protected.
• Failure/recovery: if a listed machine or the outcome statement is altered or dropped, the creator can restore it from the source text and regenerate.
• Continuation: the film proceeds to the Outro.

FR-8 — Outro content: logo, credit and slogan (explicit) As a CEMIA Content Creator, I should be able to revise and generate the Outro showing the CEMIA logo, the name of Oussama Baccara and the centre's slogan, with the voice-over and on-screen text « CEMIA : Souveraineté numérique, autonomie énergétique et excellence industrielle. Élaboré par l'Ingénieur Oussama Baccara & l'Équipe CEMIA. », so that the film ends with the required attribution.

• Trigger/input: the creator edits the Outro's visual description, voice-over and on-screen text in the Script Editor.
• Observable result: the generated video's final scene carries the CEMIA logo, the name of Oussama Baccara and the exact slogan and credit.
• Access state: protected.
• Failure/recovery: if the credit is altered or dropped, the creator can restore it from the source text and regenerate.
• Continuation: the film ends; the creator reviews it in Video Preview.

FR-9 — French language throughout (explicit) As a CEMIA Content Creator, I should have the video remain in French, matching the script's voice-over and on-screen text, so that the film addresses its intended audience in the source language.

• Trigger/input: the creator generates the video from the revised script.
• Observable result: all narration and on-screen text in the generated video is in French.
• Access state: protected.
• Failure/recovery: if non-French text appears, the creator can correct the script and regenerate.
• Continuation: the creator reviews the French film in Video Preview.

FR-10 — Self-service enrollment before protected work (required_inference) As a CEMIA Content Creator, I should be able to enroll myself through Sign Up before creating protected script and video work, so that my revised scripts and generated videos belong to my own account.

• Trigger/input: the creator chooses to begin protected work from the Landing surface.
• Observable result: a creator account exists and the protected Script Editor becomes available.
• Access state: anonymous entry on Sign Up; protected destinations remain unavailable until enrollment completes.
• Failure/recovery: invalid or already-used identity information is reported inline and the creator can correct it and resubmit.
• Continuation: the creator proceeds to the Script Editor.

FR-11 — Returning verification before resuming saved work (required_inference) As a CEMIA Content Creator, I should be able to verify my returning account through Login before resuming saved scripts, previews or generated videos, so that my prior work is restored to me.

• Trigger/input: the creator returns and chooses to resume protected work.
• Observable result: a verified session restores the creator's saved scripts, previews and generated videos.
• Access state: anonymous entry on Login; protected state becomes available only after verification.
• Failure/recovery: incorrect credentials are reported inline and the creator can re-enter them and resubmit.
• Continuation: the creator resumes at the Script Editor with prior work intact.

**FR-12 — Generation uses the revised script and preserves order, tim