Skip to content

t27f token_floor: drone flights instead of hard cuts, text in the platforms' safe zone, a marketing clock (Closes #10469) - #10471

Merged
gHashTag merged 6 commits into
masterfrom
claude/token-floor-flights
Oct 18, 2026
Merged

gHashTag merged 6 commits into
masterfrom
claude/token-floor-flights

Conversation

@gHashTag

Copy link
Copy Markdown
Owner

Closes #10469

The owner watched the reels from #10451 and said three things: the text runs over itself, the transitions are too jerky (the camera should fly like a drone, the way the effects in The Matrix move), and the reel should work as marketing too. This PR answers all three in t27.

What changes

  • reel_marketing.t27 (new). The practice of 2026 short-form reels as tested numbers, sources in the header:
    • the overlay margins of seven measured sources (TikTok, Instagram Reels, all three platforms) and a safe rect taking the widest margin of every edge: x 130..920, y 260..1436 of 1080x1920;
    • the hook clock: the voice by 500 ms, the statement written by 1000 ms, the 3 s decision window;
    • a new picture at least every 3 s;
    • the CTA held still for at least the last 1.5 s, at 64 px type or more;
    • 15 to 30 s length.
  • token_floor_scenes.t27. The hard cuts become flights:
    • each shot after the first opens with a quintic Hermite in ln z and one in the screen px the centre sweeps, matching both drifts in position and speed;
    • a long flight pulls back in proportion to the distance flown, and the whole reel hovers slightly;
    • the shots are re-timed so each narration beat lands inside its flight;
    • the tall layout is moved inside reel_safe.
  • token_floor.t27. A label the camera carries out of the scene's safe rect now fades out whole. It is no longer drawn half under the card or cut by the frame's edge.
  • token_floor_mux.t27. New tests check the hook, the CTA, the beats inside the flights and the captions in the safe zone against reel_marketing.
  • Two of master's reds from t27f token_floor: PBR gold balls, a story of shots with spec cards, tall and wide cuts from one world (Closes #10451) #10452, fixed at their cause:

Measured (Railway lab)

  • t27c test-report: 0 FAIL and 0 vacuous on all five specs (reel_marketing 3, pbr_sphere 13, token_floor_scenes 14, token_floor_mux 16, token_floor 35).
  • Camera: the worst shove is 20.1 px/frame^2 tall and 19.9 wide, against a bound of 24. The fastest glide is 164.7 / 155.0 px/frame, against a bound of 200. A hard cut would throw the picture by more than 300, and that probe bites.
  • Both reels are 15.000 s at 30 fps (1080x1920 and 1920x1080), with integrated loudness -14.0 LUFS.
  • The four TF_CUT=0 shards concatenated equal the tall cut of the one-process render, byte for byte. That holds both before and after the clamp01 dedupe (same sha).
  • All five seals were rewritten by t27c seal --save, and each spec_hash matches its spec.

Not claimed

The marketing numbers are a floor drawn from vendor and creator guides, not any platform's published law, and not a forecast of reach.

🤖 Generated with Claude Code

…tforms' safe zone, a marketing clock (Closes #10469)

The owner on the #10451 reels: the text runs over itself, the transitions
are too jerky (fly like a drone camera, as in The Matrix), and the reel
should work as marketing.

- reel_marketing.t27 (new): seven measured overlay sources and the safe
  rect taking the widest margin of each edge, the hook clock, the reset
  window, the CTA hold and size, the 15-30 s length; sources listed.
- token_floor_scenes: each shot after the first opens with a flight -- a
  quintic Hermite in ln z and one in the screen px the centre sweeps,
  matching the drifts at both ends, a pull-back for long flights and a
  hover. Worst shove 20.1 px/frame^2 tall, 19.9 wide (bound 24); a hard
  cut would throw it more than 300. Tall layout inside reel_safe.
- token_floor: a label leaving the scene's safe rect fades whole.
- token_floor_mux: hook, CTA and safe-zone tests against reel_marketing.
- clamp01 written once (pbr_sphere), so duplicate-bodies is green; the
  t27b ledger names pbr_sphere (pass) and token_floor (blocked, type
  [N]T), cap 74 -> 75 for the one new non-pass spec.

Lab: test-report 0 FAIL, 0 vacuous on all five; seals rewritten; both
reels 15.000 s at -14.0 LUFS; four tall shards equal the full render.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-18 13:40:51 UTC

Summary

Status Count
Total Open PRs 50
PRs with Failing Checks 50
PRs with All Checks Green 0
READY 0
FAILING 50
PENDING 0
NO CHECKS YET 0

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=fad12492937a != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

gHashTag and others added 2 commits October 18, 2026 21:02
…7b ledger from #10473

Master's ledger (re-measured at 7552b89) still lists this branch's specs as master had them.
The resolution keeps master's ledger and records what this branch changes:
- reel_marketing.t27 is new and passes;
- token_floor_scenes.t27 now calls @sin (the hover), and token_floor_mux.t27 uses it, so both are
  blocked on ExprCall(@sin), unimplemented, as CI's run of the merge head measured;
- max_not_pass 130 -> 132 for those two.

Refs #10469

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…amp01 dedupe, keep this branch's side

Refs #10469

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-18 14:12:37 UTC

Summary

Status Count
Total Open PRs 50
PRs with Failing Checks 49
PRs with All Checks Green 1
READY 0
FAILING 49
PENDING 0
NO CHECKS YET 0

These columns do not partition: 0 + 49 + 0 + 0 = 49, and there are 50 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=fad12492937a != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

…#10474

#10474 rewrote auto-merge-ready-prs.yml so the merger runs as TRI CLAW on
workflow_run; the rewrite added two run: steps (both handed to bash by the
runner, 299 -> 301) and six steps that name a path without a quiet shape.
Master's cli-tri went red on that merge; blessed with tri census pin --bless
at master 6070e9b on the lab, byte-identical.

Refs #10469

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-18 14:15:47 UTC

Summary

Status Count
Total Open PRs 50
PRs with Failing Checks 50
PRs with All Checks Green 0
READY 0
FAILING 50
PENDING 0
NO CHECKS YET 0

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=fad12492937a != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

gHashTag and others added 2 commits October 18, 2026 21:16
…_floor_mux

Both were pass at 1ef60ae and are now blocked on ExprCall(@sin): the drone
flight's hover in token_floor_scenes calls @sin, and token_floor_mux uses
scenes. The CI ratchet on f0d69e4 counted 132 non-pass entries against
the cap of 130 (OVER CAP 1, every other column 0); the merge from master had
dropped this branch's cap edit.

Refs #10469

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ensus itself, take master's

This branch touches no workflow, so master's quiet 220 and shell 324 are
the branch's numbers too.

Refs #10469

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-18 14:24:54 UTC

Summary

Status Count
Total Open PRs 50
PRs with Failing Checks 50
PRs with All Checks Green 0
READY 0
FAILING 50
PENDING 0
NO CHECKS YET 0

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=fad12492937a != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

t27f token_floor: drone flights instead of hard cuts, text in the platforms' safe zone, a marketing clock for the reel

1 participant