beads/docs/related-projects.md
Chris Sells a86a2c5dfc docs: port user docs into the Mintlify site tree under docs/
Port the website's current (non-versioned) authored pages into docs/ as
Mintlify pages: frontmatter title as H1 (body H1s removed), Docusaurus
admonitions converted to Mintlify components, root-relative extensionless
links, mermaid fences kept as-is. website/docs/** is untouched and keeps
serving the Docusaurus site until cutover.

git-mv the user-facing docs/ originals with no website twin into the new
IA (core-concepts/, architecture/, workflows/, recovery/, multi-agent/,
integrations/, reference/), converted to Mintlify form. The six files
previously mirrored by sync-website-docs.sh now live once in the site.
ERROR_HANDLING.md and CONTRIBUTOR_NAMESPACE_ISOLATION.md move to engdocs/
(contributor pattern guide and design doc per content review).

Pointer stubs remain at docs/{DOLT,STORAGE-BACKENDS,PLUGIN,RECOVERY,
JSON_SCHEMA}.md because released bd binaries print those paths; QUICKSTART
and DOLT-BACKEND stay as existing pointer stubs.

Corrected while porting: the intro's storage diagram claimed data lives at
.beads/dolt/; embedded mode (the default) uses .beads/embeddeddolt/
(internal/storage/embeddeddolt/store.go), server mode uses .beads/dolt/.
2026-07-12 10:37:07 -07:00

1,004 B

title
Related Projects

Adjacent or complementary tools that solve different problems in the same neighborhood as Beads. These are not Beads integrations (see COMMUNITY_TOOLS.md for those) — they are independent projects whose users may also find Beads useful, or vice versa.

Recall / knowledge graph

  • scry — (scryspec.com) — marker-indexed knowledge and recall graph for AI coding agents. Files declare identity via inline @scry.entry markers; the index makes designs, lessons, and decisions reachable by meaning, tag, and seeded question rather than by path. Different job from Beads: where Beads is a task graph for what to do next, scry is a recall layer for what was decided and why. They compose — independently arrived at the same hash-based-ID convention (bd-a1b2, ~hash) for the same reason: preventing collisions across multi-agent and multi-branch work.