LumenClip engineering documentation

This documentation is organized around the five areas maintained alongside the application.

Generation pipelines that transform application inputs into content outputs, including the exact model and provider at generative stages.

Runtime and development dependencies used by LumenClip.

Application data structures, backend architecture, endpoints, and Railway.

Component boundaries, workspace views, pages, and UI primitives.

Scheduling, reminders, publication linking, and queue execution.

Documentation rules

Keep only content-output generation workflows in docs/workflows/. Express each pipeline as ordered transformations with explicit inputs, outputs, branches, validation, and model/provider details.
Keep dependency ownership in docs/libraries/.
Keep persisted shapes and backend contracts in docs/data/.
Keep frontend architecture and product surfaces in docs/ui/.
Keep scheduled execution behavior in docs/jobs/.
Update the relevant document with every material implementation change.

This documentation is organized around the five areas maintained alongside the application.

Generation pipelines that transform application inputs into content outputs, including the exact model and provider at generative stages.

Runtime and development dependencies used by LumenClip.

Application data structures, backend architecture, endpoints, and Railway.

Component boundaries, workspace views, pages, and UI primitives.

Scheduling, reminders, publication linking, and queue execution.

Keep only content-output generation workflows in docs/workflows/. Express each pipeline as ordered transformations with explicit inputs, outputs, branches, validation, and model/provider details.
Keep dependency ownership in docs/libraries/.
Keep persisted shapes and backend contracts in docs/data/.
Keep frontend architecture and product surfaces in docs/ui/.
Keep scheduled execution behavior in docs/jobs/.
Update the relevant document with every material implementation change.