Framewright 0.7.0 — Repeat production and reuse (REL-B)

Framewright0.7.0 — Repeat production and reuse (REL-B)

Experimental prerelease. Reuse a production approach while retaining exact-version
review, known failures and honest measurements. This is an operator-led methods/
skills library, not an autonomous hosted video studio.

What changes

• Find the right starting point. README now leads to start / continue / correct,
  with compact current priorities. Older detailed entries remain as linked history.
• Check time as well as geometry. The source montage example offers an English
  caption-time CLI and opt-in render guard. Title/subtitle share the budget; short
  scenes fail before output/media access. It never silently stretches accepted
  content or assumes narration remains aligned after timing changes.
• Carry reuse through a real repeat. Beyond the Letters reuses retained sources,
  assembler, score and voice recipe, with a new script/cut/voice. Both36s formats
  are owner-accepted internal tests. The audio-only correction preserves picture
  packets; fresh-agent continuation recovers the next step without regeneration.
• Qualify specific operations. Pinned ffmpeg-skill explicit midscene frames
  match direct FFmpeg on another film. Its automatic sheet repeats failure and is
  excluded. SSI v2.1 and the AzurMenton guide retain separate receiving-project,
  approval and publication evidence. Channel/book automation remains a staged plan.

Evidence

Local scripts/check.py:514tests,18skips; schema/link/tool-reference checks and
standalone package smoke pass. One independent read-only reviewer approved the
behavior diff and navigated all three entrypoints. GitHub Codex review on5a00706
completed without findings; PR50 and exact merged-main CI onff84b1d pass.
Detailed local record ·
REL-B matrix.

Reading-time assumptions are2.5words/s,15nonspace characters/s, minimum2s plus0.4s
for transitions, rounded to frames. A particular long-copy control moved3→9.75s;
that is a heuristic check, not a reader study. New voice timing/layout and human
creative/listening approval remain independent. Accepted masters are unchanged.

Compatibility and limits

No mandatory project migration or new runtime dependency. Existing montage calls
keep their behavior; --enforce-caption-timing is explicitly opt-in. Unknown
operator labour and baseline effort remain unknown; scripted stage durations are
not a savings percentage or full turnaround quote. Whole-route admission, paid
providers, arbitrary platforms and automatic social publishing are not qualified.
Historical model-evaluation gaps remain; no fresh model calls in this release.

Assets and source examples

• framewright-router-0.7.0.zip: standalone router skill and its local helpers.
• SHA256SUMS: checksum for that ZIP.

The montage example and its new timing script live in the source repository's
examples/production-reuse/, not inside the standalone router ZIP. Optional package
case/example links point to the v0.7.0 source tag. Private media, model weights,
credentials and copied provider code are excluded.

Canonical release
records actual publication, tag and downloadable assets; prepared source links do
not by themselves prove availability. Publication audit.

Publication verification — 1 November 2026

Release PR #51 merged after CI
and GitHub Codex review without findings. Annotated tag v0.7.0 resolves to
b88df9b7013537b1db01637ad4e564e806ea01ad; merged-main CI passed.

Anonymous HTTP200 verified for the release page, source tag, router ZIP and
SHA256SUMS. Downloaded ZIP integrity passed and SHA256 matched the exact final-commit
build: 1ec7b6721f1355e1ae2b3b208afea4c77e67676378832ac51b2b2508daeb9331.
Published as non-draft experimental prerelease; no deployed website or automatic
video/social publishing is implied.

Framewright 0.6.0 — Recoverable production (REL-A)

Framewright0.6.0 — Recoverable production (REL-A)

Experimental prerelease; bounded operator-led production, not a stable autonomous studio.

Framewright can now recover a chosen final video with its exact checks and
limitations, and run an explicitly selected Eevee shot through the bounded local
executor. The production loop remains led by an operator, with manual film stages
recorded rather than presented as automatic execution.

What changes

• Recover the right final. Selected delivery includes path, bytes, SHA256 and
  exact-version review receipts. Historical waits remain visible; new ready work
  keeps its priority. Provider and publication observations are shown separately.
• Run a bounded Eevee shot. Explicit Eevee Next/AUTO joins Cycles CPU with pinned
  inputs/settings/runtime, output checks and human review still pending. A retained
  Last Seed scene verifies repeat/light change, interruption and explicit retry.
• Keep reuse honest. Oversized montage titles/subtitles fail before a clipped
  caption is exported. Scoped PixVerse/Odyssey component use remains separate from
  structured feature coverage, current quotas/access and publication rights.
• Retain production experience. Good Dog and One Artist, Two Cities case records
  preserve accepted versions, failures, corrections and focused follow-up tests.

Evidence

The complete local check ran510tests with18skips, plus retained benchmark integrity,
schema/link/matrix checks and a standalone-package smoke. A separate read-only
OpenAI reviewer approved the full scoped change in two rounds, independently ran
22tests and confirmed the engine-label nit fixed; eight affected tests passed again.
GitHub Codex review on1345590 completed without findings. PR48 and the exact merged
main commit5a98bd6 passed CI.

Compatibility and limits

Unchanged projects need no data migration. Final selection is explicit and does
not delete waits or grant execution/publication authority. Changed saved-shot
implementation fingerprints require newly prepared/reviewed contracts; do not
repin old approvals to bypass drift checks.

Eevee qualification is a short480×270 scene test on one Blender4.5.15 ARM64 build,
not full-film/final-resolution or cross-platform qualification. Whole-film manual
steps remain manual. Current model routing is not newly evaluated. Media/account
terms, commercial use, human creative/listening acceptance and public uploads stay
separate. No models, private media, credentials or vendor binaries are bundled.

Assets

• framewright-router-0.6.0.zip — standalone router skill and local helpers.
• SHA256SUMS — checksum for that ZIP.

The ZIP's optional case links target the v0.6.0 source tag. The canonical
release page
retains publication state, source commit and downloadable assets.

Publication verification

Tag v0.6.0 points to 8696269e0d81c3a2b63b74feac6ea209c3544343.
Release PR49,
merged-main CI
and tag CI passed.

The public release page, ZIP and SHA256SUMS returned HTTP200 without authentication.
The downloaded ZIP passed archive integrity and matched the published checksum:
92911ed69b5a10357de79ef50b20922d4f9d02a5a1f6f0f74ca2949a757ee668.
This verifies publication of the bounded experimental release, not broader runtime
capability, media rights or new model evaluation.

Framewright 0.5.0 — bounded production loop

Framewright 0.5.0 is an experimental consolidation of reusable production methods and bounded local tools.

• Saved Blender shots now connect to route admission and sequential execution, with pinned inputs, explicit frame limits, output checks and pending human review.
• One readable producer brief joins the task, materials, routes, constraints and next action.
• Source-first editing, OTIO/Kdenlive return, local execution recovery and cost/resource controls are included since 0.4.0.
• Last Seed and four source-based films document corrections, acceptance/publication boundaries and scoped Tone.js, p5.js and shader trials.
• Three new video-toolkit adoption plans are queued without bulk installation.

Limits: REL-A remains partial. Fresh-process recovery is not independent-operator qualification; manual Eevee production is not a fully admitted film route. Current-source model routing is not newly evaluated. Human listening/creative approval and publication remain separate.

The ZIP installs the standalone router skill; the source repository includes worked examples, evidence and documentation. No project migration is required for unchanged workflows. New saved-shot execution requires explicit selection/admission.

v0.4.0 — repeatable production workbench

Framewright v0.4.0 is an experimental prerelease of the agent-operated video-production toolkit.

What is new

• Experiment workbench and readiness: freeze a bounded question and common sources, compare retained A/B outputs, record checks/time/cost and prepare local review packs. Owner acceptance remains separate from technical evidence.
• Saved Blender shots: restore a pinned scene, change one declared camera/action/light/audio control and rerender a selected range. The original CPU fixture matched 36 repeated frames and 12 separately rendered subrange frames; audio timing and camera/action preservation are recorded.
• Versioned characters and environments: prepare passports and bind exact versions to shots. Incomplete, stale or unapproved declared definitions block execution. Automatic visual identity is not implemented.
• Studio knowledge: updated production/research records, 40 final exports, a 10-chapter book outline, three worked cases showing routes with Framewright and without it, and 10 mapped evidence gaps.
• Weekly English posts: documented ABVX metadata, 1–3 YouTube examples, a required generated cover/alt text and owner-provided publication links. The owner's configured heartbeat is account-local and is not installed by cloning the repository.

Checks and source

• Local offline gate: 360 tests, zero failures, one skip, plus retained router/storyboard evidence, documentation/catalogue links, generated reference and standalone-package smoke.
• PR #45: both CI runs passed; Codex code review completed without findings on 1e22a4f.
• Merge/tag target: dffec685ab19ae84642a9ed8d279dc66aab0c3b3; its tree matches the reviewed head.
• Main CI.
• Changelog · Release audit.

Download and scope

framewright-router-0.4.0.zip is the standalone router skill; the tagged source also contains documentation and authored examples. Python 3.11+ is recommended for the current helper set; media functions require the declared FFmpeg/Blender tools separately. This archive includes no Blender application, media, models, private journals or account automation. Preserve local skill edits before installing an update.

SHA-256: e9ae3261bd90767996b9dd6217f314c15aa4fd84182e64dfcaacf0193673fc70. SHA256SUMS is attached alongside the archive.

Current-source model routing remains not_evaluated_current_source; the historical model evaluation is unchanged. Blender qualification is limited to the original CPU fixture on one build/Mac. DJV frame access, facial naturalness, reader reproduction and SSI's first scheduled production remain bounded/pending as documented. New-video rights, playback/acceptance and audience outcomes remain separate. This release makes no claim of universal rendering, automatic publishing or audience gains.

Verified after publication

Main and tag CI completed successfully on the exact release commit. The release page and both assets were fetched without authentication. The downloaded ZIP passed integrity checks and matched the built archive and published SHA256SUMS. The annotated public tag resolves to the reviewed merge commit above. Local main is synchronized and clean.

v0.3.1 — receipt and conformance fixes

This experimental patch corrects three boundary bugs found in late review of 0.3.0.

• Replacing an output used by a check's --depends-on receipt now reopens that check and downstream delivery. A stale receipt cannot leave the delivery task marked done.
• Correcting material attribution, origin, tags or licence metadata preserves technical video checks. Rights still gate the kit independently; media/cut changes still reopen conformance.
• Odyssey's unindexed inputs no longer match explicit modality filters. The candidate has not gained production qualification.

Three public-CLI regressions were captured failing before and passing after. The complete offline check passes: 247 unit tests, retained evidence, local links, generated matrix and extracted package smoke. No model qualification, media render or paid generation was performed.

Install framewright-router-0.3.1.zip and verify it against SHA256SUMS. The ZIP contains the router skill; the full source archive includes both skills and case documentation. Optional case links are pinned to this tag. Existing schema-2 projects remain readable; resume exposes changed helper-source identity without silently replanning. The PlayMCP service film still awaits owner retakes.

v0.3.0 — resumable production studio

Framewright 0.3.0 moves toward an agent-operated personal production studio: keep the project, decisions and reusable materials together, then prepare a local publication kit.

• Resume projects with explicit tasks/waits, file pins and revision-bound evidence. Technical QA, listening, creative acceptance and publication remain separate.
• Connect scenes, demonstrations, narration and missing inputs; reuse source/rights-bound materials across independent main/Short edits.
• Build local publication kits containing final files, hashes and open checks. Uploading remains a separate action.
• Search tools and proposed combinations; use shared repackaging/insight/hybrid intake and a private music catalogue. Discovery drift now fails offline validation.
• Retain scoped game creation, game/engine reviews and games as virtual sets, plus Shorts, converter/ASR and recording-preparation workflows.

Validation: 244 unit tests and the complete offline check pass, including historical-evidence integrity, local links, generated matrix and extracted standalone package smoke. No video render or new model qualification was performed for release. Current-source routing remains experimental and unevaluated.

Installation: framewright-router-0.3.0.zip contains the router skill only, including its project/journal/scene/kit helpers. Use the full source checkout/archive for both skills (video-production-router, game-engine-production) and case documentation. Verify the ZIP against SHA256SUMS. Core references stay local; optional case/provenance links are pinned to this release tag and checked during packaging. Schema-1 production projects require explicit backed-up migration before using schema-2 additions.

The PlayMCP service review continues with owner retakes; it is not a release prerequisite. Other engines, native audio/video understanding, strict resource enforcement and general autonomous production remain unqualified or deferred.

v0.2.0 — production plans, scene by scene

Framewright helps AI agents plan and coordinate video production, scene by scene and layer by layer. Books and software promos are the initial test cases, not the product boundary.

New: readable production plans

Run python3 skills/video-production-router/scripts/plan.py BRIEF.json --format markdown to review scene timing, tool/capability evidence, explicit choices, required source kinds, suggested files, blocked requirements and separate video/still/voice QA. Default JSON and selection ranking are unchanged by this formatter. All generated checks remain planned or blocked; no asset is automatically verified.

Stage closeout and maintenance

• Complete the six-book, landing-tour and series-compilation stage, retaining owner feedback, technical QA, supplied publication links and incomplete attempts separately.
• Consolidate README/skill entrypoints and correct stale qualification wording.
• Retain scoped tool-chain evidence and manual OpenScreen/MoviePy recipes.
• Pin compilation music and thumbnail inputs, fix archive commands and reject unsafe summed PCM peaks before conversion.

Evidence and limits

167 offline tests passed, alongside retained evidence/link checks, generated matrix and standalone JSON/Markdown package smoke. No renders, provider calls or new model evaluation were performed for this release. Current source remains not_evaluated_current_source; historical scores are not promoted. Strict brief/budget/download-limit validation is deferred.

The ZIP contains the standalone router skill, not media, models, dependencies or a renderer. Review upstream licences and use your authorised runtime. See SHA256SUMS for the ZIP's checksum.

Production-plan guide · Stage audit · Open reference film

v0.1.1 — reliable deliverable routing

Patch to the first experimental release; fixes both routing findings from PR #6.

• Equivalent requirement sets now resolve to the same tool coverage. Provider selection runs to a fixed point, so a finishing request can wait for its picture/export dependency.
• Primary ranking includes requested deliverables and prefers local evidence before style/default tie-breaks. A tested native still export avoids an unnecessary video/extraction chain.
• Explicit user tool choices remain fixed. The standalone smoke test exercises the explicit Flute + FFmpeg fallback.

Validation: both review examples failed before the fix and pass after it; 41 regression tests include all 24 permutations of a four-requirement chain. Retained video/native/thumbnail integrity checks, generated capability matrix, CI and standalone package smoke check pass. No new render or model evaluation.

Start with the open first-film route or the eight-tool capability matrix.

Router remains structural_only. New mixed pipelines need integration tests. The ZIP is a standalone selection skill, not a video engine or dependency installer. Preserve/review existing local skills before replacing them. Upstream tools retain their own licences; the source reference does not establish universal free eligibility, measured pilot time/cost or clean-machine rendering after the lint repair.

Still-only plans also omit the global video assembly stage; its regression check passes.

v0.1.0 — first experimental release

Superseded by v0.1.1, which fixes requirement-order dependence and direct-deliverable routing. Use v0.1.1 for new installations. The v0.1.0 tag and assets remain unchanged.

Framewright helps an AI agent choose and execute a suitable video pipeline based on documented experiments. It is not a new video engine.

This first experimental release adds:

• Eight source-backed tool profiles, a generated capability matrix and scene/layer planning for style, effects, input material, language and frame timing.
• An offline JSON planner that preserves explicit tool choices and reports unmet requirements; it does not install, render or publish.
• An open Remotion reference project with authorised demo assets, pinned dependencies, an agent prompt, exact render commands and encoded-output checks.
• A multi-date, schema-backed integrity validator with explicit errors and independent native-export/PNG checks.

Validation: 36 tests, local retained-artifact hashes/dimensions, capability-matrix drift check, standalone package extraction/CLI smoke test and skill structure check. Six routes and eight retained exports; seventeen routing scenario specifications.

Qualification: experimental. Router remains structural_only; independent model evaluation has not run. New mixed toolchains need integration tests. The open source example has not been re-rendered on a clean machine after the lint dependency repair. Pilot time/cost was not retained. Upstream tools retain their own licences and are not bundled.

The ZIP contains only the router skill and its supporting references/scripts. Review/back up existing local skills before replacing them; no installer overwrites local work. SHA256SUMS identifies this exact archive. The tagged source contains the complete reference project.

Start here: https://github.com/markoblogo/framewright/blob/v0.1.0/docs/first-video.md
Capability matrix: https://github.com/markoblogo/framewright/blob/v0.1.0/skills/video-production-router/references/tool-matrix.md