openmixer — generated API reference
    Preparing search index...

    The whole desk's declaration, as OPTIONS <base>/ answers it.

    resources is the address space's alphabet: every template the console will answer, so a client resolves an incoming address against them rather than against a list it was built with.

    interface ConsoleContract {
        allow: readonly ResourceMethod[];
        confirms: ConfirmSheet;
        defaults: Readonly<Record<string, object>>;
        demand: Readonly<Record<string, boolean>>;
        resources: readonly string[];
        travels: Readonly<Record<string, ResourceTravels>>;
    }
    Index
    allow: readonly ResourceMethod[]
    confirms: ConfirmSheet

    Operation rows whose fire is gated behind the operator's confirm setting, keyed by the operation row's own path (ConfirmGate, 2026-08-22-osc-surface.md). Absent from a desk that publishes no confirm map, which reads as "nothing here needs asking" — the honest answer for a console that gates nothing. A remote surface with no dialog of its own reads this to find the SAME preview and the SAME sign-off the web UI's useApplyWarning reads, rather than growing a second policy.

    defaults: Readonly<Record<string, object>>
    demand: Readonly<Record<string, boolean>>

    The rows the desk declares PUMP-FED — telemetry a subscriber is sent only for the entries in its demand (demand gate §3d: which rows are pump-fed is CONTRACT, never a hand list in a client). A remote surface needs it for two different reasons and both are the same reason: it must DECLARE such a row to receive it at all, and it must not treat one as board state if it ever does. Absent from a desk that publishes no demand map, which reads as "no row is pump-fed" — the honest answer for a console that gates nothing.

    resources: readonly string[]
    travels: Readonly<Record<string, ResourceTravels>>