Use this checklist before tagging or publishing a Falsiflow release.
- Confirm the version in pyproject.toml matches falsiflow/init.py.
- Update CHANGELOG.md for the release version.
- Confirm the PyPI package metadata in pyproject.toml:
requires-python, keywords, classifiers, and project URLs for homepage, docs, source, issues, changelog, demo, architecture, data contract, casebook check, citation, and governance. - Confirm README.md, CONTRIBUTING.md, CITATION.cff, CODE_OF_CONDUCT.md, GOVERNANCE.md, SUPPORT.md, ROADMAP.md, and docs/falsiflow_architecture.md plus docs/falsiflow_data_contract.md, docs/falsiflow_adapter_profiles.md, docs/falsiflow_casebook_check.md, docs/falsiflow_security_posture.md, docs/falsiflow_template_authoring.md, docs/falsiflow_troubleshooting.md, and docs/falsiflow_1k_launch_plan.md describe the current citation, community, governance, security, architecture, data contract, adapter profiles, casebook proof, template authoring, troubleshooting, launch, supply-chain, and release posture.
- Confirm SECURITY.md and RESPONSIBLE_USE.md still match the release behavior and evidence-boundary language.
- Confirm
.github/dependabot.ymlstill tracks GitHub Actions and Python packaging inputs, and.github/workflows/falsiflow-scorecard.ymlstill runs OpenSSF Scorecard with SARIF upload. - Confirm scripts/install_local.sh, scripts/install_local.ps1, and Makefile still install and launch the local browser app.
- Confirm action.yml still exposes the reusable GitHub Action
for
claim-check,template-check,casebook-check,release-check,adoption-check,quickstart, andexternal-checkmodes. - Confirm docs/falsiflow_adoption_priorities.md still matches the current optimization priorities.
- Confirm docs/falsiflow_mvp.md describe any new public commands, schemas, community expectations, support boundaries, roadmap direction, security posture, or release gates.
python3 -m py_compile \
falsiflow/core.py \
falsiflow/cli.py \
falsiflow/adapters.py \
falsiflow/release.py \
falsiflow/adoption.py \
falsiflow/casebook_check.py \
falsiflow/bundle.py \
falsiflow/browser_demo.py \
falsiflow/demo.py \
falsiflow/discovery.py \
falsiflow/local_server.py \
falsiflow/public_release.py \
falsiflow/claim_check.py \
falsiflow/doctor.py \
falsiflow/quickstart.py \
falsiflow/scaffold.py \
falsiflow/template_discovery.py \
falsiflow/template_gallery.py \
falsiflow/template_check.py \
falsiflow/template_pack.py \
falsiflow/template_registry.py \
falsiflow/template_provenance.py \
falsiflow/template_release.py \
falsiflow/template_install.py \
scripts/falsiflow.py \
scripts/falsiflow_tests/regress_falsiflow_core.py
python3 scripts/falsiflow_tests/regress_falsiflow_core.py
scripts/install_local.sh --from-local . --prefix /tmp/falsiflow_install_check --check
python3 scripts/falsiflow.py onboard --out-dir /tmp/falsiflow_onboard_check --check --json
python3 scripts/falsiflow.py static-demo --out-dir /tmp/falsiflow_static_demo_check --force --json
python3 scripts/falsiflow.py demo-package --out-dir /tmp/falsiflow_public_demo_check --force --json
python3 scripts/falsiflow.py publish-kit --out-dir /tmp/falsiflow_publish_kit_check --force --json
python3 scripts/falsiflow.py launch-kit --out-dir /tmp/falsiflow_launch_kit_check --force --json
python3 scripts/falsiflow.py external-evidence --out /tmp/falsiflow_external_evidence.json --force --json
python3 scripts/falsiflow.py external-check --out-dir /tmp/falsiflow_external_check --force
python3 scripts/falsiflow.py casebook-check --out-dir data/falsiflow/casebook_check --force
python3 scripts/falsiflow.py adoption-check --out-dir data/falsiflow/adoption_check --force
python3 scripts/falsiflow.py release-check --out-dir data/falsiflow/release_check --forceThe final release-check must report:
release_readypackage_readyadoption_readyrelease_validation_readydist_readydemo_package_readypublish_kit_readyfor the generated release handoff kitlaunch_kit_readyfor public copy, proof card, demo script, launch metrics, and maintainer checklistexternal-evidencehas produced a structured evidence file for hosted demo, public PyPI package URL, checkout-based pipx smoke, public-package pipx smoke, Windows/PowerShell smoke results, the expected PyPI package version, and the PyPI JSON API response- the
Falsiflow External Evidenceworkflow artifact includesfalsiflow_external_evidence.json,falsiflow_pypi_project.json,falsiflow_expected_version.txt,falsiflow_pypi_version.txt,external_readiness.json, andexternal_readiness.mdfor the final public demo URL and PyPI package; the PyPI JSONpublished_versionmust match the workflowexpected_versioninput or the version inpyproject.toml external_check_statusisexternal_readyfor a public release, orexternal_blockedonly while public repo/demo/PyPI URLs, pipx public-package smoke, or Windows validation are intentionally pending- if PyPI returns
invalid-publisher, the maintainer has followed docs/falsiflow_pypi_trusted_publishing.md and configured the pending publisher or existing-project trusted publisher with projectfalsiflow, ownerAzurLiu, repositoryfalsiflow, workflowfalsiflow-publish.yml, and environmentpypi - zero package failures
- zero dist failures
- one-command
quickstartreportsquickstart_ready quickstart_summary.jsonincludes doctor handoffnext_commands- one-command
doctor --project-dirreportsdoctor_ready doctor_summary.jsonincludes arepair_checklist- one-command
claim-check --project-dirreportsclaim_check_ready - audit review decision cards generated and bundled
- all starter bundles verified
- template gallery ready with the bundled cross-domain starters
casebook_check_readywith positive demo proofs, placeholder blockers, source provenance, verified bundles, and reviewer replay scripts across bundled starters- packaged starter template pack verified
- template registry ready and template lock written
- registry
source_urland lockfile SHA-256 source pin verified - packaged starter template pack installed with
template_installed - template release bundle verified with
template_release_verified - packaged starter template release installed with
template_installed adoption_check.jsonreports all five priorities readyadoption_check.jsonincludes arepair_checklistcommand with expected artifact and success signal- PyPI metadata declares
requires-python, discovery keywords, audience/topic classifiers, and project URLs for homepage, docs, source, issues, changelog, demo, architecture, data contract, adapter profiles, casebook check, citation, and governance - architecture documentation is present:
docs/falsiflow_architecture.md - data contract documentation is present:
docs/falsiflow_data_contract.md - adapter profile documentation is present:
docs/falsiflow_adapter_profiles.md - casebook-check documentation is present:
docs/falsiflow_casebook_check.md - template authoring documentation is present:
docs/falsiflow_template_authoring.md - troubleshooting documentation is present:
docs/falsiflow_troubleshooting.md - community trust files are present:
CODE_OF_CONDUCT.md,SUPPORT.md, andROADMAP.md - citation and governance files are present:
CITATION.cffandGOVERNANCE.md - security posture files and automation are present:
SECURITY.md,docs/falsiflow_security_posture.md,.github/dependabot.yml, and theFalsiflow Scorecardworkflow with SARIF upload - local build caches such as
build/andfalsiflow.egg-info/are not left behind by the distribution gate - zero unsafe paths, unmanifested files, or registry/lock SHA-256 mismatches in the template release verification report
- GitHub Actions workflow files exist for full CI, GitHub Pages demo deploy, cross-platform Windows/macOS/Linux smoke tests, pipx smoke tests, external evidence artifact capture with PyPI JSON expected-version verification, OpenSSF Scorecard reporting, and PyPI trusted-publishing release builds
action.ymlexists for downstream GitHub Actions adoption and the main CI workflow runs a reusable-action quickstart smoke
Inspect these generated files before publishing:
data/falsiflow/release_check/release_check.md, especially theRelease Review Artifact Indexlinking claim-check, source manifest, bundle verification, evidence bundle, and template release verification artifactsdata/falsiflow/release_check/release_check.jsondata/falsiflow/release_check/release_check.mddata/falsiflow/release_check/public_demo/demo_package_summary.jsondata/falsiflow/release_check/public_demo/publish_checklist.mddata/falsiflow/publish_kit/publish_handoff.jsondata/falsiflow/publish_kit/github_publish_commands.shdata/falsiflow/release_check/publish_kit/public_release_evidence.jsondata/falsiflow/release_check/publish_kit/public_release_evidence.mddata/falsiflow/release_check/publish_kit/release_rehearsal.jsondata/falsiflow/release_check/publish_kit/release_rehearsal.mdfor the public release rehearsal commands, expected artifacts, success signals, and strict external stop conditionsdata/falsiflow/release_check/launch_kit/launch_summary.jsondata/falsiflow/release_check/launch_kit/proof_card.mddata/falsiflow/release_check/launch_kit/announcement.mddata/falsiflow/release_check/launch_kit/demo_script.mddata/falsiflow/release_check/launch_kit/readme_proof_strip.svgdata/falsiflow/release_check/launch_kit/social_preview.svgdata/falsiflow/release_check/launch_kit/github_repo_profile.mddata/falsiflow/release_check/launch_kit/launch_posts.mddata/falsiflow/release_check/launch_kit/launch_metrics.jsondata/falsiflow/release_check/launch_kit/launch_metrics.mddata/falsiflow/release_check/launch_kit/maintainer_checklist.mddata/falsiflow/release_check/launch_kit/publish_kit/public_release_evidence.mddata/falsiflow/release_check/launch_kit/publish_kit/release_rehearsal.mddata/falsiflow/release_check/publish_kit/external_evidence_template.jsondata/falsiflow/release_check/external_readiness/external_readiness.jsondata/falsiflow/release_check/external_readiness/external_readiness.mddata/falsiflow/release_check/adoption_check.jsondata/falsiflow/release_check/adoption_check.mddata/falsiflow/adoption_check/adoption_check.jsondata/falsiflow/adoption_check/adoption_check.mddata/falsiflow/release_check/quickstart_project/quickstart_summary.jsondata/falsiflow/release_check/quickstart_project/quickstart_summary.mddata/falsiflow/release_check/doctor/doctor_summary.jsondata/falsiflow/release_check/doctor/doctor_summary.mddata/falsiflow/release_check/doctor/project_validation.jsondata/falsiflow/release_check/doctor/evidence_diagnostics.jsondata/falsiflow/release_check/claim_check/claim_check.jsondata/falsiflow/release_check/claim_check/claim_check.mddata/falsiflow/release_check/claim_check/evidence_bundle_verify.md- the
Review Artifact Indexsections inclaim_check.md,evidence_bundle_verify.md, andtemplate_release_verification.md data/falsiflow/release_check/demo/audit/audit_review.jsondata/falsiflow/release_check/demo/audit/audit_review.mddata/falsiflow/release_check/template_gallery.jsondata/falsiflow/release_check/template_gallery.mddata/falsiflow/release_check/casebook_check/casebook_reviewer_replay.mddata/falsiflow/release_check/casebook_check/casebook_reviewer_replay.shdata/falsiflow/release_check/casebook_check/casebook_reviewer_replay.ps1data/falsiflow/release_check/template_pack.zipdata/falsiflow/release_check/template_pack_verification.mddata/falsiflow/release_check/template_registry.jsondata/falsiflow/release_check/falsiflow_template_lock.jsondata/falsiflow/release_check/falsiflow_template_lock.attestation.jsondata/falsiflow/release_check/falsiflow_template_policy.jsondata/falsiflow/release_check/template_release.zipdata/falsiflow/release_check/template_release_verification.jsondata/falsiflow/release_check/template_release_verification.mddata/falsiflow/release_check/template_install_templates/falsiflow_template_index.jsondata/falsiflow/release_check/dist/wheel/*.whldata/falsiflow/release_check/dist/sdist/*.tar.gz
The wheel must install in isolation and pass installed-package release-check.
The sdist must include release docs, package modules, starter template data,
community templates, architecture documentation, template authoring
documentation, data contract documentation, adapter profile documentation,
casebook-check documentation, citation and governance files,
Dependabot config, Scorecard workflow, troubleshooting documentation, and the
security posture documentation. Security and responsible-use docs must be
present in the sdist.