--- okf_version: "0.1" bundle: aria-own-your-context title: "Own Your Context — OKF v0.1 Knowledge Bundle" updated: 2026-07-03 concepts: 13 --- # Own Your Context — OKF v0.1 Knowledge Bundle Local Context Architecture is a synthesis playbook for a single recurring pattern: managing an LLM's context — your process, standard operating procedures, skills, memory, and even the agents themselves — as plain local files you own. The unit is a folder of markdown files with YAML frontmatter, a reserved index catalog and an append-only change log, cross-linked by standard markdown links into a graph that is readable by a human without tooling, parseable by an agent without an SDK, versionable in git, and portable across models and harnesses. It traces the pattern through its canonical forms (Andrej Karpathy's compile-once LLM-wiki and Google's Open Knowledge Format), then across layers: context-engineering principles, skills-as-files, personal knowledge operating systems, and the company brain. A distilled best-practices checklist covers one-concept-per-file, a required type field, reserved index and log files, portable links, local memory, progressive disclosure, and vendor-neutrality. The motivating thesis is anti-lock-in: own your context locally rather than renting it back from a vendor. --- ## The playbook hub — start here - [local-context-architecture](local-context-architecture.md) — the synthesis hub: own your process, SOPs, skills, memory and the agents themselves as plain local files; the core pattern, techniques by layer, and a best-practices checklist. ## Techniques by layer ### Format — the file/folder contract - [open-knowledge-format-okf](open-knowledge-format-okf.md) — the specified, vendor-neutral exchange form: one required `type` field, reserved `index.md`/`log.md`, an untyped markdown-link graph, permissive conformance. - [llm-wiki-template](llm-wiki-template.md) — Karpathy's compile-once "LLM-wiki" authoring template: immutable `raw/` sources + LLM-maintained `wiki/` pages + a schema file. - [okf-knowledge-bundles-cole-medin](okf-knowledge-bundles-cole-medin.md) — a shareable OKF bundle in practice (the practitioner lens, and the origin of this bundle's `okf-cli.py`). ### Context — why files beat a stuffed prompt - [context-engineering](context-engineering.md) — the smallest set of high-signal tokens: just-in-time retrieval on lightweight identifiers, and progressive disclosure instead of front-loading everything. ### Skills — capability on demand, as files - [agent-skills-progressive-disclosure](agent-skills-progressive-disclosure.md) — a Skill is a folder with a `SKILL.md` manifest (when-to-use, tools, how-to-verify) plus heavy reference loaded only when triggered. - [open-skills-portable-agent-procedures](open-skills-portable-agent-procedures.md) — portable, vendor-neutral procedures with verification baked in: "do not call this done unless this evidence exists." ### Personal-OS — a whole second brain in folders - [pai-life-operating-system](pai-life-operating-system.md) — a personal Life-OS as memory + skills + TELOS in local files an agent operates. - [mypka-scaffold-reference](mypka-scaffold-reference.md) — the ICOR "one folder" myPKA scaffold: SSOT golden rule, flat concept folders, portable-core-vs-per-harness-adapter seam. - [agent-long-term-memory-solutions](agent-long-term-memory-solutions.md) — own your agent memory locally as Markdown exposed over MCP (Basic Memory), not a black-box hosted layer. ### Org & SOP — the company brain - [ai-native-organization-people-agents-context](ai-native-organization-people-agents-context.md) — the org "brain" is literally folders of markdown agents read and write back, over a capture → curate → store → execute → experience loop. - [company-os-ai-native-team](company-os-ai-native-team.md) — encode each function's SOPs as per-function skill files built from an ontology of the work. ### Anti-lock-in — why local - [claude-tag-context-lock-in](claude-tag-context-lock-in.md) — the motivating thesis: as context accretes inside a vendor you "rent your company back" from them; own the context layer yourself. ## Appendix - [references](references.md) — the broader R&D concepts (and raw source captures) that these pages cite but which live outside this bundle, in the full ARIA-RD encyclopedia. --- *Consumer: run `python3 okf-cli.py index | find | read `, or open [viz.html](viz.html) for the link graph. See [README](README.md) for usage and provenance and [log](log.md) for history.* --- --- type: readme title: "Own Your Context — OKF v0.1 Knowledge Bundle" description: A shareable OKF v0.1 bundle for the "own your context locally" playbook and its key techniques. okf_version: "0.1" bundle: aria-own-your-context source_bundle: null # curated cross-cluster bundle — no single matching logical id in _aria/bundles.yaml --- # Own Your Context — OKF v0.1 Knowledge Bundle ## What this is A self-contained, shareable **Knowledge Bundle conforming to the Open Knowledge Format (OKF) v0.1**. Its subject is a single playbook: **how to structure your process, standard operating procedures, skills, context, memory — and even the agents themselves — as LOCAL markdown files and folders you own, instead of renting them back from a vendor.** It bundles the synthesis **hub** (`local-context-architecture`) plus **12 technique concepts** that trace the pattern across layers — the file/folder **format** (OKF, Karpathy's LLM-wiki, a worked bundle), **context** principles, **skills**-as-files, the **personal-OS**-in-folders, the **org / SOP** brain, and the **anti-lock-in** motivation for keeping it all local. Everything is plain markdown with YAML frontmatter: if you can `cat` a file you can read it; if you can `git clone` a directory you can ship it. ## Layout ``` index.md catalog / entry point (progressive disclosure, okf_version 0.1) README.md this file log.md change log references.md concepts + raw captures cited but living outside this bundle okf-cli.py dependency-free consumer (Python stdlib only) viz.html self-contained force-directed link graph (no network/CDN) local-context-architecture.md .... the playbook hub (moc) <12 more>.md ..................... the technique concepts (flat, bundle root) ``` Each concept is one markdown file whose id is its filename minus `.md`. Every non-reserved `.md` carries a `type` field in its frontmatter — that is the OKF conformance contract. `index.md` and `log.md` are the reserved files. ## How to use **With the bundled consumer** (Python 3, no dependencies) — run from inside the bundle: ```bash python3 okf-cli.py index # print the catalog (index.md) python3 okf-cli.py find context # ranked keyword search across concepts python3 okf-cli.py read local-context-architecture # print a concept (id = filename minus .md) python3 okf-cli.py selftest # OKF-conformance check (every concept has a type) ``` **With an agent** — hand it the **OKF v0.1 SPEC** plus this bundle directory, and point it here. The spec explains the conventions (concepts, reserved files, `type` frontmatter, `index.md` as the map); this directory is a conformant instance the agent can navigate directly (read `index.md` or shell out to `okf-cli.py`). **Visually** — open [`viz.html`](viz.html) in any browser for a self-contained, offline force-directed graph of how the concepts link to each other. ## Conformance Conforms to OKF v0.1: every knowledge concept is one markdown file whose YAML frontmatter carries the single required field `type`; `index.md` and `log.md` are the reserved files; cross-links form an untyped directed graph; `okf_version: "0.1"` is declared in `index.md`. Verify with `python3 okf-cli.py selftest`. > Note: the reference `okf-cli.py` reserves only `index.md` and `log.md`, so it > also validates this `README.md` (`type: readme`) and `references.md` > (`type: reference`) as conformant concepts. That is why `selftest` reports > **15** conformant concepts, not 13 — expected, not an error. ## Provenance Extracted **2026-07-03** from the **ARIA-RD** R&D AI-knowledge encyclopedia, where these pages live under the `agents`, `ai-products`, and `theory` themes around the `local-context-architecture` hub. The source pages were **copied, not moved or modified** — the encyclopedia remains the source of truth. Cross-links *between* the 13 members were rewritten to bundle-relative `./concept.md` links; links to other encyclopedia pages (and to raw source captures) were redirected to [`references.md`](references.md) rather than left dangling; external `http(s)` URLs and each page's own `## Sources` / `# Citations` footers were preserved verbatim. See [`log.md`](log.md) for history.