Add the independent program IR from blueprint sections 7.1 and 11: - ModuleId, FunctionId and UnitId canonical identities; UnitInfo/UnitKind for heading scopes (root, namespace, function, section). - Function with explicit or inferred signature metadata, params and defaults; assignments, expression statements, link-form calls, branches, loops and returns, all carrying source spans. - CallTarget distinguishes same-module, import-alias-qualified and link-resolved calls. - ImportDecl from explicit front-matter imports; Resource records inert Formula/Code artifacts with SHA-256 content hashes and owning units. - Module anchors, resolved import edges and Program lookup helpers used by the runtime and CLI. - Builtin registry (names, aliases, arity, named-only/effect flags) shared by static validation and runtime dispatch; adding a builtin is a spec change. Prose is absent from the IR by construction, so narrative edits cannot change the executable projection.
Marqdo CLI — next-generation design starter
Design-only starter package. This archive does not contain an executable CLI or a completed Rust implementation.
Marqdo aims to be a Markdown-native, independently interpreted programming language: Markdown AST structures carry program control semantics; readable prose can coexist with execution, while runtime effects are explicit and controlled. The new toolchain is independent of the original cflmy/marqdo repository.
Read first
docs/DEVELOPMENT_BLUEPRINT.md— the comprehensive Chinese design and development specification: motivation, formal mapping, functions/parameters/calls/returns, execution, references, Math/Foreign kernels, environment and package manager, sandbox, plugin ABI/SDK, milestones, tests and related projects.AGENTS.md— succinct onboarding instructions for coding agents and new contributors.
Planned CLI surface
marqdo init
marqdo run index.mq.md
marqdo call index.mq.md main
marqdo check index.mq.md
marqdo inspect index.mq.md --ast
marqdo add <package>
marqdo lock && marqdo sync
marqdo plugin inspect <artifact>
These commands are planned APIs, not yet available in this starter package. Begin by implementing P0 tests and a reference Markdown AST explorer; do not start with a monolithic CLI or port old parser heuristics.
Design status
The language direction and architecture principles have been selected. Detailed proposals still require ADRs and conformance testing before a stable version. See blueprint section 17 for unresolved items and section 18 for the Alpha definition of done.