koru

Tend the membrane memory corpus — an OKF concept store whose fragment evolution lives in the git log as lineage trailers. Fire when creating, evolving, merging, splitting, or CORRECTING durable memory/knowledge that lives as OKF files under git; when recording how a belief changed or was repudiated; or when tracing a concept's history through time. YOU are the evolver — there is no evolution engine and no LLM sidecar. NOT for transient notes, scratch, or code comments.

Compile-time metaprogramming in Koru: event globbing and compile-time event matching — the "you are the compiler" surface where userland code sits inside the pipeline. Use when writing compile-time event selection or pattern-matching over events. SEED TOPIC — currently scoped to event globbing; widen `clusters` in koru-by-example.json as the metaprogramming surface grows.

Control flow in Koru: `~if` and `~for` as templates over continuation-return, not host keywords. Use when emitting conditionals or iteration in Koru, or when working on the template/lowering layer (`koru_std/control.kz`). Covers how `for`/`if` select continuations and lower per target.

How to work with the Koru language and its compiler `koruc`. Use when working in a Koru repo (`.kz`/`.k` files), running or reading regression tests, or when you need to orient on the toolchain — what the language is called, how to compile, where the docs and tests live. Start here before reading code.

Koru regression test harness workflow. Use when checking test status, investigating failures, or coordinating test runs with the user.

How to work with the Koru language and its compiler `koruc`. Use when working in a Koru repo (`.kz`/`.k` files), running or reading regression tests, or when you need to orient on the toolchain — what the language is called, how to compile, where the docs and tests live. Start here before reading code.

Drive koru's diagnostic-code registry to green. Use when `zig run scripts/registry_check.zig` FIRES on DEAD/ORPHAN_EMIT/ROTTEN_PIN codes and you need to disposition each one (wire an emit / reserve / consolidate). The watcher detects drift in src/errors.zig's ErrorCode enum; this is the playbook for clearing it. Derived from three cold-room probes — trust the procedure, verify every claim.

Draft a short korulang.org blog post announcing a newly-landed Koru feature, grounded in its regression tests and using the site's bespoke RegressionTestLink component. Use when Lars says "write a blog post", "pen a blog post", "blog this feature", or asks to describe recent work as a post for korulang_org. Produces a DRAFT for Lars to read — never publishes.

DRAFT. The method for making Koru fast — NAIVE CODE => OPTIMAL BINARIES. Use when a benchmark/kernel is slow and you need to close a performance gap: diagnose from the Koru code, escalate to emitted-Zig backport, or introduce a high-performance primitive — with the optimization always landing in the toolchain, never in the .k. Also the discipline referenced by the compute-kernel gap-mining challenge for commissioned perf runs.

Run a progressive capability census — prove Koru can do real tasks of increasing complexity, pristinely, or pin the precise frontier that blocks it. Use when climbing a proof corpus (e.g. tests/regression/810_AOC_2015), authoring or judging a proof submission (tests/regression/820_PROOFS), or deciding whether a task solution is "done" — the pristine bar lives here.

The core Koru language: events with named outcome branches, flows that dispatch (`|`) and chain (`|>`), subflows vs host procs, the `~` parser-mode rule, plus loops (label + jump) and literals/punning. Use when writing or reading any `.kz`/`.k` file and you need the foundational shapes. Start here before the narrower topic skills.

The world-modeling practice of Arbiter-Driven Development — instrumenting anything (a repo, a product, an idea, a dataset) with executable world models that fire signals. Fire whenever world-modeling comes up in ANY form — "should this be instrumented?", starting a project under the world-model regime, floating an ontology from data or a codebase, building or judging a signal instrument, the tending loop, probes vs instruments, faucets. NOT the wm tool's manual (that lives in `wm help` and is never duplicated here). This is the method-side guide and the honed-prose home for the practice.

Pull and manage feedback from korulang.org. Use to see what users are reporting about tests/documentation, prioritize work, and mark items resolved.