Module mode 

Run modes and admission. A run sits in exactly one mode; the catalog lists only that one (progressive disclosure — the other mode’s text stays out of the window).

One exception, and it is one line long: dev_entry tells a run that this city’s own code is changeable, and names the evidence a change can be asked to carry. Without it an agent working in this city never learns that the city’s own code and SPECs are changeable at all, or under what discipline — and a capability nobody is told about is one nobody uses.

The half that decides is admits: it says whether what a run produced may land, given the run policy it was dispatched under (crates/runtime/spec/Mode.lean §8-54). The evidence arrives as plain answers rather than as an instrument’s type, because the instruments live in citysim, outside this crate, and the question here is not how evidence was gathered but whether enough of it exists.

Structs

Produced

Enums

Admission

Whether this may land, and if not, what to do about it.

Constants

DEV_ENTRY

The name of the catalog row that opens the developer discipline.

Functions

admits

Whether what a run produced may be merged, under the policy it was dispatched with (crates/runtime/spec/Mode.lean §8-54).

catalog_entry

The catalog row for this mode: disclosure one-liner plus the expansion text. The chat row is the whole of what chat mode does: one line telling the resident that the person is talking with it.

core_tools

What a run has to show for itself.

dev_entry

The row that tells a run this city is changeable, and nothing more.