pliego-cli 0.0.2

Unified PliegoRS build, dev, and inspect workflow.
Documentation

PliegoRS folds append-only event logs into interfaces. State is projected from typed events, the projection advances as events arrive, and replay must produce the same result. Useful HTML is emitted first; Rust/WASM resumes only the behavior the document needs. Mature browser libraries such as GSAP, Lenis, and Three.js remain JavaScript behind explicit lifecycle adapters.

The current public preview release is 0.0.1. PliegoRS is pre-1.0 software: the documented contracts are deliberate, while APIs may still evolve between minor releases.

What exists

  • deterministic static generation with typed heads, routes, assets, and ledgers;
  • escaped DOM/view construction and typed view! components;
  • signals, memos, effects, ownership scopes, typed/versioned events with exact schema-value round trips, transactional projections, and contract-bound snapshots;
  • typed Markdown, JSON, and TOML content with bounded discovery;
  • Rust/WASM clients and a versioned mount/update/unmount adapter contract;
  • lazy loading, capability policy, Save-Data, reduced motion, cancellation, and automatic cleanup for external browser libraries;
  • reproducible image, video, font, and 3D asset plans with device budgets;
  • a protocol v2 Hyphae client boundary with signed append/page attestations, stream-bound typestate replay, and no claim of a production gateway;
  • pliego new, check, build, native-event dev, preview, inspect, why artifact, why-rebuilt, causal graphs, typed HMR, and maintained replayable default, minimal, editorial, and cinematic starters;
  • default-disabled, identifier-free voluntary funnel telemetry with local preview, explicit export, a 64-event bound, and complete deletion;
  • a five-target, two-replica release pipeline with a signed exact-set manifest and a distribution-only golden path;
  • an independently committed external flagship that exercises durable events, replay, forks, effects, receipts, provenance, audit, and selective sync;
  • an official bilingual site authored by PliegoRS itself.

Direction

PliegoRS is not a Vite, Astro, Next.js, or Leptos clone. Its differentiator is the trust model across events, folds, effects, artifacts, and lifecycles. Hyphae is the first-class durable data plane when a project needs it, but static projects do not require Hyphae.

The R0-R7 hardening sequence is complete: reactive safety, artifact trust, verified sync, snapshots and schemas, DOM lifecycle, developer golden path, reproducible distribution, and an external flagship. See the hardening roadmap and the bounded R7 evidence. Production Hyphae operation remains a separate system boundary.

Packages

Package Responsibility
pliego-log Typed/versioned local history, canonical payloads, exact cursors, and sealed schema catalogs
pliego-fold Transactional projection, replay, canonical state codecs, and contract-bound snapshots
pliego-reactive Signals, memos, effects, ownership, and disposal
pliego-dom Escaped view and DOM construction
pliego-macros Typed view! and component props
pliego-content Typed content, safe CommonMark, limits, and diagnostics
pliego-artifact Portable namespaces, build receipts, and exact-set verification
pliego-ssg Documents, routes, assets, SEO, and staged builds
pliego-resume Resumable standard browser actions
pliego-adapters External ESM lifecycle and WASM bootstrap
pliego-assets Adaptive media plans, budgets, and manifests
pliego-inspect Artifact integrity and budget inspection
pliego-hyphae Protocol v2 attestations, authority policy, and type-gated verified replay
pliego-starters Maintained embedded starter projects
pliego-cli Project creation, build, dev server, preview, and inspection

Install

Install the CLI from crates.io:

cargo install pliego-cli --version 0.0.1 --locked
pliego new my-site
cd my-site
pliego check
pliego dev

Diagnose an environment, create a redacted local reproduction archive, and check exact package alignment without modifying the project:

pliego doctor
pliego report --bundle
pliego upgrade --check
pliego telemetry status

The delegated pliego css check surface is experimental interoperability with a separately installed executable. PliegoCSS research is paused, is not published, and is not part of the supported PliegoRS quickstart. PliegoRS accepts standard CSS and remains independent of any CSS toolchain.

Linux production binaries and macOS/Windows development binaries are also published in the GitHub Release. Installers require Node.js and verify their selected payload against the signed release manifest before extraction. Download installers to disk and verify the complete release bundle before running them; never pipe a network response directly into a shell. See the distribution guide.

Local development

cargo build -p pliego-cli
target\debug\pliego.exe new ..\my-site --framework-path .
cd ..\my-site
..\pliegors\target\debug\pliego.exe check
..\pliegors\target\debug\pliego.exe dev 4400

The server binds 127.0.0.1 by default. Use --lan only for deliberate access from a trusted local network.

Quality gates

cargo fmt --check
cargo clippy --workspace --all-targets --locked -- -D warnings
cargo test --workspace --all-targets --locked
RUSTDOCFLAGS="-D warnings" cargo doc --workspace --no-deps --locked
cargo clippy --target wasm32-unknown-unknown --locked -p pliegors-site-client -p spike -- -D warnings
npm ci
npm run check:benchmarks
npm run check:fuzz
npm run check:golden-path
npm run check:telemetry
npm run check:docs
npm run check:distribution
npm run check:phase-1
npm run test:phase-1
npm run check:site

Core documents

Project policies

Apache-2.0. A Celiums Solutions LLC project. Contact hello@pliegors.dev.