Set the project standard (rigor profile)
set_standardSet and lock a project's rigor level (prototype, standard, polished) and attach a custom mandate. This defines how demanding the workflow, research, and testing will be for all work packets.
Instructions
Set — and LOCK — how much rigor a project's work is held to. Levels: "prototype" (move fast, minimal ceremony), "standard" (normal professional loop), "polished" (research-first: competitor teardowns, layout/IA of comparable apps, white papers, UX/UI heuristics, automation-everywhere, high test rigor + self-review). The resolved standard is injected into every work packet (packet.standard + extra definition-of-done items) and bends research-on-intake (polished forces it on with expanded questions; prototype skips it). mandate is the project's own free-text bar, carried verbatim into packets. INFERENCE RULE: when a project's standard is unset/unlocked, infer the level from the user's cues ONCE (pass source:"inferred") and lock it. A locked standard is settled — this tool refuses to change it unless force:true, which you pass ONLY when the user explicitly asks to change the standard. Account-wide default for unset projects: set_global_config defaultStandard.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| force | No | Override a LOCKED standard. Pass ONLY when the user explicitly asked to change it. | |
| level | Yes | ||
| source | No | Who decided: the user explicitly (default), or inferred once from conversation cues. | |
| mandate | No | Project-specific bar in the user's words, e.g. 'research competitors + whitepapers + UX guides; automate everywhere; highly polished engineering standard'. | |
| project | Yes |