Skip to content

Epic 15 · video-convert proves the verification loop on real work #455

Closed
2 of 2 issues completed
Closed

Description

@pascalandy

The problem (CMO)

COR-103 and COR-104 built a verification loop for extensions. COR-104-T1 to COR-104-T9 are real code with tests. But no agent has used the loop to deliver a real extension. The 18 prototypes of the day-1 trials gave no earned "Done when". Since COR-104, nobody has tried again.

Before #442, just next serves COR-102-T1 first, so COR-104-T10 waits behind three French cards. COR-104-T10 is the only card that tests the loop on a real extension. Some tracking files are also out of date.

Unknown: how long each gate takes on a real extension, and which gates find real defects.

REF: #427, #425, #405

The outcome (FMO)

ncly-video-convert releases through the loop on the latest template. A table gives the time and the findings of each gate. The queue and the tracking files say what is true.

Stories

  1. The queue serves French before the only card that tests the loop. (docs(backlog): serve COR-104-T10 before COR-102, and make the tracking files true #442) · text
  2. video-convert cannot release on the latest template. (template: an existing extension adopts just finish after the update #427) · code + tests
    • Today: ncly-video-convert v0.2.1 pins template v0.23.4 and has no just finish. The adoption rule exists since COR-104-T9.
    • After: ncly-video-convert uses the latest template. just signoff and just release pass. The pull request gives the time and findings of each gate.

Done when

just next in nicely prints COR-104-T10 before COR-102 (#442). In ncly-video-convert, just signoff and just release pass on the latest template (#427). The table of gate measures is in the pull request and in a comment on #427.
Every Story has a documented disposition. The outcome has delivery evidence.

👨🏻‍🍳 For the agent

👨🏻‍🍳 Details

Out of this Epic

Blocked by

Evidence

by Opus-5.5 via Claude Code

Activity

  1. added
    3-pty:p1High priority; takes precedence over ordinary planned work
    4-epicGroups Stories around a shared outcome through native sub-issues
    on Nov 3, 2026
  2. added
    1-ready-for-agentValidated work, sufficiently specified for an autonomous agent
    on Nov 3, 2026
  3. pascalandy commented on Nov 4, 2026

    @pascalandy
    OwnerAuthor

    Every line of Done when holds. The Epic is delivered.

    Done when Evidence
    just next in nicely prints COR-104-T10 before COR-102 (#442) #442 closed on 2026-11-03 through #459. On 531b3b48 (v0.26.1), docs/status.md:71 says "just next prints COR-104-T10". COR-104 has since shipped, so just next now prints COR-102-T1
    In ncly-video-convert, just signoff and just release pass on the latest template (#427) ncly-video-convert#17 merged at 4ad77bd5e19ddab9d79c3c5d692087a2789c64d2. just signoff signed that SHA, and just release v0.2.2 exited 0. Tag v0.2.2 points to that commit
    The table of gate measures is in the pull request and in a comment on #427 Gate rows Intake to Signoff are in the body of PR #17. The comment on #427 has the same table, plus the Merge and Release rows
    Every Story has a documented disposition #442 is closed as completed. #427 is closed as completed, after nicely#487 set COR-104-T10 to done (closing comment)

    Outcome: video-convert released through the loop on the latest template, and a table gives the time and findings of each gate. The queue and the tracking files are true: COR-104 is Shipped, the queue is COR-102 then COR-105, and the COR-104 milestone is closed.

    Follow-ups: ncly-video-convert#14, ncly-video-convert#18, #484, #485, #486. COR-104's After keeps Pascal's UAT and the gate-removal review. Nicely v0.27.0 is the release of the Shipped item COR-104 (D043).

    by Opus-5.5 via 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

    Labels

    1-ready-for-agentValidated work, sufficiently specified for an autonomous agent3-pty:p1High priority; takes precedence over ordinary planned work4-epicGroups Stories around a shared outcome through native sub-issues

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions