Project Continuity Kit
Create continuity reports and deterministic metadata-only bundles whose recorded scan scope is reused when checking repository drift.
The problem it solves
Project Continuity Kit Build and verify a portable, redacted handoff and recovery package from a local repository. Version 1.2 inventories files without copying their contents, fingerprints the repository, detects operational signals, records six continuity domains, audits missing knowledge, observes declared recovery prerequisites without executing commands, and compares an existing bundle with the current working tree.
Who Project Continuity Kit is for
- Developers and maintainers who need reviewable evidence before changing or releasing software.
- Users working with project continuity, handoff, recovery who want the documented v1.3.1 behavior.
- People who prefer an open-source release with visible limitations, source, and license terms.
Intended result
Create continuity reports and deterministic metadata-only bundles whose recorded scan scope is reused when checking repository drift.
This summary is reconciled from the current catalog and repository documentation.
Features in v1.3.1
Capabilities below come from the current project README and release documentation.
Build and verify a portable, redacted handoff and recovery package from a local repository. Version 1.2 inventories files without copying their contents, fingerprints the repository, detects operational signals, records six continuity domains, audits missing knowledge, observes declared recovery prerequisites without executing commands, and compares an existing bundle with the current working tree.
Verified examples
Screenshots are shown only when the current README references a local source image. Otherwise, repository example files are linked directly.
Platforms and implementation
The public release claims only the cataloged platforms and technologies.
Supported platforms
- Windows
- macOS
- Linux
Built with
- Python
Changelog
Release notes from the canonical v1.3.1 source tag.
New reports include scan_scope version 1: sorted unique excluded_names (the effective defaults plus custom path-component names) and environment_files set to exclude-dotenv-except-example. Bundle verification validates and reuses this scope, so excluded additions and edits do not count as drift while included changes do. Unknown policy versions, malformed objects, unsafe names and missing default exclusions are rejected. Legacy bundles use validated privacy.excluded_names when available; bundles without that metadata use documented defaults and report scan_scope_source as legacy-defaults. Scope provenance is explicit in verification output. ZIP output remains deterministic and contains file metadata rather than source contents. Recovery, restore and deployment commands are never executed.
- Validate continuity inputs and add an HTML handoff with evidence links, ownership coverage and changes since a prior report.
- Added regression coverage for the audited behavior and invalid inputs.
- Added non-executing recovery drills for required commands, files, artifact patterns, declared environment names, and documented commands.
- Added bundle-to-working-tree verification with current and recorded fingerprints, file drift, missing capability signals, and current continuity gaps.
- Recorded explicit privacy evidence that environment values are not read and arbitrary recovery commands are not executed.
- Added six structured continuity domains covering architecture, operations, dependencies, deployment, recovery, and handoff.
- Added secret-key and operator-term redaction, repository capability signals, continuity gap analysis, recovery evidence, previous-manifest diffs, and aggregate fingerprints.
- Added deterministic ZIP continuity bundles containing the structured manifest, handoff report, and verification record without copying repository contents.
- Released the first complete Project Continuity Kit command-line workflow.
- Added deterministic JSON and Markdown reporting, representative examples, and cross-platform tests.
Quick start
The shortest documented path into the current release.
Before running these source commands, download the v1.3.1 source archive, extract it, and open a terminal in the extracted project folder containing README.md. Follow the tagged README for required runtimes and any platform-specific setup.
python -m pip install .
continuity-kit examples/sample.json
continuity-kit examples/sample.json --format json --output continuity.json --bundle continuity.zip
continuity-kit --verify-bundle continuity.zip --root path/to/repository --format jsonThe deterministic ZIP contains continuity.json, HANDOFF.md, and VERIFY.txt. It never contains source files. Existing reports and bundles are never overwritten.
Current limitations
These boundaries are part of the product and prevent the page from implying unverified capability.
Everything runs locally. .git, real environment files, virtual environments, dependencies, and build outputs are excluded by default. File paths, byte counts, and SHA-256 hashes are recorded; file contents are never included in the package. Environment values are never read.
A green handoff or recovery-drill result means the declared evidence contract is satisfied. It does not prove that a restore, build, or deployment works. Command availability and documentation presence are observations, not execution evidence.
Python 3.10 or newer is supported on Windows, macOS, and Linux with no runtime dependencies, telemetry, account, or hosted service.
Privacy and licensing
Review the actual data boundary before using a tool with sensitive inputs.
Privacy and safety
Everything runs locally. .git, real environment files, virtual environments, dependencies, and build outputs are excluded by default. File paths, byte counts, and SHA-256 hashes are recorded; file contents are never included in the package. Environment values are never read.
A green handoff or recovery-drill result means the declared evidence contract is satisfied. It does not prove that a restore, build, or deployment works. Command availability and documentation presence are observations, not execution evidence.
Python 3.10 or newer is supported on Windows, macOS, and Linux with no runtime dependencies, telemetry, account, or hosted service.
License and release
Project Continuity Kit is published under MIT. The current cataloged release is v1.3.1, published 2026-10-16.
Related projects
Related projects are selected deterministically from shared catalog tags, category, and implementation technologies—not popularity or paid placement.
Project Continuity Kit v1.3.1
Use the tagged release for downloads and release notes. Use the repository for source, issues, contribution guidance, security reporting, and complete documentation.
Page source: current Forge catalog plus README and CHANGELOG from the canonical GitHub release tag. Fingerprint: 9e73e8886f574b18.