mirror of
https://github.com/okf-memory/okf-agent-memory.git
synced 2026-10-01 18:25:09 +00:00
7cd556fb9f- Cap MCP tag length to 50 characters in tools.json schemas and handler - Replace repeated fsPassed FlagSet visits with local passed map in cmdUpdate - Add upfront non-empty type validation to cmdCreate - Link requirements/mutation-metadata in root knowledge/index.md - Document update flags and MCP tag length limit in docs/guides/CLI.md - Credit Rogelio (@rogeliodh) for issue #38 report and analysis in CONTRIBUTORS.md - Record knowledge updates in knowledge/log.md
1.8 KiB
1.8 KiB
| okf_version |
|---|
| 0.2 |
OKF Agent Memory Knowledge Base
The persistent knowledge corpus for the okf-agent-memory project, structured as a conformant Open Knowledge Format (OKF) v0.2 bundle.
Project
- OKF Agent Memory Overview - A domain-neutral persistent project-memory system for AI agents based on the Open Knowledge Format (OKF) v0.2.
- Why OKF Agent Memory (Value Proposition & Selling Points) - Key value propositions, strategic differentiators, and core selling points of the OKF Agent Memory ecosystem.
Architecture
- 5-Layer System Architecture - Structural separation of concerns across the OKF specification, agent convention, skills, deterministic tooling, and knowledge corpus.
- Go Single-Binary CLI & MCP Architecture Decision - Architectural decision to implement the deterministic OKF tooling layer as a standalone Go binary with dual CLI and MCP support.
Convention
- Core Memory Principles & Agent Contract - Foundational design principles and minimal behavioral guarantees for agents maintaining persistent project memory.
- Knowledge Lifecycle & Review Workflow - Operational lifecycle stages and the Read-Before-Write loop for discovering, persisting, and updating project knowledge.
Roadmap
- Project Roadmap & Development Milestones - Phased implementation roadmap from specification validation to Go library, CLI tooling, cross-agent testing, and zero-knowledge hub sync.
Requirements
- Metadata Mutation Parity for CLI and MCP - CLI and MCP creation and update must expose type, status, and tags with explicit replacement semantics and valid lifecycle values.