Documentation

DOC / 01 / START

Getting started

Install the CLI, create a project, start the development server, and produce the first verified build.

In this guideGetting started
Getting startedProject structureCLI referenceDeveloper loopRouting and pagesRust viewsEvents and foldsSchemas and snapshotsHyphae verified syncTyped contentBrowser runtimeDOM ownershipAdaptive assetsArtifact trustErrors and diagnosticsBuild and deployCrates and APILicensing and policy

Before you begin

PliegoRS projects are Rust workspaces. Install a stable Rust toolchain, the wasm32-unknown-unknown target when the project has a browser client, and wasm-bindgen-cli at the exact version reported by pliego check.

Rust
1.85 or the release toolchain declared by the project
Targets
Linux x64/ARM64 for production; macOS and Windows for development
Source
crates.io packages, GitHub Releases, and the canonical celiumsai/pliegors repository

Install the CLI

shell
cargo install pliego-cli --version 0.0.1 --locked
pliego version

Release installers are downloaded to disk, verified, and then executed. PliegoRS never documents piping an unverified network response directly into a shell.

Create and run a project

shell
pliego new my-app
cd my-app
pliego check
pliego dev
  1. 01

    Scaffold

    pliego new writes the default onboarding project transactionally; it never merges into a non-empty directory.

  2. 02

    Check

    pliego check validates the manifest, Cargo packages, Rust target, and wasm-bindgen contract without producing output.

  3. 03

    Develop

    pliego dev builds, serves on 127.0.0.1:4400, watches source files, and presents build failures in the browser.

  4. 04

    Verify

    pliego build && pliego inspect produces and verifies the production artifact ledger.

Where to go next