WorkflowMoves

The guarded workflow layer of DanceFlow

WorkflowMoves

Make the whole ecosystem usable, safely.

WorkflowMoves packages versioned rules, task guides, portable agent skills, evidence gates and an additive installer. It helps people and coding agents bring the right DanceFlow capabilities into a project while preserving its existing instructions, privacy boundaries and publication controls.

WorkflowMoves diagram showing reviewed sources passing through guarded routes into preserved project instructions
Generated WorkflowMoves 0.1.36 architecture illustration. It explains the contract; it is separate from evidence that a particular workspace installed a route.

What it gives you

A reviewable path from released capability to working project.

Guarded installation

The installer checks exact anchors, known predecessors, conflicts and every selected route before writing. Unknown or edited managed blocks stop without replacing surrounding project text.

Whole-ecosystem routing

Current guides connect FrameRudiments, StemLab, DanceRudiments, DanceMoves, PixelCue, PrismMoves, MediaSlide and the rest of DanceFlow through their supported file and API contracts.

Evidence gates

Previewed, installed, invoked, reviewed, published and verified-live remain distinct states. A clean check or saved instruction never becomes an invented outcome.

People and agent guidance

Each route keeps human decisions, agent actions, privacy, model storage, cost limits and publication permissions visible beside the technical steps.

Working example

Preview the exact route set before any write.

Check the current release

Compare the latest stable GitHub release with the source you will actually run. Read its release notes, capability reference and Potential problems.

Preview

python install.py --root "Z:\My Songs" --routes tool-adoption-routes.json --check

The check validates the entire selected set before writes. Review every proposed destination and conflict.

Apply and read back

python install.py --root "Z:\My Songs" --routes tool-adoption-routes.json

Read the changed files again and verify the owning workflow actually uses the released tool. Installation alone is not integration evidence.

Complete suite

One workflow layer, independently useful tools.

WorkflowMoves keeps each package in its own area of responsibility and helps tasks compose only what they need.

  • StemLab
  • DanceRudiments
  • FrameRudiments
  • DanceMoves
  • KeywordMoves
  • RasterMoves
  • LikenessForge
  • PixelCue
  • PrismMoves
  • ThumbMoves
  • React Timeline Sequence
  • MediaSlide
  • EPK Social Metadata
  • DanceVault
  • Potbot
  • DanceFlow for Unity
  • DanceFlow toolkit

Model weights and model caches stay under the owning project’s ignored models/. Short Shifter keeps its independent identity outside DanceFlow.

Verified baseline

Tested rules with explicit limits.

123 tests

WorkflowMoves 0.1.41 passed 123 tests, with required Windows/Linux CI and tagged release checks. Tests cover additive installation, repeat runs, conflict stops, evidence validators and complete workflow-contract membership.

Immutable release assets

The verified v0.1.41 baseline contains a versioned archive and SHA-256 manifest. DanceFlow 0.1.17 indexes WorkflowMoves in its release preflight, catalogue and portable skills.

A passing test or route preview cannot prove that a destination workspace adopted the change, that an external service accepted it, or that a public page was saved. Verify each of those outcomes separately.

Built for people and agents working together.

For people

Choose the task, review the proposed route set and keep the decisions that need your authority clear. The tools provide evidence and repeatable steps without turning a catalogue into automatic consent.

For agents

Inspect released, installed and imported identities. Prefer maintained primitives to copied helpers. When a task exposes a reusable gap, improve the smallest correct canonical owner with tests, documentation and a public-safe example.

Current capability and package audit · 23 October 2026

Current features and supported handoffs

The 0.1.41 integration adds checked workflow contracts for seventeen components plus the separate toolkit, a membership-derived coverage checker, development-learning guidance and guarded installation routes. The structural check does not establish native execution, complete chat-history recovery or adoption by another running chat.

Released 0.1.43 also provides a local social-publication calendar and read-only preflight for exact file and payload hashes, named timezone/UTC agreement, duplicate assets, slot collisions, rolling native date windows and retained receipts. Pending saves, private drafts, native schedules and verified publication remain separate. It prepares a plan; native platform uploads and scheduling are separate operations. Read the direct social scheduling guide.

Official stable source inspected: v0.1.41. Read the complete feature, package and example reference.

Unity recording and Potbot host handoffs keep source previews, installed runtime and qualified execution separate. Existing embedded examples retain their declared versions.