Two editable definition documents
Edit the source and comparison graphs independently; inspect canonical identities and escaped JSON Pointer changes.
Developer tools / INTERACTIVE WORKSHOP
Workflow Tools v1.0.0Definition review and publication
Run actual Artisan validation, graphs, diff, reviewed publication and export against an isolated database. Edit full JSON data; fingerprints, file limits and immutable version conflicts are enforced by the installed packages.
01 / CONFIGURE
Choose a scenario. Change the inputs or build a sequence of commands.
02 / RUN
Execute the installed package against a new fictional example.
03 / INSPECT
Follow the result, actual calls, generated output and integration code.
THE WORKBENCH
Make it your example.
Your server-side changes are temporary. External-service examples use local response fixtures. Start with sample data.
Start with a preset, or change the input and run it.
The behavior is the example.
Your result will show the values, decisions and generated output from the actual package.
Calls used by this scenario. The handbook explains setup, authorizers, storage and error recovery.
The complete response is shown as data. Wide PHP integers are transported as exact decimal strings. Values are never evaluated as PHP or JavaScript.
Run an example to inspect its response.
The last two successful run states stay in this tab’s memory. Run a changed example to compare the actual package results.
What you can exercise here.
Literal CLI output and exit codes
Run the six installed commands with fixed host registration; data remains literal and rejected operations return their actual status.
Canonical fingerprint review
Whitespace is ignored while labels, assignments, targets and versions remain part of the reviewed identity.
Explicit reviewed apply
Preview creates no publication; apply requires the exact reviewed hash and reports actual saved definitions.
Immutable version conflicts
A changed snapshot cannot overwrite an existing name/version; a reviewed next version remains independent.
Export/read/diff round-trip
A host recipe exports the real saved definition, rereads it through DefinitionFiles and compares it through DefinitionDiff.
Legacy mapping blockers
Stored callbacks, cancellation meanings and extra metadata require explicit mapping; source behavior is never executed.
UNDERSTAND THE BEHAVIOR
Review a definition before publishing its canonical identity.
Build before/after graphs and explicit review commands. Inspect real diagnostics, diagrams, semantic diffs, fingerprinted publication, exports and legacy mapping plans.
Builders edit trusted definition data
Before and after step rows expose IDs, transitions, assignment strategy and parameters. Raw JSON can test parser boundaries such as duplicate keys. Every command is visible; replaying a prefix starts again with a fresh disposable definition store.
Diagnostics are actual command results
The runner captures literal command output and exit codes. Validation, graph, diff, publish, export and legacy-plan call the real package commands. A diagram projects validated structure; it does not execute transitions or authorize actors.
Preview and apply have different effects
Publish preview is read-only. Applying requires the exact reviewed fingerprint. A matching hash proves content identity, not user authentication. A published name/version cannot be overwritten; publish a new version for a deliberate change.
Round-trip composes package APIs; legacy planning is a package operation
Roundtrip runs the package export/read/diff path and reports the result; there is no workflow:roundtrip CLI. Legacy planning maps stored behavior for review and does not import domain records. Runtime history import belongs to the Workflow lab.
GO FURTHER
Try the boundary cases.
Change and review a graph
Edit a transition in the before step builder, then run validate and graph commands. Expected: invalid destinations produce package diagnostics; a valid graph produces text or Mermaid output. Use a label containing markup to confirm literal data remains text.
Compare definitions semantically
Edit the after version or a step, then run diff and diff with check. Expected: semantic changes and command exit status are explicit. Keeping both definitions equivalent produces an empty semantic difference; formatting alone is not a new runtime decision.
Preview, apply and export the exact definition
Use the default sequence for preview, apply and export: expected preview shows a fingerprint without writing and apply stores the reviewed content. Publish and verify export round-trip instead applies its known reviewed fixture hash and performs the host export/read/diff recipe. Add a separate preview command when editing. If you edit the definition, update expect intentionally from a fresh preview; a stale or omitted hash is refused.
Protect publication identity
Run Published name and version cannot be replaced, then Review and publish a new version. Expected: changed content cannot replace an existing published identity; the distinct reviewed version can be published. The hash check is still separate from application administrator authorization.
Inspect parser and migration boundaries
Run Duplicate object keys, Oversized file and Preserve a large numeric identity exactly. Expected: strict parser/size diagnostics or exact identity preservation. Run Legacy stored behavior requires explicit mapping and inspect its plan; it proposes reviewed mappings without executing old business actions.
COMPOSE THE RESPONSIBILITIESUseful alone.
Useful alone.
Better when the boundaries fit.
Tools reviews definitions and migration plans. Workflow owns runtime commands, receipts and saved-history import. Native Flow executes Laravel state transitions; neither diagram output nor a publication fingerprint replaces runtime actor policy.