Babulus — Roadmap (Alpha → Beta)
Audience: mixed (technical + non-technical)
Status: Alpha
What Alpha is
Alpha is about proving the end-to-end loop is real and reliable:
- edit → generate → preview → render → publish
- deterministic outputs (approvals mean something)
- cost control (iteration doesn’t burn quotas)
- security boundaries hold (multi-tenant isolation)
What we consider “done” for Alpha
- A user can create a project, edit a video, generate assets, preview reliably, render a final MP4, and publish/share it.
- The system remains portable: projects are files/folders, artifacts are inspectable.
- It works repeatedly, not just once.
Current priorities (Alpha gates)
Gate 1 — Generation reliability
Generation is the heart of making preview meaningful. The system needs to reliably produce:
- voiceover audio segments
- script/timeline artifacts
- consistent storage of outputs for preview
Gate 2 — Render pipeline
To be publish-ready, Babulus needs a reliable path to MP4 outputs (frames + encoding) that can run as a worker job.
Gate 3 — Publishing verification
Publishing should produce stable shareable outputs (URLs + access policy). The focus is verification and polish, not adding new complexity.
Beta shape (after the loop is reliable)
Once the alpha loop is stable, beta is about speed and ergonomics—without breaking the “DNA”:
- Live preview from source: reduce the “generate to see changes” loop time.
- Import resolution: make
_*.babulus.xmlutilities first-class in projects. - Better approval workflows: operationalize “autonomy with gates”.
- Local folders + sync: enable a desktop/local workflow that mirrors the cloud folder model.
- Publishing integrations: distribute and track outcomes, then feed them back into topic selection and iteration.
Longer-term direction
- A production-grade agent loop that runs continuously with minimal supervision.
- A portable project format that can move between cloud, local, and teams.
- A publishing engine that turns outcomes into better future drafts.