This page collects the smallest reviewable examples that prove xflow's public claims without requiring a private tracker, npm publish, or a production repo.
Use it as an evaluator map: start with the clean local smoke, then move to the workflow path that matches the change type.
Best for: first-time evaluators, CI, package reviewers.
xflow demo cleanWhat it proves:
- a brand-new project can initialize xflow without copying internal workflow files
.xflow/GOAL.mdbecomes a durable project artifact and passes goal audit- doctor and
workflow validate yolopass against the clean consumer project
Reference docs:
docs/demo-proof.mddocs/adoption/openflow-release-hardening.mddocs/adoption/README.md
Best for: backend, docs, infra, and small UI changes.
xflow init --project-root .
xflow goal set "Ship the next verified change" --project-root .
xflow goal audit --project-root . --json
xflow workflow validate yolo --project-root .What it proves:
.xflow/GOAL.mdis a durable project artifact, not a thread-only reminderxflow:goalis useful when yolo uses it as direction context- the lite workflow is executable data with TDD and archive gates
Reference docs:
docs/goal-vs-codex.mddocs/launch-demo.mddocs/walkthrough.md
Best for: product, UI, competitor-led, or multi-agent work.
xflow goal show --json
xflow goal audit --json
xflow corps --explain --jsonWhat it proves:
- corps is governed by a proof contract instead of a loose prompt chain
- visual benchmark, no-stub runtime witnesses, and final proof review are named
- goal alignment remains visible before and after heavy-track work
Reference docs:
docs/corps-operator-guide.mddocs/launch-demo.mddocs/quality-assessment.md
Best for: teams that already use GitHub Issues, Jira, Linear, or another tracker.
xflow adapter import-file --input docs/fixtures/tracker-item.json --project-root .What it proves:
- external systems can supply context without owning xflow workflow truth
- local change artifacts stay reviewable inside the repository
- adapter work can be tested without live service credentials
Reference docs:
docs/integrations.mddocs/public-benchmark.mddocs/fixtures/tracker-item.json
Best for: maintainers preparing a public launch.
xflow launch dossier
xflow launch audit --pre-publish --strict --json
xflow package preflight --check-registry --check-auth --jsonWhat it proves:
- score, goal, adoption, package, and launch claims are audited together
- the irreversible npm publish step is blocked until identity and registry evidence are present
- missing surfaces are explicit rather than buried in prose
Reference docs:
docs/launch-dossier.mddocs/public-release.mddocs/npm-publish-handoff.md