Commit Graph

6 Commits

Author SHA1 Message Date
Z User
fa764ec933 Full look every scene; 'nude' for uncovered body parts, never 'bare'
H3 needs every aspect of the look restated per scene, and uncovered
skin is steered by the skin-state word 'nude' (tank-top with nude
arms), not 'bare'. Added to both prompts' subject anchor + craft
rules + self-checks and SKILL.md; the validator prints a non-blocking
note when a description line uses 'bare'.
2026-10-29 23:18:56 +00:00
Z User
405386a1af Decompose every action into body mechanics (H3 drift rule)
Compressed outcome verbs ('picks up the ball') leave H3 nothing to
animate between start and end poses, so it guesses and drifts off
intent. The craft rules in both prompts and SKILL.md now require the
ordered joint-level sequence with the hand/limb named per step.
2026-10-29 22:46:12 +00:00
Z User
df8df95d39 User-approved scene guide is a mandatory workflow step
Encoded the intended user flow end to end: story + scene count ->
scene guide (outline.json) -> USER APPROVAL (hard stop, changes applied
to the guide first) -> scenes composed one at a time (~10s each) from
the approved guide -> continuity verified across the handoff chain ->
final plan.json.

SKILL.md: goal line states the five moves; new Step 2 'Present the
guide for approval (do not skip)' — plain-language presentation, STOP
and wait, approved guide is the contract; Step 3 works only from the
approved guide; Step 4 renamed 'Verify the continuity, put it all
together'; revising section split into guide-level vs single-scene.

README: workflow reframed as 4 stages with Stage 2 = approval (human in
the loop, never skipped); example gains a real guide-presentation +
'Approved — go' exchange between outline and scene writing; steps
renumbered.

Scene-agent prompt: stage table gains the Approval row and a 'Stage 2 is
a hard stop' note; assembler prompt re-labeled Stage 4. Suite + --check
green.
2026-10-29 19:28:18 +00:00
Z User
f5575fa678 Scene composition is the gate, not word counts
The skill exists so the LLM writes/rewrites each scene one at a time
with full attention on making it a complete scene composition — not so
it can hit a word target.

Prompts: the word-budget craft bullets are replaced by an 8-element
composition checklist (subject anchor, style anchor, continuity anchor,
blocking, camera, performance, physical texture, exit state) in both the
scene-writer PROMPT B (new SCENE COMPOSITION section) and the single-pass
prompt. Chase the elements, never a number; padding is as much a failure
as a thin one-liner.

Validator: hard word bands (<10s: 150-200, >=10s: 200-300) removed from
plan and fragment checks. Replaced by a thin-scene floor (100/120 words)
that only trips lazy output, plus a new continuity-anchor check — chained
fragments must open inside the previous end_state. No target band, no
upper limit; output lines say so.

SKILL.md/README: goal, Step 2, craft rules, table rows, and example
outputs updated to match. Suite, --check, chained fragment checks all
green.
2026-10-29 19:13:27 +00:00
Z User
83cc5145bf Realign: one plan JSON, written one scene at a time
The deliverable is the single merged plan.json — the same shape the
single-pass system prompt emits — and the multi-clip video is what the
node itself produces from it: each shot renders as its own clip, chained
through the H3 context loop into one continuous video. Removed the
--clips per-scene export (external stitching is NOT the design).

Workflow restated everywhere: outline turn -> the LLM writes each scene
one at a time (one focused turn per scene) -> build_plan.py puts it all
together at the end into plan.json -> paste once, queue once.

build_plan.py: --clips option and export block removed; docstring now
describes the node-side chaining. README: intro/example/validating/
wiring rewritten around the single deliverable. SKILL.md: goal, Step 3
(Put it all together at the end), Step 4 (the node makes the multi-clip
video), and the revising loop updated. Suite + --check green.
2026-10-29 19:00:11 +00:00
Z User
bd50b1ba51 Add H3 plan-JSON gate: agent workflow prompts, validator, assembler, examples
- h3_scene_agent_system_prompt.md: outline turn + one-scene-per-turn writer
  with a truthful _handoff chain (style_and_cast frozen at outline)
- h3_plan_assembler_system_prompt.md: verbatim-copy LLM merge step
  (deterministic alternative: build_plan.py)
- h3_plan_json_system_prompt.md: single-pass variant for short 2-4 scene
  stories; prompt_prefix fixed to [""], native H3 three-line shot template
- verify_plan_rules.py: node-replica validator (plan + fragment modes,
  handoff-chain checks, embedded pass/fail suite)
- build_plan.py: deterministic fragment merger with --check for existing plans
- h3_agent_workflow_examples/: worked 3-scene greenhouse courier run
  (outline -> 3 fragments -> validated plan.json, 1042 frames = 43.42s)
2026-10-29 17:18:28 +00:00