kyzodb

The review lens for judging any code, seal, or story against the storage architecture's caliber — not "did it pass the meter" but "is this the best it can be." Use when QA'ing a sealed task, assessing a story, or judging whether built code rises to decisions.md and the storage architecture. Not a checklist pass; a wisdom pass.

Ideal target-state file map for KyzoDB — where each seat lives and what it owns. Use before placing a construct, naming a file, choosing a zone, or judging whether code sits in the wrong place. Not current-tree inventory (read the tree) and not per-construct coding law (rust-* skills).

Create precise, high-context direction for LLMs as Q/A/E triplets — the hardest question, the ruled answer, the enforcement that makes it stick. Use when writing specs, rulings, migration destinies, agent priming, review standards, or any context where an LLM must make a choice exactly the way you would.

Gate whether a working set of atoms/clusters is closed under dependency edges (OPEN lists crossings). Use after organize-work when the border must be a real min-cut. Not organize-work. Not architecture-design.

Hoist all reads to session entry and sink all writes to session exit around a pure Decision middle. Use when a host/session path mixes IO with meaning. Not name-and-seat-construct. Not organize-work.

Name a construct's kind of truth and seat it in exactly one zone (KEEP or SPLIT). Use when placing or splitting a type/module/bag under zone law and future pressure. Not io-inversion. Not architecture-design. Not organize-work.

Partition stories/requirements into MECE clusters ordered by dependency. Use when re-slicing many items on wrong seams or turning planning smear into a build partition. Not closure-check (border gate). Not architecture-design. Not write-story.

Build the three plumbing constructs — composition root, config-once injection, sealed public door — the only places a kyzo binary or host assembles the engine and crosses its own public contract. Fires before writing main.rs or a CLI entrypoint, an env var read outside config, a host (kyzo-bin/kyzo-wasm) function that imports engine internals or caches results, or a runner/orchestrator/step-list function sequencing domain work by hand.

Fires when a boundary crossing is about to be hand-rolled instead of built as the matching construct in python-adapters-success — a before-validator that indexes/renames/routes/computes on raw foreign data, a try/except catching Exception or ValidationError or running multiple statements in its except body, or .model_dump/.model_dump_json called anywhere but a route reply or client binding.

Build the three boundary-crossing constructs — foreign model, contract model, ordered union — the only shapes for data crossing in or out of the program. Fires before touching a foreign payload, file format, message, or client reply; before declaring an API surface or response shape; or before writing a try/except, error handler, retry, fallback, or None-check around foreign input.

Fires when live state or a transport client is about to land somewhere wrong instead of the matching construct in python-state-success — frozen=True on the consistency model, a client field with no verb emitting through it, or arbitrary_types_allowed=True on any model other than the consistency model.

Build the two live-node constructs — consistency model and binding — the only places mutable state and transport clients are allowed to converge. Fires before holding a socket, database, bus, or client; before declaring a mutable field; before writing a manager, an engine, or a second unfrozen model in a context; or before writing a connect/setup/wiring class.

Fires when domain data is about to be shaped wrong instead of as the matching construct in python-values-success — a bare primitive field, an unproven scalar or collection, a T | None absence, free-floating vocabulary, a drifted or unmodeled enum, an after-validator policing a relation the fields should reparameterize, a bare .root held mid-graph, an open (unfrozen or extra-allowing) model, a union alias built without a discriminator, a union wrapped in a class, or a field the ontology never declared.

Build the five proven shapes for domain data — semantic scalar, value object, concept model, collection, union. Fires before writing a bare primitive field, a dataclass/NamedTuple/TypedDict, a list/set/dict field, a T | None field, a raw Literal or bare StrEnum field, or a match/if-elif/isinstance ladder selecting by kind.

Fires when a model method is about to be written wrong instead of as the matching construct in python-verbs-success — a stub body (raise NotImplementedError/pass/...), a second top-level construction statement in a verb, a verb's signature drifted from its modeled row, a modeled verb missing from the class, a verb/derivation/method with no row authorizing it, an undecorated method on a frozen model, or a verb body that skips a declared constructs/emits participant.

Build the two behavior constructs — verb (state transition) and derivation (pure computed fact) — the only legal methods on a model. Fires before writing any method on the consistency model that isn't a derivation, any method/property/computed field on a frozen model, a standalone function computing from a model's fields, a stored derivable field, a fetch-and-return method, or a multi-step construction chain.

ONLY board read/write — plan MCP tools, never raw gh. Tool descriptions are role×verb. Not write-story or run-story.

Parent after start_story — arm paths, spawn demolition then each T#, run board Check, spawn judge, allowlist-commit on PASS / path-restore on FAIL, Final QA verdict then check_final_qa. Not write-story or manage-board.

Minimal completion_request the development-task sends to the judge after allowlist edits. Not board writes, not git, not tree meters.

Author or revise board epics — name + outcome as the value state the story group creates. Not story contracts (write-story), not T# runs (run-story), not column moves (manage-board).

Author or revise board story contracts (name, sources, condemned, ceiling, choice, allowlisted T#s, Final QA DoD). Not epic authorship (write-epic), not T# execution (run-story), not raw board moves (manage-board).

The process for onboarding a new comparative subject (opponent database or engine) into one or more kyzo-bench benches. Use whenever a story adds a competitor that doesn't already have a rig, whether into one existing bench or across several. Enforces pin-first, fairness-before-wiring, and treats the output-format correctness bridge as the genuinely hard, per-workload step that no interface generalizes.

The discipline for executing one bench or demo story from the shared KyzoDB board. Use when picking up any story. Enforces working from the board, one coherent end-state target, verify-the-number, hostile methodology review, and the anti-avoidance rules.

The verify-with-run discipline for a benchmarks repo. Use whenever making any claim about what a rig does, what a run produced, what an opponent's configuration is, or what a result file contains. Every such claim must be backed by a real run whose output is quoted, or by reading the actual file.