Knowledge · Governed · Federated
A garden you tend. An oracle you consult.
Hard-won technical knowledge, structured for AI retrieval. Not documentation. Not Q&A. A governed collection of gotchas, techniques, and undocumented behaviours — captured once, found when needed.
Get started in three steps
In any Claude Code session, point it at the Hortora marketplace. Skills install automatically — no scripts, no config.
When something non-obvious surfaces, forage generates a collision-free GE-ID locally and opens a PR. No GitHub issue needed — CI validates automatically on every PR.
GitHub Actions validates every submission — format, score threshold, duplicate scan, injection check — and posts a result comment. On merge, indexes update automatically.
What Hortora is
Entries are plain markdown with structured fields — symptom, root cause, fix, why non-obvious. Claude finds the right entry in three tool calls, under 1,500 tokens, regardless of garden size.
CI validates every PR — format, score threshold (≥ 8), injection scan, Jaccard duplicate check. On merge, indexes update automatically. No manual curation step. The editorial bar is enforced before anything reaches the garden.
Canonical gardens set the standard. Child gardens enrich them with local context. Peer gardens share across domains. Each garden remains sovereign — no centralisation required.
"A Claude session would go in circles on something solved in a different session. Each new context window was a blank slate. The fix was obvious: capture the hard-won stuff before context closes."
— The Rootstock: How the Hortora Garden was Germinated
Repositories
The root canonical garden. 169+ entries. CI validates every submission — PR-based, automated, governed.
activeThe open protocol specification — federation rules, entry format, governance, and the design diary.
activeThe engine — forage and harvest skills, validate_pr.py, integrate_entry.py, GitHub Actions workflows, garden-setup.sh.
active