October 29, 2026 — plugin merge and editorial source checkpoint

PR #467 is merged at 1a193eb3924ad20ee5add77c2c495bb32e9bb900. #466 remains open for observed plugin acceptance.

The next selected feature, #379, is implemented in draft PR #468 at 256b0e88884db3d6dd768d7acca89d143b8f119d: bundled article presentation through the canonical profile/strategy path, a shared Markdown metadata contract, HTML/PDF outputs, optional DOCX/EPUB semantics, exact source export, licensed local assets and a synthetic example. Guide.

Next feature: #378, the optional writing/polishing agent targeting that concrete contract. It is not implemented by #468. #350 remains the subsequent presentation-profile option.

Nine regression cases are authored and unrun. Build/test/Cargo/lint/format/schema/docs, product CLI/native/provider and CI qualification remain paused; no rendered or visual result is claimed. #379 stays open. Baseline/documentation/release work in #458/#459/#419 and released Flow consumption in Flow #52 remain separate outstanding outcomes. No release/tag was created.

Earlier draft/merge snapshots below are preserved history.

October 29, 2026 — configured plugin checkpoint and artifact-forest handoff

The artifact-forest demo selection and public SDK publication view are merged through #464 and #465. Main is 93c69b37432234201e92ab5af7580c8d3e24b106. Their source changes do not replace the pending CLI/SDK/native-provider and released-consumer qualification under #430/#421.

New follow-up #466 makes the existing plugin SDK configurable through ordinary transform YAML and CLI metadata commands. Its implementation is saved in draft PR #467 at f4cdfceb794e5e3ee38482fe4f686013ce78bcf3: explicit trusted local command plugins, exact artifact-graph edges, per-transform configuration, bounded process execution and cancellation forwarding, and a supplied-name counter producing JSON and CSV. It reuses the existing plugin/artifact/process contracts. Command-plugin cache/checkpoint reuse is disabled until executable dependencies can be attested.

#379 remains the separate optional editorial presentation profile; a custom extractor/exporter fits the existing plugin extension path. This checkpoint does not add PDF/OCR, arbitrary entity recognition, XLSX or a second parser framework.

Qualification remains deferred at the user's request. Tests are authored but unrun; no build/Cargo, lint/format/schema/docs validation, product CLI/native/provider execution, or GitHub Actions execution/polling was performed. #466 stays open for observed acceptance. #458, #459, #419 and Flow #52 retain their baseline, documentation, first-release and released-consumer work. No release/tag was created.

This dated receipt supplements the preserved roadmap below; older “zero open PRs” snapshots are historical.

October 28, 2026 — suite roadmap refresh and current merge truth

This dated update supersedes stale draft/issue-count statements below while preserving every original issue, acceptance criterion and historical receipt.

Live snapshot: main c1d1bebfd48369d18e7c46295859d76e3f831499; 27 open issues, 0 open pull requests, 0 GitHub releases. The open count includes this roadmap and creative epic #421; it is not a count of 27 missing foundational features. Suite roadmap: Flow #11.

What has landed

• NUKED — completed: [Checkpoint 414.1] Bind ordered collections to canonical planning and execution #415 ordered-collection planning/execution, [Publication] Generate deterministic print-interior PDFs from ordered page collections #416 ordered-page print PDF, [Checkpoint 414.2] Generate deterministic EPUB 3.3 fixed-layout packages #417 fixed-layout EPUB generation, [Checkpoint 414.3] Validate fixed-layout EPUB and publish capability truth #418 EPUB validation/capability truth. These four issues are closed as completed. Their completed source scope does not replace the pending release gate.
• PR #455 merged October 27 at 0842c16cb50530f37a35b18fb6b0211f3ffc2386. Bounded original-Fountain body exports, Trelby and transcript terminal Text are now merged source; earlier “draft/unmerged” and “missing exports/Text” descriptions are historical.
• Reconcile current contributor and architecture documentation #459 contributor/architecture documentation corrections merged through docs: reconcile contributor and architecture navigation [skip ci] #461 at 645a789e8ce36081287ee032f0f1a72fe160dfce. Documentation structural/link execution remains deferred.
• Restore the locked Rust qualification baseline #458 schema integer/Snap workspace source corrections merged through fix: correct schema integer types and Snap workspace selection [skip ci] #462 at 8d7a71edd4033a60801c663fec242a2195a2562e. Cargo-produced lock reconciliation, recorded lint findings and exact-source executable qualification remain outstanding.
• [Publication] Add localization-ready layered page composition and locale render targets #406 has six merged composition checkpoints, including ordinary renderflow/v2 build/CLI/SDK admission through feat(composition)!: admit normal builds [skip ci] #454. Earlier “next: ordinary-build admission” notes are historical. Broader typography/native interchange and actual runtime/visual/platform/consumer qualification remain open.

Short path to the first usable publication release

1. Finish Restore the locked Rust qualification baseline #458's locked baseline and Reconcile current contributor and architecture documentation #459's remaining documentation acceptance when the maintained qualification deferral is lifted.
2. Complete [Release] Publish the first verified Renderflow integration-candidate release and reconcile distribution truth #419: the first exact-source, immutable, verified integration candidate, initially Ubuntu 24.04 x86_64 GNU, with downloaded-asset installation and truthful distribution evidence.
3. Complete the consuming adapter and released contract proof in Flow #52. Flow owns orchestration; Renderflow remains independently usable through its own CLI/SDK.

The bounded ordered-page PDF/EPUB release does not wait for every optional Renderflow profile, the entire creative forest, broader localization or an HTTP service. A source version or merged PR is not a published/qualified capability.

Complete remaining queue

All 27 current open issues appear in the table. Optional capabilities stay visible but do not expand the first usable-release finish line. #458/#459/#419 and all creative/composition acceptance issues remain open.

This refresh performed source/issue/PR/release-state reads only. Tests, compiler/build/Cargo resolution, lint/format/schema/documentation validators, native/provider/media/CLI execution and CI remain deferred. No Actions were dispatched or polled, and no current green-baseline, runtime, release or storage-savings claim is made.

Audit and complete open-work ledger — 2026-10-21

This dated section supersedes historical counts, green-baseline claims and near-term ordering below. The complete previous roadmap body remains intact after the history divider. Every original issue remains open; this audit does not close acceptance criteria or rewrite prior decisions.

Audit report: https://github.com/egohygiene/renderflow/blob/audit/flow-suite-20261021T025401Z/audits/flow-suite-20261021T025401Z.md

Snapshot: main 81088f01b14c010e7dc6523763771f8461ed9b09; 25 open issues including this roadmap (24 original work issues), one draft PR #455, no GitHub releases. The current implementation version is 0.3.0-rc.1, not a published stable v1. Existing exact-source provider records show four successful, four failed and two skipped jobs; failures include Rust/Clippy, lockfile and Snap workspace-package blockers. No product tests, compiler/build, schema qualification, native/CLI/provider execution or CI reruns were started for this audit.

* marks a distinct issue-specific predecessor, release/integration prerequisite or explicit scheduling gate. Bounded preparation may still proceed. Common executable qualification remains deferred for every affected issue and does not by itself earn a dependency star. The maintainer's implementation-sprint qualification deferral remains in force. Audit-artifact checks are separate from product qualification. Do not close a starred issue because its implementation PR merged.

First usable publication candidate

1. #459 — Reconcile current contributor and architecture documentation.
2. #458 — Restore the locked Rust qualification baseline; source correction preparation can precede the later authorized test session.
3. [Release] Publish the first verified Renderflow integration-candidate release and reconcile distribution truth #419* — Publish the exact reviewed, verified immutable Ubuntu 24.04 x86_64 GNU integration candidate and reconcile distribution truth.

The first candidate is the bounded ordered-page print-PDF/fixed-layout EPUB path built by closed #415–#418. It is independent of the complete creative forest, broad localization, HTTP service, AI summaries, Sonic DNA, editorial profiles, presentations and podcasts. Passing this boundary means an installable, evidenced release for that declared scope. It does not claim stable v1, all optional channels or every conceivable derivative. Flow owns its adapter and consumer proof.

Creative forest and composition: complete the authored work honestly

4. [Artifact Forest 1/9] Define cycle-safe exhaustive derivative planning #422 — Cycle-safe exhaustive derivative planner qualification.
5. [Artifact Forest 2/9] Define canonical screenplay artifacts and capability truth #423* — Canonical screenplay/capability truth qualification.
6. [Artifact Forest 6/9] Add timed-text formats and embedded subtitle extraction #427 — Timed-text/embedded-subtitle qualification.
7. [Artifact Forest 3/9] Add bounded scripttool screenplay conversion adapter #424* — Bounded Scripttool directions, including individually documented refusals.
8. [Artifact Forest 4/9] Add afterwriting Fountain PDF and screenplay-analysis adapter #425* — Afterwriting PDF/analysis qualification.
9. [Artifact Forest 5/9] Recover screenplay structure from PDF and unstructured text #426* — Lossy PDF/text recovery and explicitly selected OCR qualification.
10. [Artifact Forest 7/9] Add local speech-to-timed-transcript provider #428* — Local speech-to-timed-transcript qualification.
11. [Speech] Add explicit original-media time maps and aligned subtitle exports #440* — Explicit original-media time maps/aligned subtitle qualification.
12. [Artifact Forest 8/9] Add a creative conversion toolchain profile and doctor surface #429 — Exact optional provider/platform/asset toolchain qualification.
13. [Artifact Forest 9/9] Prove the multi-family artifact forest and hand it to Flow #430* — Review the existing draft export checkpoint Add original Fountain, Trelby and transcript text exports [skip ci] #455, then prove actual multi-family CLI/SDK execution, source suppression, repeatability and released handoff.
14. [EPIC][Artifact Forest] Build truthful screenplay, transcript, and exhaustive derivative workflows #421* — Reconcile and close the original nine-checkpoint creative epic only when its complete outcomes are demonstrated.
15. [Publication] Add localization-ready layered page composition and locale render targets #406* — Complete justified broader typography/native interchange work and the deferred schema, runtime, visual, platform, release and consumer qualification of six merged composition checkpoints.

Items 4–6 remain independently preparable fronts. This is an execution order, not a new claim that they must wait for the first candidate to begin source review. Exact provider combinations should be finite and evidence-backed. The #406 composition lane may proceed in parallel and does not block the default-locale ordered-page candidate. Keep native/runtime/visual unqualified status explicit.

PR #455 remains draft and unmerged at eb47f6331cf3f81868b3566521976484349a64b9. It authors direct original-Fountain body exports and transcript terminal Text; these are not main/released features. It does not qualify Scripttool reverse routes, replace recovery review or complete #430 acceptance. Retain the current per-target publication index, artifact ID, locator, loss/review state and partial-run semantics for downstream consumers; manifests are evidence to verify, not an automatic attestation of bytes.

Conformance depth

16. Build a comprehensive adversarial rendering fixture corpus #412 — Grow the existing generator-first adversarial corpus in finite PR/nightly/release tiers.
17. Add a synthetic comic fixture and reusable document-type fixture packs #413* — Add the focused synthetic-comic pack and reusable document-type convention under Build a comprehensive adversarial rendering fixture corpus #412.

Fixture design can proceed during source work; execution waits for the maintained qualification boundary. #413 does not become a new blocker for comics #93. Avoid a second fixture framework or a huge copyrighted binary collection. Optional provider absence, deliberately unattempted work, static/mock conformance and real native proof stay distinct.

Optional capabilities, each as a bounded product increment

18. 📝 Add long-form editorial article template/profile paired with the Medium-style Copilot agent #379 — Deterministic long-form editorial profile and shared content/metadata contract.
19. 🤖 Add Medium-style article Copilot agent for generation and polishing #378* — Paired editorial generation/polishing agent; author meaning and citations remain reviewable.
20. Add a Slidev-backed product presentation publication profile #350 — Renderer-neutral presentation profile with a pinned Slidev adapter.
21. Evaluate repository briefings and podcast derivatives from canonical content #349 — Evaluate repository briefings/podcast derivatives; explicitly adopt, adapt, defer or reject before expanding.
22. [AI] Add source-grounded publication summary candidates using shared runtime profiles #456* — Source-grounded review-required publication-summary candidates through existing AI/runtime profiles.
23. Add Sonic DNA normalization and semantic audio descriptions #397* — Deterministic Sonic DNA normalization and optional semantic audio descriptions with honest analyzer/model authority.
24. 🌐 Expose Renderflow through a first-class HTTP API and job service #420 — Optional HTTP/job adapter over the public core SDK, with bounded upload/retrieval, progress/cancellation and structured partial results.

These are useful capabilities, not prerequisites for the first local publication release. Content agents and AI produce candidates; they do not approve canonical copy, replace reviewed metadata or publish. No new router, implicit remote fallback, mandatory paid endpoint or autonomous harness is introduced merely to complete the ledger.

Governance and final reflection

25. Backfill repository ADR history and enable continuous decision capture #405* — Shared-system-scheduled ADR backfill and continuous capture; preserve the existing scheduling decision and accepted four-digit naming.
26. [Audit] Post-roadmap repository, backlog, and Identity audit #409* — The separate post-roadmap repository/backlog/Identity audit using fresh final evidence.

This audit is planning input to #409, not its completion. Identity source promotion remains human governed, and unavailable approved assets must not be invented. Final stable-version policy remains a later explicit release decision after real integration and closeout evidence. Optional work stays visible even when it is scheduled after a usable release.

One ledger, preserved ownership

Recommended native hierarchy: this roadmap directly contains #421 and the other top-level work, #421 contains #422–#430 and #440, and #412 contains #413. #440 retains its distinct speech extension scope and links #428. All 24 original work issues appear exactly once across that tree; both new focused gaps are added without deleting or replacing any original issue. If an existing native parent is discovered during the final refresh, preserve it and use the roadmap's linked descendant inventory rather than forcibly reparenting.

Working rhythm: select one bounded checkpoint, inspect its current source and preserved full issue, author/review a small PR, record executed versus deferred evidence, and return to this ledger. Keep original acceptance criteria and issue history; close only with concrete scope-matching evidence and an explicit note. Avoid repository-wide implementation rewrites or duplicate audit/roadmap epics.

Preserved roadmap history

The following is the complete original roadmap body captured before this update. Historical statuses, source SHAs and green-run claims apply to their own dates.

Artifact-forest lane — 2026-09-25

This delta adds a parallel creative-derivative lane without changing the first
publication-release critical path.

• #421 is the new parent
  for cycle-safe exhaustive derivative forests, screenplay interchange/recovery,
  timed-text extraction, local speech transcription, optional creative-provider
  tooling, and the Flow handoff.
• Checkpoints are [Artifact Forest 1/9] Define cycle-safe exhaustive derivative planning #422–[Artifact Forest 9/9] Prove the multi-family artifact forest and hand it to Flow #430.
• [Artifact Forest 1/9] Define cycle-safe exhaustive derivative planning #422 (derivative-forest planner semantics), [Artifact Forest 2/9] Define canonical screenplay artifacts and capability truth #423 (screenplay artifact model),
  and [Artifact Forest 6/9] Add timed-text formats and embedded subtitle extraction #427 (timed-text model/extraction) are independently startable fronts.
• scripttool and afterwriting are provider candidates only; provider adoption
  must be evidence-backed and remain outside Renderflow core implementation.
• This lane does not block [Checkpoint 414.1] Bind ordered collections to canonical planning and execution #415 → ([Publication] Generate deterministic print-interior PDFs from ordered page collections #416/[Checkpoint 414.2] Generate deterministic EPUB 3.3 fixed-layout packages #417) → [Checkpoint 414.3] Validate fixed-layout EPUB and publish capability truth #418 → [Release] Publish the first verified Renderflow integration-candidate release and reconcile distribution truth #419, the first immutable
  publication release path.
• [Artifact Forest 9/9] Prove the multi-family artifact forest and hand it to Flow #430 is the convergence/proof point that hands a released artifact-forest
  contract to Flow's exhaustive-comic workflow.

The current intent is that a project-level "everything" run can eventually
produce screenplay, PDF, e-book, page, transcript/subtitle, accessibility,
localization, and other authorized derivative families while producing each
target identity once and retaining honest loss/provenance/provider evidence.

Live sweep delta — 2026-09-22

This dated delta supersedes older issue counts, status claims, and execution order below while preserving the original deep audit and quest line as historical architecture context.

• Current main: 170c3d5985af073d3da8f6ac2e0c4b639cfd2b3e (tree edbaf6c6a87fcb03e3c8cd600822dd9bbc666358).
• Current-main CI and documentation validation are green; scheduled conformance and benchmark evidence are also green.
• Open pull requests: 0.
• GitHub releases: none.
• The existing unsigned v0.2.1 tag points to historical commit 96d1e55231c30449b12f4849d7cdda63853abc68; it is historical evidence, not a release of current main, and must not be moved or reused.
• The immediate comic/publication production path is #415 → (#416 and #417) → #418 → #419 → the Flow-owned immutable Renderflow adapter and static-publication proof.
• #406 remains the parallel/later layered-composition and localization lane. It is not required for default-locale ordered-page PDF/EPUB generation, but it remains required before claiming localization-ready publication.
• #412 and #413 follow the production exporters. Add a synthetic comic fixture and reusable document-type fixture packs #413 consumes the print-PDF and fixed-layout EPUB routes as reusable synthetic-comic evidence; it does not block their implementation.

The live queue above is authoritative for near-term execution. Remaining profile, ADR, corpus, audit, and final-stable-release work stays valid after this production path.

Current implementation status — 2026-09-12

The universal artifact foundation and its publication proving layers are now complete:

• Universal binary-safe artifact, planning, execution, validation, provenance, checkpoint, adapter, profile, and publication-hygiene foundation
• Artifact DNA and provider-neutral AI integration for the magazine workflow
• Golden artifact corpus and end-to-end conformance coverage (Establish a golden artifact corpus and end-to-end artifact-forest conformance suite #366, merged through PR test(conformance): add golden artifact corpus #403)
• Rights-aware coloring-book profile (Add a rights-aware coloring-book publication profile and line-art pipeline #348, merged through PR feat(publication): add rights-aware coloring-book profile #404)

Recent verified completions also include #396 (PR #398), #387 (PR #399), and #380 (PR #401). The Artifact DNA/AI magazine integration tracker #400 is closed.

Remaining Renderflow implementation queue:

• Add Sonic DNA normalization and semantic audio descriptions #397 — Sonic DNA normalization and semantic audio descriptions
• 📝 Add long-form editorial article template/profile paired with the Medium-style Copilot agent #379 — long-form editorial article template/profile
• 🤖 Add Medium-style article Copilot agent for generation and polishing #378 — Medium-style article Copilot agent
• Add a Slidev-backed product presentation publication profile #350 — Slidev-backed presentation profile
• Evaluate repository briefings and podcast derivatives from canonical content #349 — repository briefings and podcast derivatives

#367 remains open through these remaining profiles and the final Flow-suite release-hardening pass.

North-star outcome

Make Renderflow a trustworthy universal derivative engine that can:

1. accept an arbitrary source artifact or source collection,
2. inspect and classify it safely,
3. discover every configured/available derivative capability,
4. resolve one shared execution DAG,
5. wrap many replaceable local or remote tools through explicit adapters,
6. generate a bounded "everything" artifact forest when requested,
7. validate and provenance every output,
8. survive interruption and resume deterministically, and
9. expose a stable provider seam that egohygiene/flow can orchestrate without owning Renderflow's domain logic.

The concrete proving workload is a magazine/publication build that can fan reviewed source into print, digital/web, e-book, editorial, image/preview, accessibility, metadata, archive, and optional enrichment derivatives.

Deep-audit summary

Strong foundations already present

Renderflow is not starting from scratch. The repository already contains substantial architecture and implementation for:

• a modular Rust workspace and embeddable core SDK
• graph planning and multi-target DAG execution
• optimization modes
• transform registries and command transforms
• plugin SDK boundaries
• AI provider abstraction
• caching
• execution-plan serialization/visualization
• broad format/capability modeling and magic-byte detection
• documentation/product site/release infrastructure
• existing derivative roadmap issues

These pieces should be preserved and evolved rather than replaced wholesale.

Critical architectural gaps found

1. The "universal" graph is binary-incompatible underneath

The core transform/executor contracts still move String values, graph source loading uses read_to_string, and command output can be read as UTF-8 text. Binary-native documents/media/archives therefore cannot truthfully share the same execution substrate yet.

2. Configuration is still single-source and family-gated

The current config has one input and hard-coded document/image/audio compatibility rules. That prevents arbitrary source collections, cross-family derivatives, and declarative artifact-forest profiles.

3. There are multiple execution paths

The SDK dispatches between legacy build and graph-build paths instead of one canonical plan/execute lifecycle. This creates different semantics depending on invocation mode.

4. Public execution evidence is not authoritative yet

ExecutionResult exposes useful fields but currently populates cache reuse, skipped transforms, and diagnostics as empty values. ArtifactManifest is currently path/name oriented rather than provenance-complete artifact evidence.

5. External tool execution is duplicated and under-bounded

Multiple command runners execute arbitrary tools without one shared timeout/cancellation/output-bound/environment/provenance policy. This becomes a major reliability and security concern when the maximal profile wraps many tools.

6. Tool availability is not a complete planner model

The capability model currently knows a small built-in external-tool set while arbitrary commands/plugins can exist. Provider identity/version/platform/capability must become canonical planner input.

7. Format breadth is ahead of validation evidence

Many formats are declared, but the long-term support contract needs to require fixtures, validators, provider evidence, and honest loss/fidelity classification before a capability is called production-supported.

8. Flow integration needs resumable evidence, not just an SDK call

Flow already defines federated ownership, versioned contracts, artifact identity, redacted diagnostics, and resumable orchestration. Renderflow needs checkpoint compatibility and structured run/result contracts while Flow retains cross-holon state/recovery ownership.

9. Maximal publication expands the privacy/rights blast radius

The audit found no first-class publication redaction/sanitization stage. Generating many derivatives can multiply embedded metadata, paths, credentials, geolocation, rights ambiguity, or PII unless publication hygiene is explicit.

10. Current default-branch CI is red

The latest audited main run fails web setup because pnpm caching is requested before pnpm exists and fails Snapcraft validation because Snapcraft 9 rejects the current override-install key. These should be fixed before architecture expansion is treated as verified.

Dependency-aware quest line

Wave 0 — Restore truth

#351 — Restore the default-branch CI and packaging quality gate

Make main green and keep package/docs claims evidence-backed.

Exit: default-branch CI is completely green.

Wave 1 — Build the universal artifact substrate

#352 — Introduce a binary-safe artifact kernel and content-addressed artifact store

Replace String -> String as the universal substrate with binary-safe artifact identity, storage, collections, and lineage.

#356 — Centralize and harden external tool execution with bounded process policies

Create the one process execution service every wrapped tool will use.

#353 — Define Renderflow spec v2 for arbitrary sources, artifact forests, profiles, and execution policy

Make source collections, target selectors, profiles, budgets, and policy declarative/versioned.

#354 — Unify legacy build and graph build behind one canonical planner and executor

Every operation should become inspect -> plan -> execute -> validate -> evidence.

#359 — Create a runtime tool capability registry and reproducible toolchain fingerprint

Make installed provider/tool identity and versions planner/cache/provenance inputs.

#365 — Build universal input intake, deep inspection, and safe recursive artifact extraction

Turn arbitrary files and compound artifacts into trustworthy graph seeds without pretending unknown formats are supported.

Wave 1 exit: a binary source can be safely inspected, represented, planned, and transformed through the same canonical engine as text.

Wave 2 — Make execution trustworthy and resumable

#355 — Make execution results provenance-complete and align artifact evidence with Flow contracts

Populate actual outputs, cache reuse, skips, failures, validation, digests, producers, and source relationships.

#357 — Stabilize Transform v2 and the plugin SDK around typed artifact I/O

Give built-in and third-party transforms the same artifact-native runtime contract.

#360 — Add artifact validation, fidelity gates, and a capability conformance matrix

An exit code is not enough: outputs must carry validation evidence and honest support status.

#358 — Add checkpointed execution and a resumable Renderflow provider seam for Flow

Implement interruption-safe Renderflow work and the structured provider contract Flow will consume.

#366 — Establish a golden artifact corpus and end-to-end artifact-forest conformance suite

Build this incrementally throughout Waves 1-4; it becomes the release-grade proof that the contracts work together.

Wave 2 exit: a failed run can be assessed/resumed without repeating compatible work and every result explains exactly what happened.

Wave 3 — Expand the replaceable tool ecosystem

#362 — Establish first-class adapter packs for the high-value open tool ecosystem

Evaluate and wrap document/PDF, image, media, office, archive/data, OCR/extraction, subtitle, and related providers through the common adapter contracts.

Existing #344 — Evaluate and implement EPUB and KEPUB derivative support

Integrate as e-book provider capabilities rather than a special pipeline.

Existing #345 — Define the HandBrake transform adapter and Aniflow boundary

Use the bounded process/provider contracts and preserve Aniflow's temporal-video ownership.

Wave 3 exit: the maximal profile has broad real provider coverage without core/provider coupling.

Wave 4 — Build the maximal derivative product

#361 — Add publication hygiene for metadata sanitization, secret detection, privacy redaction, and rights gates

Make public/commercial release a deliberate state transition rather than "files exist, therefore ship them."

#363 — Add derivative profiles and an everything artifact-forest expansion mode

This is the "jacked on steroids" switch: expand every reachable, allowed, available, validated branch under explicit storage/runtime/network/AI budgets.

#364 — Add a magazine publication profile and complete multi-channel release bundle

Use the generic profile system to produce a magazine issue's print, digital, editorial, preview, metadata, provenance, checksum, and package derivatives.

Existing #348 — Add a rights-aware coloring-book publication profile and line-art pipeline

Optional specialized publication branch.

Existing #349 — Evaluate repository briefings and podcast derivatives from canonical content

Optional audio/podcast enrichment branch.

Existing #350 — Add a Slidev-backed product presentation publication profile

Optional presentation branch.

#377 — Add a Lulu-compliant print and EPUB adapter pack

Prove that provider-specific commercial rules can extend the generic publication profile without entering core domain logic or performing publication side effects.

Wave 4 exit: one reviewed source publication can produce a validated multi-channel release forest in one shared DAG, with unavailable/blocked branches explicitly explained.

Suggested execution order

For small, reviewable PRs, use this order unless implementation evidence changes a dependency:

#351
  ↓
#352 ─────── #356
  ↓            ↓
#353         #359
  ↓            ↓
#354         #365
  ↓
#355 ─────── #357
  ↓            ↓
#360 ──────────┘
  ↓
#358
  ↓
#362 → #344 / #345
  ↓
#361
  ↓
#363
  ↓
#364
  ↓
#377

#366 should grow continuously alongside the implementation and become the completion proof rather than being postponed until the end.

Architecture guardrails

• Flow orchestrates; Renderflow transforms.
• Renderflow does not import mutable sibling source.
• Canonical source is immutable; derivatives are artifacts.
• Formats are domain types; external tools are replaceable providers.
• No capability is "supported" without implementation + fixture + availability semantics + validation evidence.
• No human console text is an orchestration contract.
• No hidden network/AI execution in deterministic/local profiles.
• No maximal build is unbounded; budgets and policies are explicit.
• No public/commercial bundle bypasses configured privacy/rights/validation gates.
• Generated artifacts and docs are projections, not competing sources of truth.
• Every new adapter should fit the same artifact/process/provider contracts rather than creating a bespoke pipeline.
• Flow’s federated extension contract is tracked in egohygiene/flow#7; Renderflow owns only its domain-specific SDK and provider behavior.

Completion definition

This roadmap is complete when a synthetic magazine fixture and at least one real reviewed publication can be driven through the public Renderflow contract—directly or through Flow—to produce the configured artifact forest, interrupt and resume safely, validate every terminal artifact, emit provenance-complete manifests/checksums, and truthfully report unavailable, excluded, blocked, failed, reused, and produced branches. The proof includes a provider-specific Lulu candidate through #377 without placing Lulu logic in core.