Release Planning & Document History
This section details how the business and software requirements of the Fast Layered Universal Document Engine (Flude) are distributed across developmental release milestones, and tracks the version history of this specification document.
Document Version History
We track the revisions of these specifications using a structured versioning schema:
| Doc Version | Date | Phase Description | Lead Author | Status |
|---|---|---|---|---|
0.4 | 2026-06-11 | Developing documentation | Sir Derryk | Draft (Active) |
0.3 | 2026-06-09 | Developing prototype | Sir Derryk | Approved (Superceded) |
0.2 | 2026-06-08 | Planning MVP | Sir Derryk | Approved (Superceded) |
0.1 | 2026-06-07 | Requirements gathering | Sir Derryk | Approved (Superceded) |
- Version 0.4 Scope: Comprehensive design, planning, and deployment of the hybrid online documentation portal (Flude Portal), including the GHA CI/CD publication workflow (Flude Publisher).
- Version 0.3 Scope: Active core implementation of Python-based Flude prototype according to TDD methodologies (Weeks 1 to 5).
- Version 0.2 Scope: Granular scheduling of 12 TDD tasks across 5 weeks, preparing executable development task specifications, and updating Docusaurus navigation layouts.
- Version 0.1 Scope: Gathering high-level business goals (BRD), defining system functional/non-functional constraints (SRS), drafting the pipeline design (SDD), and mapping out the implementation schedule.
Release Planning Summary
To guarantee a fast, stable, and highly predictable development process, the implementation of Flude is structured into two main releases:
- MVP (v1.0) Release Plan: Focuses on core parsing, AST extraction, CommonMark rendering, push-gating, and complete local execution.
- Future Releases (v2.0+): Introduces AI translation workflows, asynchronous translation lifecycle status databases, XLIFF import/export subcommands, and tree-sitter direct code parsers.