How to work with MYEQ
A practical operating manual for Skills, Storyboard, Production Entities, Assets, generation, QA, repair and the Editor. The same method applies whether you use Studio directly or automate through the API/MCP.
01 · First-use guides
Production starts before generation
Define the Workspace context, at least one Skill and the project intent before spending credits. MYEQ works best as a production system, not a prompt box.
- Define → Plan → Generate → Verify → Correct → Approve.
- Guides work even when your credit balance is zero.
- Generated work is not the same as approved work.
02 · First-use guides
Teach MYEQ how your team works
Create at least one Skill with your method, visual language or delivery rules. Strong Skills reduce repeated prompting and improve consistency.
- Start with one real Skill, not an empty placeholder.
- Recommended: method, visual language and delivery rules.
- Workspace Skills can establish shared production standards.
03 · First-use guides
Turn the brief into scenes
Use Script to define narrative, dialogue, rhythm and scene structure. Identity continuity still belongs to Production Entities and references.
- Write the story before expensive generation.
- Keep dialogue and scene intent explicit.
- Use Storyboard to turn script intent into shots.
04 · First-use guides
A scene is more than a prompt
Storyboard should make action, camera, duration, references and audio intent explicit before generation.
- Select and configure each scene deliberately.
- Bind durable entities and references before critical generations.
- Generate only when the scene is ready.
05 · First-use guides
Use @mentions for durable identity
The Production Bible stores characters, avatars, locations, products and other entities. Use @handles whenever identity or continuity matters across scenes.
- @hector refers to the stored entity, not just the word “Hector”.
- Use @locations, @products and @wardrobe when they recur.
- Fix unknown or ambiguous handles before generation.
@hector enters @black-office carrying @red-case
@product-x remains centered on @marble-table06 · First-use guides
Assets are production evidence
Use Assets to upload, inspect and reuse references, generated media and source material. Reuse approved references instead of describing them again from memory.
- Prefer durable references over repeated prose.
- Attach an asset to the correct scene role.
- Keep source media and generated candidates distinguishable.
07 · First-use guides
Select a scene to edit it
Click a scene in the timeline or canvas to work at scene level. Use targeted operations instead of regenerating accepted work unnecessarily.
- Select the scene before editing its prompt or media.
- Use Retake or another local repair when the defect is local.
- Review the final cut before approval.
QA, repair and approval
Generation produces candidates. QA checks them. Repair changes only what failed. Approval is the accountable final decision.
Do not regenerate accepted work simply because one local defect exists. Prefer the smallest valid repair.
- Check identity, continuity, composition, audio, motion and stability.
- After a material repair, re-check any approval that depended on the previous version.
- Generated ≠ Certified.
Voice replication: own voice or explicit authorization only
MYEQ Character Voice requires a real reference recording and explicit consent. Reference and authorization duration limits depend on the active Character Voice enrollment flow; follow the limits shown in Studio.
Upload your own voice by default. Only use another person’s voice when you have explicit authority to do so and the required consent can be recorded.
- Do not upload a third-party voice merely because it is publicly available.
- The voice sample establishes vocal identity; text alone does not.
- Consent and lawful use remain the user’s responsibility.
Understand generation errors before retrying
A useful error should tell you what happened, whether retrying makes sense and what you can change. Provider names and raw stack traces are implementation detail, not the primary user message.
AUTO can choose among available production technologies only when the runtime supports and certifies that route. A route change should be explicit in the UI; never assume a silent fallback occurred.
- Policy/input problem: change the request or source material.
- Rate limit/temporary outage: retry only when the interface marks it retryable.
- Reference problem: replace or repair the reference instead of repeating the same generation.
- Billing problem: add usable credit balance before paid execution.
Credits and managed production packs
MYEQ’s current commercial model is not a monthly or annual software subscription. Self-service generation uses pay-as-you-go credits / available balance.
Separately, MYEQ can sell managed audiovisual production packs in which the MYEQ production team creates and delivers the agreed videos. Those packs are production services, not recurring software subscriptions.
- Credits authorize self-service paid generation.
- Managed packs have their own scope, deliverables and commercial terms.
- Documentation never converts a managed service pack into software entitlement.