dancxjo/conduit

**One continuing computer, made from the computers you have.**
Conduit is an experimental programming system for portable, typed flows of work.
A program describes what should happen. Hosts offer the machinery they can
actually supply. Planning joins the two in an exact, finite realization.
A **body** is the logical computer that can continue while its hosts, devices,
and connections change. It may run on one machine or span several. This is the
architectural direction; each target and lifecycle promise has its own
implementation and proof boundary.
Try it
- **Open the body Workspace** to meet the browser product and its resident plots
- **See ConduitOS running** in the ten-step x86_64 QEMU journey
- **Check the published build** for development, accepted-release, publication, and proof identities
To run the first hosted example, install Git and Rust through rustup,
then use the checkout's pinned toolchain:
This builds the repository tooling and runs Hello
through the production checker, planner, and kernel. A native linker is needed;
browser and hardware tools are not prerequisites for this example. The first
build takes time and disk space. See Try Conduit for the
browser, native workbench, and ConduitOS routes.
Read a plot
The literal supplies text, text/upper makes it uppercase, and
face/text presents it. The full stop after } makes structural drain
semantic completion. The source chooses no OS, window, socket, or device.
Three small groups explain the model:
| Question | Terms |
|---|---|
| What should happen? | A **plot** composes semantic **kinds**. Each **gear** is one occurrence of a kind; its **fore** is the callable signature. Typed **ports** connect through **cords** carrying **info** |
| How can it happen here? | A **host** offers **backs** that realize kinds. A **plan** selects exact backs, resources, authority, lines, and finite bounds |
| What is happening? | A **play** executes one plan through bounded **steps**. **Signs** record evidence; a replacement plan handles changed reality explicitly |
A **fore** is the function-like signature an author calls. A **face** is the
body's human-facing meaning and agency. A **mask** realizes that face as a
**show**. Callability and human presentation are distinct concepts.
Canonical Conduitese pairs two small vocabularies. A **type** says what a value
means; a **form** says the concrete portable shape in which that value is
carried. A **plot** says what should happen; a **plan** selects how it will
happen here; a **play** is that plan executing. In short: type -> form and
plot -> plan -> play. See the
current language reference for checked
examples and their limits.
Choose a reading path
| You want to… | Start here |
|---|---|
| Understand the idea | Why Conduit, then the architecture tour |
| Learn the language | Conduitese, examples, then try plots |
| Find an exact contract | Language reference, glossary, or architecture reference |
| Run a target or inspect a body | Try Conduit, targets, Patchbay workbench |