obsidian-plugin/sparkwild_obsidian-tracekeeper
1
0
Fork 0
mirror of https://github.com/sparkwild/obsidian-tracekeeper.git synced 2026-07-22 17:50:29 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
sparkwild_obsidian-tracekeeper/docs
History
sparkwild 872c836dda
Release 0.2.2 review queue polish (#19) 
Release Tracekeeper 0.2.2 with review queue, task closeout, project history recall, and auto-refresh polish.
2026-06-03 15:27:19 +08:00
..
AGENT_MCP_USAGE.md Release 0.2.2 review queue polish (#19) 2026-06-03 15:27:19 +08:00
ARCHITECTURE.md Release 0.2.2 review queue polish (#19) 2026-06-03 15:27:19 +08:00
COMMUNITY_PLUGIN_SUBMISSION.md fix: complete community release readiness 2026-05-15 04:19:24 +08:00
DEVELOPMENT.md Release 0.1.6 2026-05-18 19:32:13 +08:00
KNOWLEDGE_ARCHITECTURE.md feat: add legacy structure organizer 2026-05-27 15:53:46 +08:00
README.md feat: add unified knowledge architecture 2026-05-26 14:48:08 +08:00

README.md

Tracekeeper Documentation

This directory keeps the maintained Tracekeeper product and release documentation. Runtime, permission, plugin-surface, and client-configuration notes are consolidated so there is one canonical place to update each topic.

Current Docs

  • Architecture: product architecture, plugin surface, MCP permissions, Runtime security, and agent client configuration.
  • Knowledge architecture: unified 00_tracekeeper / 01_knowledge / 02_archive layout, memory-wiki bridge rules, and lint constraints.
  • Agent MCP usage: cross-agent task start, project-scoped recall, closeout, and Review Queue proposal rules.
  • Cross-agent MCP workflow: practical start-task, project-scoped recall, task closeout, and Review Queue proposal handling.
  • Community plugin submission: Obsidian community checklist, release creation steps, and submission entry.
  • Development and release notes: repository layout, verification commands, release readiness, roadmap, and acknowledgement policy.

Core Boundary

  • Agent clients start knowledge work.
  • Obsidian is the human review and governance surface.
  • The vault is the durable knowledge layer.
  • Client connection details use local Runtime defaults that users can change; Tracekeeper does not hardcode vault paths, repository paths, or developer machine paths.
  • Graph health checks are configurable, but graph repair remains review-gated and never runs automatically.