Readable by engineers
Architecture rationale, design intent, explanations, requirements context, and documentation remain ordinary readable text.
Text2System is an open, human-readable language for defining software and embedded systems. Architecture, contracts, requirements, packaging, deployment, documentation, and projections live in one canonical plain-text source.
Text2System brings software engineering the equivalent of electrical schematics: one canonical, human-readable system definition from which documentation, diagrams, validation, and implementation artifacts are projected.
T2S defines what a system is.
Programming languages define how it behaves.
Example System system: id: ExampleSystem module: id: Core interface: id: Service function: id: process
T2S combines human-oriented narrative with machine-readable semantics, while keeping target languages and renderers outside the canonical system definition.
Architecture rationale, design intent, explanations, requirements context, and documentation remain ordinary readable text.
Systems, modules, interfaces, functions, types, relationships, tests, packages, and deployments are declared explicitly.
Documentation, diagrams, Rust, Zig, Python, C ABI, validation reports, and other outputs are projections of one model.
The canonical model sits between source syntax and target-specific output.
The current Rust bootstrap includes the T2D narrative parser, T2S Semantic Builder, documentation projector, deterministic HTML output, and regression testing against the official specification.
# create a project text2system-cli init my_project # build documentation text2system-cli project documentation my_project # validate the current implementation cargo test --workspace cargo clippy --workspace --all-targets -- -D warnings
The project is deliberately built in small, testable compiler stages.
The T2S language specification is dedicated to the public domain under CC0-1.0.
The reference tools are released under the 0BSD license.
Text2System treats text as the canonical system definition. Documentation and implementation artifacts stay synchronized because they are projected from the same source.