No secret fetching
Authenticated URLs are never fetched or embedded. Credential-like query parameters stop the build.
A durable handoff, not another wiki
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
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
List files, public URLs, owners, expiry dates, and known gaps in a small YAML checklist that belongs in version control.
The CLI validates the schema, copies and SHA-256 hashes local files, and can check public links with rate limits and robots controls.
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
The bundle is ordinary HTML, JSON, CSS, JavaScript, and copied files. There is no proprietary database, hosted account, or runtime dependency.
{
"format": "knowledge-handoff-bundle/1",
"project": { "title": "Atlas migration" },
"summary": {
"artifacts": 3,
"verified": 2,
"gaps": 1
}
}✓ VERIFIEDRecord your copy
$ 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-linksThe fine print
Authenticated URLs are never fetched or embedded. Credential-like query parameters stop the build.
Link checking is opt-in, one request per origin per second, with a named user agent and robots awareness.
The generated site works from disk. Review progress remains local and exports as a plain JSON receipt.