routine profile
small, well-understood changes; rename, bump, wording, one-line fixes
majordomus start "…" --profile routine
- capability class
- fast
- reasoning effort
- low
- output verbosity
- terse
- presentation
- machine
- checkpoint interval
- 30m
- output contract
- outcome, changes, verification
context loaded
- architecture_notesfalse
- current_statetrue
- decisionsfalse
- failing_outputfalse
- recent_history_depth0
- relevant_filesfalse
- tasktrue
verification
- decision_record_requiredfalse
- regression_test_requiredfalse
- verify_command_requiredif_files_changed
What is claimed about profiles
- guaranteed Every profile is parsed, its unknown keys rejected, and the default profile proven to exist
- advisory Capability class, reasoning effort, output verbosity, context and verification are five independent axes
- advisory A profile names a capability class rather than a vendor model
- advisory A profile declares which context a worker should load and no more
- advisory Escalating reasoning effort after repeated blocked attempts is recorded rather than assumed
- advisory A profile sets how often a worker should checkpoint, and a stale task is reported
- guaranteed The context a worker is given is assembled from durable state in authority order, and what a profile excludes is excluded
- guaranteed The assembled context obeys a line budget, and every section it drops is named with its reason
Source: share/skeleton/profiles/routine.yaml. Capability classes are not vendor model names; the generated instructions tell the worker to pick the closest its environment offers.