CLI reference

yichus organize

Render the organization lenses (page, vocabulary, stack, conventions, map, flow, diff) over Bosatsu files

This help is generated from the same argument parser as the CLI. For a subcommand, append its name and --help to see its options.

Usage:
    yichus organize page
    yichus organize vocabulary
    yichus organize stack
    yichus organize conventions
    yichus organize aid
    yichus organize map
    yichus organize flow
    yichus organize composition
    yichus organize composition-diff
    yichus organize layers
    yichus organize structure
    yichus organize abstractions
    yichus organize effects
    yichus organize writes
    yichus organize view
    yichus organize composition-proposal
    yichus organize diff

Render the organization lenses (page, vocabulary, stack, conventions, map, flow, diff) over Bosatsu files

Options and flags:
    --help
        Display this help text.

Subcommands:
    page
        One page: how organized is this program, at a glance
    vocabulary
        The type vocabulary: concepts, roles, signature families, plumbing
    stack
        The stack: the blocks by layer in the order a reader learns them, with each block's reuse
    conventions
        How this project writes each recurring shape (form + kit), and where it disagrees with itself
    aid
        HEURISTIC AID over the conventions page, for a reader who cannot judge from it: flags labeled as heuristics, never evidence
    map
        The abstraction map: layers, mass, duplication, clone pairs
    flow
        The IO flow: causal effect order per binding, resources, declared systems
    composition
        Shared definitions, declaration roles, matched flow bodies and effect-use contexts
    composition-diff
        Source-backed bounded structural changes between two complete program versions
    layers
        Packages in rows by level, the packages each one uses, and the direct effect sites and tables in each
    structure
        Records of functions and the values that fill them, where each called function comes from, chains, phases by type, what each caller does with a shared result, values put together as a tree, choices keyed by a plain String or Int, and crossings between declared groups
    abstractions
        Higher-order generators, curried specializations, call-site slot fillings, and route responsibility splits
    effects
        Every route as a tree: the calls, wrapper arguments and guard branches down to each effect
    writes
        The effects tree with only row writes (write, create, delete) drawn
    view
        A lens page (stack, map, or conventions) with an authored VIEW under it: the author's order, foreground, declared groups, and captions, checked against the page and refused when they break a rule
    composition-proposal
        An authored, snapshot-checked structural plan and optional compiled observation
    diff
        The factual delta between two snapshots of one program (the policing instrument)

Make a data app · Build an API · MCP / WebMCP docs