Architecture-as-code for the agentic era. Write your system as plain pseudocode; the toolchain validates the model and generates the C4 and sequence diagrams your team and your agents build against. Model-driven engineering, reignited.
Open the Web IDE → · See a generated doc site → · Language spec · Patterns
| Path | What it is |
|---|---|
LANG.md |
The normative language spec (§1–§12). The source of truth. |
PATTERNS.md |
Idioms and recipes for modelling in PseudoScript. |
CONFORMANCE/ |
The executable contract — lexical, syntax, static, generation cases. |
decisions/ |
Architecture Decision Records, one per resolved fork. |
crates/ |
The Rust toolchain: parser, checker, formatter, diagram emitter, LSP, and the pds binary. |
web-ide/ |
The browser IDE — the whole toolchain compiled to WebAssembly. |
web-landing/ |
The marketing site. |
model/ |
PseudoScript modelling its own design — the compiler crates, the web IDE, and the landing site. Its generated doc site is live at pseudoscript-model.pages.dev. |
pds init # scaffold a workspace
pds eval # read a model from stdin, report diagnostics (great for agents)
pds check <file> # check a file or workspace
pds doc --serve # render the live C4 + sequence-diagram doc site
pds lang | pds skill # print the grammar / authoring method for an LLMBuilding a model with an agent? pds skill and pds lang teach it the method
and grammar; pds eval lets it check its work as it goes.