mirror of
https://github.com/basicmachines-co/basic-memory
synced 2026-06-21 13:47:35 +00:00
a148e72f56
Signed-off-by: phernandez <paul@basicmachines.co> Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
2.5 KiB
2.5 KiB
title, type, entity, version, schema, settings
| title | type | entity | version | schema | settings | ||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Manpage | schema | Manpage | 1 |
|
|
Manpage
A ManpageNote is one page of a Unix-style manual implemented as Basic
Memory notes (issue #952): commands in section 1, MCP tools in section 3,
file formats in section 5, concepts in section 7, admin in section 8. The
manual becomes a knowledge graph — SEE ALSO entries are typed relations,
and pages are found by structured recall:
search_notes(metadata_filters={"type": "manpage", "section": 3}).
This schema is an opt-in seed for documentation projects; the canonical
manual lives in the Basic Memory team workspace manual project.
What makes a good ManpageNote
- NAME / SYNOPSIS / DESCRIPTION — classic man-page structure, with PARAMETERS, MCP USAGE, CLI EQUIVALENT, EXAMPLES, GOTCHAS, SEE ALSO where applicable.
- Verified examples — EXAMPLES contain only commands that actually ran;
the
verifiedfield records the version and path (mcp, cli, or both). - generated — declares regeneration ownership:
registry(from the MCP tool registry) andtyper(from CLI help) pages get mechanical sections rewritten; curated sections (EXAMPLES, GOTCHAS, SEE ALSO, observations) are never overwritten. - gotcha / bug observations — field knowledge accumulates on pages without being clobbered by regeneration; bugs link their tracking issues.
Frontmatter
type: manpage plus section makes the manual queryable like man -k:
by section, by tool, by command, or by missing/stale verified stamps.
Validation is warn, never blocking.