MN Manual of StyleLanguage rules for the Multiple Natures framework

Usage, capitalization, and vocabulary — each backed by a theory claim.

Quick Reference

Browse rules

⚠️

RULE-G01 — Predicate Nominative

Natures are not predicates of identity. Say "she has a high Creative Nature", never "she is a Creative".

⚠️

RULE-G02 — Probabilistic Tendency

Trait expression is probabilistic. Say "tends to", never "always" or "will".

📄

CAP-001 — Capitalization

Named Natures and Intelligences are both-words capitalized. Collective plural is lowercase.

📄

DEC-001 — Trait Valuation

Traits have assets and liabilities — never strengths and weaknesses.

What this is

The MN Manual of Style is the canonical language guide for the Multiple Natures framework. Every rule here traces to a specific theory claim (CLM-LXXX) — not editorial preference.

Use this guide when writing about Natures, Intelligences, trait scores, or any other framework concept.

Authority chain

Each rule lists its authority_claims. Those claims (CLM-LXXX) carry the full theoretical grounding. The rule is the language surface; the claim is the theoretical substrate.

Theory layer (claims.db)
  └── CLM-L021  Natures are situational, not identity types
  └── CLM-L034  Trait expression is probabilistic
        │
        ▼
Language layer (mos_entries in claims.db)
  └── RULE-G01  No predicate-nominative typology
  └── RULE-G02  No deterministic predication
  └── CAP-001   Capitalization discipline
  └── DEC-001   Assets/liabilities not strengths/weaknesses

How to use this

Before drafting: read Quick Reference (90 seconds).

When flagging a phrase: look it up by rule ID. Each entry lists forbidden and required vocabulary with OK/Not-OK examples and rewrites.

When adding rules: write the MoS entry in style-manual/, run claims-build.py to ingest into the DB, then run sync.sh to update this site.