| type | Architecture | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| title | 5-Layer System Architecture | ||||||||||||||||||
| description | Structural separation of concerns across the OKF specification, agent convention, skills, deterministic tooling, and knowledge corpus. | ||||||||||||||||||
| resource | https://github.com/okf-memory/okf-agent-memory | ||||||||||||||||||
| tags |
|
||||||||||||||||||
| generated |
|
||||||||||||||||||
| status | stable | ||||||||||||||||||
| sources |
|
OKF Agent Memory strictly separates semantic reasoning from syntax handling through a 5-layer stack.1
flowchart TD
L1["1. OKF v0.2 Specification<br/>(Normative Markdown & YAML Format)"]
L2["2. Agent Memory Convention<br/>(Behavioral Rules: Search, Review, Trust)"]
L3["3. Agent Skill<br/>(LLM Prompts & Operational Workflows)"]
L4["4. Tooling Layer: Go Library & CLI<br/>(Deterministic Parsing, Serialization, Validation)"]
L5["5. Project Knowledge Corpus<br/>(knowledge/ OKF Bundle)"]
L1 --> L2
L2 --> L3
L3 --> L4
L4 --> L5
The data representation contract. Defines concept frontmatter (type, sources, generated, verified, status), index files, and log.md.
Defines agent behavior around the format without altering OKF syntax.2 Governed by convention/principles and convention/lifecycle.
Teaches an AI agent how and when to execute memory operations (e.g. running search queries, discovering relevant concepts, structuring updates). Connects to the broader project as described in project/overview.
Ensures format correctness, validates links, maintains index files, and manages frontmatter metadata deterministically without placing parsing burdens on the LLM, as decided in tooling-decision. Tracked under roadmap/milestones.
The version-controlled knowledge/ directory holding the actual durable concepts, cross-links, and change log.
- Bundle Isolation and Mutation Security Boundaries: Layer 4 tooling enforces security boundaries and bundle isolation
- Engineering & Coding Best Practices (Clean Code, TDD, DRY): Coding standards governing Layer 4 Go tooling development
- Governance vs. Execution Context and Code Binding: Specifies the 3-tier epistemic governance model and code-to-knowledge binding
- OKF Registry Client, Dependency Locking, and Multi-Scope Vendor Layering: Multi-scope resolution and registry distribution expand the tooling and knowledge layers