Skip to content

epic: T27F content factory -- every reel distinct, derived from its own content #10560

Open
3 of 3 issues completed

Description

@gHashTag

The owner, 2026-10-19: every lesson reel shows almost the same picture, so there is no uniqueness. They want one universal template, a factory pattern, a content factory, instead of hand edits to code for each reel.

The diagnosis, from the specs: specs/t27f/lesson_reel.t27 says in its NOT CLAIMED block that the backdrop of every lesson reel is token_floor's physics world (glass balls in a tube), not a picture of the lesson, and that its frame labels are the physics reel's. Only the voice, the captions and the cards change between lessons 1 and 27. The template has one scene, and every item gets it.

Boundary

  • In: specs/t27f/ (a new factory law plus the scene renderers it names), specs/skills/ cards for TRI CLAW, the t27f skill, and the tri CLI entries that run the factory.
  • Out: the voice service, the music, the trinity site, and publishing to any social network. Publishing needs the owner's yes for each post.

User Scenarios

  1. The owner asks for the reels of course 0. The factory reads each lesson's own code and gives each reel a different scene: the code assembling, the spec as a diagram, tests lighting up, a trit field, loops orbiting, a branch splitting, data blocks stacking, modules linking, or invariants guarding.
  2. A new course or a blog post arrives as data. It gets distinct reels with no code edited by hand.
  3. TRI CLAW is asked for a post about a lesson. It picks the format the channel needs (tall or wide reel, square or 4:5 post, cover, carousel, X card, og image) from the same plan.

Requirements

  • R1. A factory law (specs/t27f/reel_factory.t27) maps an item's content features to a plan: archetype, accent, camera motion and layout, plus the formats it renders.
  • R2. Uniqueness is tested: no two items share a signature; adjacent items differ in at least 3 of its 4 fields; no archetype covers more than its cap; every archetype shows something the item has; no item gets a backdrop that comes from another item.
  • R3. A renderer per archetype, in t27, run on the Railway lab. A still per lesson is rendered and compared pairwise, and pairs that are too similar fail.
  • R4. lesson_reel.t27 takes its backdrop from the plan instead of token_floor.
  • R5. TRI CLAW skill cards cover making social visuals: the formats, the choice of archetype, the uniqueness gate and the publish consent.
  • R6. tri CLI commands run the factory: print the plan, render the covers, and run the similarity gate.

Success Criteria

  • The factory's tests pass on the lab with 0 vacuous.
  • The 27 lesson stills, rendered from the plan, have pairwise SSIM under the gate, measured on the lab.
  • The lesson 1 and lesson 14 reels show different scenes, and each one's hero is drawn from that lesson's own code.

Sub-issues are filed per requirement as the loop reaches them.

Requirements

  • FR-001: A factory law at specs/t27f/reel_factory.t27 MUST map an item's content features to a plan containing archetype, accent, camera motion, layout, and the formats it renders.
  • FR-002: Uniqueness MUST be tested: no two items share a signature; adjacent items differ in at least 3 of 4 fields; no archetype exceeds its cap; every archetype reflects something the item has; no item receives a backdrop derived from another item.
  • FR-003: A renderer per archetype, written in t27, MUST run on the Railway lab; a still per lesson MUST be rendered and compared pairwise, and pairs exceeding the similarity threshold MUST fail.
  • FR-004: specs/t27f/lesson_reel.t27 MUST take its backdrop from the factory plan instead of token_floor's physics world.
  • FR-005: TRI CLAW skill cards under specs/skills/ MUST cover making social visuals: format selection, archetype choice, uniqueness gate, and publish consent.
  • FR-006: tri CLI commands MUST run the factory: print the plan, render covers, and execute the similarity gate.

Success Criteria

  • t27c specs/t27f/reel_factory.t27 --test exits 0 with 0 vacuous tests on the Railway lab.
  • tri factory similarity-gate --course 0 --lab railway exits 0 and reports 27 lesson stills with pairwise SSIM under the configured threshold.
  • tri factory render --lesson 1 --format still --lab railway and tri factory render --lesson 14 --format still --lab railway produce outputs whose hero elements are derived from lesson 1 and lesson 14 code respectively, verified by tri factory inspect --lesson 1 --lesson 14 --lab railway exiting 0.

Activity

  1. added
    shape-refusedClosed by the issue-shape gate (specs/policy/issue_shape.t27); a passing edit reopens it
    on Oct 18, 2026
  2. github-actions commented on Oct 18, 2026

    @github-actions
    Contributor

    Closed by the issue-shape gate (specs/policy/issue_shape.t27, #7498): an issue must have the template's sections. Edit the body; an edit that passes reopens it.

    • missing: ## Requirements -- numbered obligations, FR-001: ... MUST ...
    • missing: ## Success Criteria -- an outcome a machine can settle: a number with a unit, a backticked file, exit 0, or a backticked command
  3. removed
    shape-refusedClosed by the issue-shape gate (specs/policy/issue_shape.t27); a passing edit reopens it
    on Oct 19, 2026
  4. gHashTag commented on Oct 19, 2026

    @gHashTag
    OwnerAuthor

    Reopened by the self-heal of #11007. The issue-shape gate closed this issue with a queued run that judged an older body from its event payload; the current body passes gen/c/policy/issue_shape.c, and the gate's own contract is that a passing body stays open. If the work is in fact finished or obsolete, close it as completed.

  5. gHashTag commented on Oct 19, 2026

    @gHashTag
    OwnerAuthor

    Part of mega epic #11038, the one map of every T27F and gen-UI track.

    🤖 Generated with Claude Code

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

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions