A durable handoff, not another wiki

Leave the project.
Not the context.

Turn one readable YAML file into an offline bundle of source-of-truth files, checked links, accountable owners, expiry warnings, known gaps, and a recipient receipt.

Free and open source · No account · No telemetry

A collage of a cassette whose tape leads to four checked project folders
One packet. Every track labelled.

The dropout

“I sent the wiki and the drive folder. I thought the rest was obvious.”

The next owner should not have to reconstruct which document mattered, which link expired, or who still owes access.

Side A / workflow

Three tracks. One handoff.

  1. 01

    Write the truth down

    List files, public URLs, owners, expiry dates, and known gaps in a small YAML checklist that belongs in version control.

  2. 02

    Verify the copy

    The CLI validates the schema, copies and SHA-256 hashes local files, and can check public links with rate limits and robots controls.

  3. 03

    Hand over the tape

    Send one static directory. The recipient can browse it offline, mark reviewed items, and export a receipt tied to the manifest hash.

Side B / transparent by design

Readable after the tool is gone.

The bundle is ordinary HTML, JSON, CSS, JavaScript, and copied files. There is no proprietary database, hosted account, or runtime dependency.

  • Local files copied and SHA-256 hashed
  • Public links checked only when requested
  • Credential-like URLs blocked before output
  • Owners, expiry, and gaps stay first-class
MANIFEST.JSONWRITE-ONCE COPY
{
  "format": "knowledge-handoff-bundle/1",
  "project": { "title": "Atlas migration" },
  "summary": {
    "artifacts": 3,
    "verified": 2,
    "gaps": 1
  }
}
✓ VERIFIED

Record your copy

From checklist to bundle.

SHELL / 01EXIT 0
$ cargo install --git https://github.com/B-Divyesh/sf-knowledge-handoff-bundle
$ khb init handoff.yaml
$ khb check handoff.yaml
$ khb build handoff.yaml --output ./bundle --check-links

The fine print

Trust comes from limits.

No secret fetching

Authenticated URLs are never fetched or embedded. Credential-like query parameters stop the build.

No invisible traffic

Link checking is opt-in, one request per origin per second, with a named user agent and robots awareness.

No hidden cloud

The generated site works from disk. Review progress remains local and exports as a plain JSON receipt.