Reference Directory

Type: kb/types/index.md

← Parent

Subdirectories

Files

  • Agent memory coverage (note) - How commonplace's shipped surfaces realize agent-memory requirements: control plane, contracts, storage roles, validation, review, activation, promotion, lifecycle, and current gaps
  • Available types (note) - Catalog of the types shipped by commonplace — global base and utility types plus directory-scoped specialised types delivered with the framework scaffold
  • Collections and types (note) - How collections and types compose in commonplace - collections own register conventions and per-destination outbound linking rules, types own structural contracts declared in type-spec docs, and the two meet through path-valued type pointers listed in COLLECTION.md; covers the COLLECTION.md surface and the live per-destination model the write and connect skills consume
  • Commonplace agent memory gap plan (note) - Plan for closing Commonplace's current agent-memory gaps: session traces, candidates, cue activation, behavioral evaluation, lifecycle, source alignment, import, ranking, and authority
  • Commonplace architecture (note) - Shipped commonplace architecture — installed project layout, packaged runtime, scaffolded library under kb/commonplace/, empty user collections, promoted skills, and the library/user boundary
  • Commonplace CLI commands (note) - Reference for the commonplace-* CLI commands shipped by llm-commonplace - project setup, validation, indexing, snapshots, note operations, and the review system
  • Commonplace library (commonplace.lib) (note) - Internal API reference for commonplace.lib - frontmatter, naming, note_parser, type_resolver, validation, and relocation modules used by CLI commands and the review system
  • Control-plane goals (note) - How commonplace ships KB goals in always-loaded context — the AGENTS.md layout, the scaffolded AGENTS.md.template, and the install-time fill-in contract
  • Instruction generation (note) - Commonplace's shipped build-time instruction generation flow — scaffold trees, template substitution, the commonplace-init entry point, and the specific generated artifacts
  • Link vocabulary and linking approach (note) - Commonplace's linking approach: collection-owned outbound rules, reader-need labels, articulation tests, connect reports, and the shared label catalogue for COLLECTION.md authors
  • Navigation (note) - How agents navigate a commonplace KB using control-plane pointers, rg, titles/descriptions, indexes, links, connect reports, and possible future search layers
  • Review system architecture (commonplace.review + commonplace.cli.review) (note) - Code architecture for commonplace.review and commonplace.cli.review - package layout, data model, single-note bundle execution, targeting, prompt format, and repair utilities
  • Scenario architecture (note) - Scenario-derived shipped architecture — single KB root with a library/user split under kb/commonplace/, package-provided commands, promoted skills, and a measurable scenario decomposition
  • Storage (note) - Where commonplace stores data — authored markdown under kb/, derived indexes rebuilt from those files, and the review subsystem's local SQLite database
  • Type loading (note) - How commonplace resolves a note's type contract at authoring and validation time - collection-scoped lookup, collection conventions, and skill-driven on-demand loading
  • Writing conventions for kb/reference/ (descriptive register)