Native reference path
A Desktop-uploaded photo, product or logo stays tenant-bound, passes governed reference admission, and can be relayed through a short-lived secure URL to an eligible native reference input or frame-reference path.
ILAIOS Video / Media Factory
A media lifecycle that remains controlled from references to delivery.
Video / Media Factory coordinates the content-production chain while keeping validation, evidence, recovery, publishing side effects, and cost controls explicit.
Video / Media Factory at a glance
Turn references into a reviewable, verified media target.
The visual describes the target production path. A “verified video” label means required acceptance checks must pass for that exact artifact; it is not a promise that every external generation route is currently available.
Target workflow: request → analyze references → produce → verify → deliver. External generation and publishing remain separately evidence-gated.
Native reference & identity consistency
Use real photos and brand assets to preserve people, products and logos across generated video.
In developmentAuthenticated reference upload/binding and reference-aware conditioning exist in the repository; native signed relay, direct provider-reference delivery, full consistency QA and live certification remain separately evidence-gated.
The public experience stays simple: attach a reference and describe the outcome. Provider-specific input-reference and frame-image contracts remain behind the governed product boundary.
Identity & product consistency QA
Generated video is checked against the admitted references so supported visual identity, subject appearance, product geometry, colors, materials and marks do not silently drift.
Strict logo fidelity
Native reference comes first. Logo consistency QA follows. If a logo must remain exact, the strongest target is deterministic original-asset lock/overlay or compositing, then final QA on the exact rendered artifact.
Target governed chain
Reference → secure relay → native conditioning → generation → consistency QA → logo asset-lock when required → final QA & evidence.
Real generation, CI and live production certification must prove the exact provider path and final artifact before this capability is promoted beyond its evidence-backed maturity.
This page describes the canonical workflow plus the current bounded repository truth. It does not claim that every external provider, publishing destination, or media format is generally available today.
01
Topic & research
Start from a defined content goal, gather relevant research, and preserve source context where the workflow depends on factual claims.
02
Content & script planning
Turn the brief into a structured content plan, script, continuity constraints, and acceptance requirements.
03
Scene & shot planning
Break the script into scenes and shots with duration, composition, continuity, asset, and generation requirements.
04
Asset & execution planning
Plan uploaded/generated assets, rights/provenance, quality/cost thresholds and eligible execution resources inside policy.
05
Media, voice & audio
Acquire or generate visual media, voice, audio, and captions through bounded job steps.
06
Assembly & rendering
Compose the media artifact, render through the admitted technical profile, and retain artifact identity.
07
Technical & content validation
Check media properties, continuity/content requirements, policy and rights constraints, and required acceptance criteria before approval.
08
Approval & platform adaptation
Where required, obtain approval and prepare platform-specific format, metadata, cover/thumbnail, disclosure, and scheduling data.
09
Publish & verify
Publishing is a side effect: use idempotency, rate-limit handling, delivery verification, duplicate prevention, and post-publish checks.
10
Evidence, metrics & recovery
Retain provenance, validation, delivery state, cost, retry/recovery context, and metrics without treating provider-reported success as final proof.
Provider-independent by design
Execution resources can change without becoming the source of workflow authority.
The public product experience does not require users to choose a provider. Eligibility, policy, cost and quality remain governed behind the product boundary.