/**
 * THE LAW (§12), restated for the checking floor.
 *
 * The runtime already refuses to project an irreversible tool onto an unattended
 * run. This is the same law applied one step earlier — to what an app is
 * PLANNING to do at build time — so "email everyone on Friday" is caught while it
 * is still a plan and answered in plain language, instead of the person finding
 * out when a run fails.
 *
 * A judgment rule rather than a fact check: only a reader can tell that a
 * scheduled step moves money or messages a person, so it joins the reviewer's
 * rubric as its own line.
 */
export declare const UNATTENDED_IRREVERSIBILITY_RULE = "Work that runs while nobody is watching may read and write, but it must never move money, message a person, or delete anything \u2014 not with a limit, not with an approval. An app that schedules one of those is wrong even if it looks careful: the honest shape is that the scheduled part PREPARES and a person sends, with the real amounts and recipients in front of them.";
/** The floor's automations check, mounted with the automations subsystem.
 *
 *  Typed structurally rather than against the checking floor's own `Check`: this
 *  package sits on core alone (dependency-guard), and the rule is a SENTENCE —
 *  the floor is merely where it happens to be read. The literal `kind` is what
 *  keeps it assignable at the umbrella's mount site. */
export declare const unattendedIrreversibilityCheck: {
    name: string;
    kind: "judgment";
    rule: string;
};
//# sourceMappingURL=law.d.ts.map