A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live
majordomus.depth-is-not-verbosity@1
Execution depth is not output verbosity
What it is
- URI
majordomus://rule/majordomus.depth-is-not-verbosity@1- Kind
rule- Identity
majordomus.depth-is-not-verbosity@1- Path
.ai/repo/rules/vendor/majordomus/rules/principle-06-depth-is-not-verbosity.v1.md- Provenance
- declared
- Media type
text/markdown- As a capability
- rule.majordomus.depth-is-not-verbosity@1
Front matter
{
"id": "majordomus.depth-is-not-verbosity",
"version": 1,
"kind": "rule",
"title": "Execution depth is not output verbosity",
"description": "Think as hard as the task needs; report as briefly as the profile says.",
"statement": "Keep the depth of work and the length of its report as two separate settings, each taken from the profile.",
"status": "active",
"class": "advisory",
"depends_on": [],
"tags": [
"principle"
]
}Content
---
id: majordomus.depth-is-not-verbosity
version: 1
kind: rule
title: Execution depth is not output verbosity
description: Think as hard as the task needs; report as briefly as the profile says.
statement: Keep the depth of work and the length of its report as two separate settings, each taken from the profile.
status: active
class: advisory
depends_on: []
tags: [principle]
---
# Rationale
Long output is not evidence of careful work, and careful work does not need long output. Confusing the two produces reports nobody reads and depth nobody controls.
# Required behaviour
Keep the depth of work and the length of its report as two separate settings, each taken from the profile.
# Failure behaviour
Nothing decides this rule directly, so a violation is reported by nobody; it is the rules that depend on it that decide what a machine can decide and stop or warn accordingly.
# Verification
The enforced rules whose `depends_on` names this one carry the validators, the tests and the CI wiring. `majordomus doctrine list` shows them.