Component · spec & evidence

Executable Doctrine Grammar

Checks that example standards files declare their purpose, rule, records, and what they do not claim.

Contract

Does It checks that a folder of example "doctrine" files (toy public standards and write-ups that describe how the system is supposed to behave) actually have the required parts: a stated purpose, the rule that governs them, the result records they are expected to produce, and an honest statement of what they do NOT claim. It reports, file by file, which entries are well-formed and which ones fail a required check, including ones that overclaim (saying a passing grammar check proves the doctrine is complete) or that try to treat plain advice as enforceable authority.

Scope limit It validates an exported public executable-grammar metabolism bundle with exact copied-body digests and redacted result records, plus fixture regressions for standards/paper-module shape. It does not publish source doctrine bodies in result records, prove doctrine completeness, export a private standards engine, authorize later components, or claim external model access, non-public data equivalence, launch-scope decision, or whole-system correctness.

Run

PYTHONPATH=src python3 -m microcosm_core.organs.executable_doctrine_grammar validate-executable-grammar-metabolism-bundle --input examples/executable_doctrine_grammar/exported_executable_grammar_metabolism_bundle --out receipts/first_wave/executable_doctrine_grammar --card

Evidence

ClassContract validatorevidence 5/5Import validation

Links to Doctrine Fact Claim Audit

architecturenavigationdoctrine

Source

Source Design note · Source

Map Show on the map

Index Open compact index card

Paper module