FR-001noneno test runA harness's specifications MUST be natural language in Markdown, and its ontology, code, tools and tests MUST be TypeScript 7 or later, run on Bun by default and on Node 26 as the backup (0005-typescript-practice).
0017-two-languages · owner if · domain commons · part of 0003-mizan
FR-001noneno test runA harness's specifications MUST be natural language in Markdown, and its ontology, code, tools and tests MUST be TypeScript 7 or later, run on Bun by default and on Node 26 as the backup (0005-typescript-practice).
FR-002noneno test runA fact, a setting or a schema MUST NOT be kept as source in another language or format (YAML, JSON, XML, Turtle, SQL), except as a named exception (FR-004); what other forms a tool writes from the TypeScript is generated, marked .auto., and never edited by hand.
FR-003noneno test runCode written to integrate, extend or plug into another system MUST be TypeScript 7 where it can be. Where TypeScript does not support what the job needs natively and a hand-written minimal parser or client would not be good enough, the best stack (format, language or tool) for the integration job MUST be chosen and used: an integration that works is not given up for a language.
Cited by: integrations/pure/read-rdf-xml, IFC Mizan Integrations
FR-004noneno test runEach such choice MUST be a typed Exception of the ontology: the tool, its language or format, why TypeScript or a hand-written parser is not enough, its pinned version (0002-packaging), its isolation (a typed TypeScript wrapper with files in and files out, so that nothing else depends on it), the platforms it supports, and the real-tool tests that run it.
Cited by: mizan/mizan, IFC Mizan Integrations
FR-005noneno test runMizan's documentation MUST say that drift between specification and ontology is a real danger, and that sticking to natural language for specifications and TypeScript 7 for ontology and code reduces it without removing it.
FR-006noneno test runA harness MUST hold these controls against drift: each source file names the requirements it implements (// Spec:), each test names what it proves (proves([...])), each ontology term names the specification that defines it, a specification names only terms the ontology defines, the words code branches on are code lists imported as unions and never written again, generated files are checked for staleness and the direction of imports is checked (0015-trace).
FR-007noneno test runException.0003-mizan.Exception, per FR-003 and FR-004.Exception.OQ-1open questionWhether the exceptions' isolation should be a subprocess contract or a library boundary, per tool, once the first one exists.
SC-001success criterionA harness's only non-TypeScript sources are named exceptions or third-party files.
SC-002success criterionEvery exception has a pinned version and a test that runs its real tool.
Mizan, integrations/pure/read-rdf-xml, rules, Ontology, mizan/mizan, IFC Mizan Integrations