Oko/Docs

Invocation#

Command

oko innovation derive [--json]

Inputs and options#

The register is ~/Library/Application Support/Oko/innovations.json; OKO_INNOVATION_REGISTER moves it, and beside a moved OKO_DEFECT_REGISTER it is <register>.innovations.json.
The frustration register; the declared factory signals; the recorded innovations and their verdicts, so a pattern or a rejected proposal is not repeated.

Prints {offered, proposed: [{id, title}], refused: [{title, quotes, cause}], open: [{quote, outcome}]}. Only a moment a recorded proposal cites is kept as considered. Every other moment offered, cited only by a refused proposal or by none, is listed under open with its outcome and kept in the register with a digest of what it was offered under (the measures and the recorded proposals); it is offered again only when a new open moment arrives or those inputs change. A pass where open moments exist and all wait asks Brama nothing and prints {proposed: [], waiting: [{quote, outcome, at}], why: “no open frustration moment is new, and every one no recorded proposal cites was offered under the same measures and recorded proposals; …”}; a pass with no open moment left uncited prints {proposed: [], why: “no open frustration moment is left that no recorded proposal cites”}. Oko Desktop → Innovation → Derive shows the same lines, the why included. Every model policy pass runs it after measuring, so an unchanged moment costs one completion, not one a minute.
The real journey `cargo test --manifest-path rust/Cargo.toml --test innovation-derive -- --ignored` asks the Brama this machine reaches over registers of its own: two open moments are offered and left open, a second pass at once asks nothing and answers both waiting with the kept outcome, and a third moment re-offers all three; a refusal of Brama fails it as blocked.

Brama that cannot be asked or answers outside the schema refuses with its answer; a proposal `propose` refuses is listed under refused with its cause.