One coherent way to inspect, plan, transform, validate, and explain content.
Flow is the suite and future orchestration layer for Ego Hygiene's independently useful Rust tools:
| Holon | Owns | Does not own |
|---|---|---|
| Aniflow | Time-based video decomposition, ordered processing, reconstruction, and temporal validation | Collection optimization or general document rendering |
| Optiflow | Local inventory, evidence-backed relationships, safe optimization plans, and collection normalization | Video-frame processing or transform-graph execution |
| Renderflow | Spec-driven transform graphs and publication-ready document, image, and audio derivatives | Collection policy or temporal video reconstruction |
| Flow | Cross-holon planning, compatibility, execution state, provenance, validation, recovery, and suite experience | Reimplementing a holon's specialized engine |
Each holon remains usable as both a Rust library and a standalone CLI. Flow may compose them through stable public library interfaces or versioned CLI contracts, without introducing direct dependencies between sibling holons.
This repository is currently architecture-first. It intentionally contains no copied holon source or working orchestrator yet. The approved suite boundaries, dependency directions, and first orchestration slice are recorded in the roadmap and integration contracts.
- Architecture map
- Suite system model
- Suite structural architecture
- Decision index
- Suite boundaries
- Versioned contracts
- Roadmap
The .agents/ directory contains the repository-local Aether specifications,
skills, agents, templates, and validators used to maintain these documents.
Flow is in the contract and adapter definition phase. Current descriptions of Aniflow, Optiflow, and Renderflow are grounded in their default branches as inspected on 2026-08-13. The holons remain independently released repositories; Flow will compose named releases through public libraries or versioned CLI contracts and will not import sibling source.
MIT