Quality Standards

Internal governance document — authored and maintained by the CEO. Thresholds and checklists established during agent fleet setup and refined through operational experience.

Output quality checklists for non-code work. Architecture tests define good code. This document defines good output for everything else.

Agents self-score their work (1-10). This document adds two things: a minimum-present threshold (don't show the CEO work that scores below 6) and pass/fail checklists per output type.

External-Facing Content

Tweets, landing page copy, directory listings, announcements, social posts.

• [ ] Every factual claim is verifiable from company/ or shared/ docs
• [ ] No off-limits features mentioned (see CLAUDE.md "Off-Limits for External Messaging")
• [ ] Tone matches the channel guide in brand-guide.md
• [ ] No buzzwords from the brand guide's Don't list
• [ ] Specific over generic — numbers and concrete outcomes, not adjectives
• [ ] Within character/length limits for the channel
• [ ] Self-score is 6 or above

If any item fails, fix it before presenting. If you can't fix it (e.g., missing source data), flag the specific gap to the CEO.

Internal Reports

Audits, research reports, finance reports, competitive analyses.

• [ ] Leads with the finding or recommendation — evidence follows, not the other way around
• [ ] Every claim cites a specific file path, URL, or data source
• [ ] Includes a "what this means for Kendo" section — not just raw data
• [ ] Flags uncertainty explicitly rather than hedging with weak language
• [ ] Self-score is 6 or above

If your self-score is below 6, do not present the report. Instead, state what's blocking quality (missing data, unclear scope, conflicting sources) and ask the CEO how to proceed.

Knowledge Base Changes

Wiki updates, research filings, compiled sources.

• [ ] Source attribution present per the provenance rule (two hops max from claim to origin)
• [ ] INDEX.md updated with new or modified entries
• [ ] Cross-references added to related wiki files where relevant
• [ ] No structural changes to existing documents without CEO approval

Structural changes = renaming sections, reorganizing a file's layout, splitting or merging documents. Data updates within existing structure are fine.

Minimum-Present Threshold

All agents that self-score should apply this rule:

Score	Action
7-10	Present to CEO
6	Present to CEO with a note on what would make it better
4-5	Do not present. State what's blocking quality and ask for guidance
1-3	Do not present. Something is fundamentally wrong — escalate the blocker

Related

• decision-principles.md — Trade-off hierarchy when goals conflict
• brand-guide.md — Voice, tone, and copy standards
• mission.md — Strategic priorities