Kw Okf Memory

KW-OKF Memory

Core Boundary

Use this skill to maintain a long-term Codex memory wiki that stays structured, can evolve safely, supports index-and-graph retrieval, and prevents silent AI writes. Recommend Obsidian for human review, search, backlinks, and navigation after commit, but keep Markdown and the glue script as the write/audit authority. KW-OKF is an opinionated, OKF-inspired memory profile; the internal Vault does not claim direct OKF v0.1 conformance. Use export-okf for an interoperable handoff bundle.

Keep the boundary clear: the Skill stores tools and protocol, the Vault stores long-term knowledge assets, the Python glue layer performs deterministic filesystem/index/audit work, and Codex extracts, judges, previews, and asks for confirmation.

Task Routing

• For preservation or write intents, including saving experience/rules/cases, distilling knowledge, creating or updating OKF pages, or updating long-term memory, read references/write_workflow.md plus references/okf_schema.md, references/vault_framework.md, and references/association_workflow.md as needed.
• For lookup intents that need specific existing records, read references/retrieval_workflow.md and references/wiki_lookup_workflow.md, then use search.
• For synthesis, judgment, planning, conflict-check, comparison, creative expansion, or lesson-extraction intents that need prior memory, read references/retrieval_workflow.md and references/wiki_lookup_workflow.md, then use think.
• For maintenance intents involving vault health, duplicates, conflicts, stale notes, orphan pages, missing links, or deep organization, read references/maintenance_workflow.md.
• For memory asset processing intents, preview with process-img --preview, then follow the confirmation and path rules in references/write_workflow.md and references/vault_framework.md.
• For interoperability or handoff intents, preview and run export-okf; keep the internal KW-OKF Vault unchanged.
• Use obsidian-open / obsidian-search only for human review. Obsidian is not the write or audit authority.

Load As Needed

• config.json: read before filesystem actions to locate the Vault and resolve language, image, and Obsidian settings. Structural safety rules are fixed by the Skill and script rather than configurable bypasses.
• references/write_workflow.md: formal writes, preview, confirmation, commit, and existing-knowledge updates.
• references/okf_schema.md: KW-OKF node types, frontmatter fields, body template, source refs, and official OKF compatibility boundary.
• references/vault_framework.md: fixed Vault skeleton, path safety, and directory creation rules.
• references/retrieval_workflow.md: search / think mode selection, synthesis, gap analysis, and staleness checks.
• references/association_workflow.md: lightweight write-time associations, relationship labels, and deep association cleanup.
• references/maintenance_workflow.md: manual maintenance flow, command roles, duplicate/conflict/staleness/orphan checks.
• references/wiki_lookup_workflow.md: wiki-style lookup, small reads, link following, and error-book rules.

Command Entry

Use the glue script for deterministic filesystem work:

python scripts/okf_glue.py  [options]

Common commands are init, build, audit, search, stage, commit, process-img, export-okf, obsidian-open, and obsidian-search; before running a command, read the task-specific workflow reference and confirm arguments with python scripts/okf_glue.py --help.

Language Policy

• When writing formal notes, use the same language as the current user-Codex conversation unless the user explicitly requests another supported language. When unclear, use the configured fallback language, which defaults to en-US in this public release.

Hard Rules

• Never write a formal wiki/ page without preview and explicit user confirmation.
• Formal writes must follow stage -> preview -> user confirmation -> commit -> build/audit.
• A user may grant batch confirmation for one clearly scoped ordinary cleanup task; batch confirmation does not cover framework changes, schema changes, formal-knowledge deletion, or large merges.
• Store formal knowledge only in the Vault; do not store business knowledge in the Skill folder.
• Create runtime business directories or missing Routers only when previewed and confirmed.
• Do not create asset subdirectories or overwrite existing assets without preview, explicit confirmation, and the matching command flag.
• Treat new top-level directories and new wiki/ first-level categories as framework changes that require explicit user confirmation and framework doc updates.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: KevinLuo1
• Source: KevinLuo1/kw-okf-memory-skill
• License: MIT

Install and usage instructions live in the source repository linked above.