Kitchen prepares terminal instructions before they are served.
Plausible commands are not good enough for a real terminal. Kitchen keeps target facts, user conventions, shell constraints, fixtures, tests, and preflight rules together so generated commands can be checked against the actual environment.
assumptions/— observations, preferences, and unknowns kept distinctsystems/— facts and assumptions scoped to machines and environmentsuser/— stable human conventions and preferencesshells/— language- and runtime-specific constraintspreflight/— checks required before a command is presentedprobes/— read-only ways to establish missing target factsfixtures/— disposable states used to exercise commands and scriptstests/— executable checks and regression casesincidents/— escaped mistakes turned into durable regressionssources/— provenance and links to upstream facts such as Cat Food
Start with AGENTS.md.
See the Grease-first canonical procedure.
The checked generator emits one complete standalone Grease program. Flexible Pipes runs it and verifies repository identity before the result is presented.
Read the IB handoff incident before serving a checkout-dependent phone test.
The versioned IB baseline task preserves existing checkouts, verifies source and blob identities, and keeps the passing old baseline separate from the unavailable E2 repair. Its regression covers failed context discovery, repeated execution, and login-shell preservation. Cat Food owns verified checkout lookup and the dated phone observation.
New source-test handoffs use the shared producer gate. It verifies fresh source materialization before emitting a digest-bound command. Consumer execution remains read-only and acceptance stays scope-specific.
The A1 material-bound preparation consumes exact Cat Food profile requests and AICI corrections before selecting the source-test, freshness, diagnostic, or export-copy action.