pliego-cli 0.4.0-beta.1

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 beta is v0.4.0-beta.1, published on 2026-07-30. All twenty-one framework crates are coordinated on crates.io at the exact 0.4.0-beta.1 version. PliegoRS remains pre-1.0 software: documented contracts are deliberate, while incompatible changes may still arrive in a new prerelease or minor version with a changelog entry and migration guidance.

This beta unifies G1 native rendering, G2 data, G3 portable deployment, and the G4 incremental engineering preview in one exact package graph. G4 Adoption remains open and no external adoption claim is made. RFC-006 and RFC-007 remain Draft, and ADR-006 remains Proposed; OpenSDK and PBOC are public preview contracts, not stable or accepted 1.0 APIs. The current MSRV is Rust 1.86.

product.capabilities.json is the canonical, machine-readable inventory of what is released, available only from source, partial, not released, or external to this repository. CI rejects drift between that inventory, Cargo metadata, the support matrix, public documentation, and the official site.

Project status

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, verified no-op build, native-event dev, preview, inspect, cache status, cache clean, why artifact, why-rebuilt, causal graphs, selective Page::lazy route reuse, typed HMR, and maintained replayable default, minimal, editorial, and cinematic starters;
• read-only adaptive asset work status with deterministic pending, ready, and invalid jobs for resumable external encoders;
• default-disabled, identifier-free voluntary funnel telemetry with local preview, explicit export, a 64-event bound, and complete deletion;
• pliego doctor, deterministic redacted support bundles, and read-only compatibility checks through pliego upgrade --check;
• six maintained libFuzzer targets, reproducible build/browser/memory benchmarks, and a release-only nine-environment golden matrix;
• a five-target, two-replica release pipeline with reproducible archives, a signed exact-set manifest, CycloneDX SBOM, SLSA-compatible provenance, Sigstore identity, 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, documentation system, security center, and evidence-linked changelog authored by PliegoRS itself;
• an experimental OpenSDK preview with typed Wasm Component admission, resource budgets, effect receipts, Rust/TypeScript/Python conformance, React/Svelte/Lit fixtures, and JSON-RPC/MCP tooling contracts;
• a public G1 native-runtime preview with a sealed dynamic router, bounded HTTP/1.1 and HTTP/2 transport, complete/ordered/async-boundary SSR, route-owned complete and streamed layouts, structured completion events, operator-enabled OpenTelemetry, real-socket adversarial cases, and fixed-load Linux RSS evidence.
• a public G2 beta with capability-scoped resources and loaders, progressive actions, truthful commit/cancellation state, idempotency, secure server-side sessions, bounded uploads, SSRF policy, explicit public/private runtime cache, causal invalidation, application contract manifests, and receipt-driven CLI diagnostics.
• a public G3 PBOC preview with exact bundle verification, pre-upload host admission, explicit rolling and rollback compatibility, a least-privilege Linux OCI target, and one same-build conformance corpus for native and Cloudflare Workers hosts.

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.

R0-R7 and P8 are complete and remain regression gates: reactive safety, artifact trust, verified sync, snapshots and schemas, DOM lifecycle, developer golden path, reproducible distribution, external proof, diagnostics, adversarial validation, benchmarks, clean environments, and voluntary-only telemetry. See the execution backlog, hardening roadmap, and bounded R7 evidence. Production Hyphae operation remains a separate system boundary.

G1 is complete and available in the coordinated public beta. The native router and runtime cover bounded connection and request lifecycles, HTTP/1.1 and HTTP/2, inherited middleware, authored errors, and complete, ordered, and asynchronous-boundary SSR. Complete and streamed documents bind structural layouts and head metadata to the sealed route ownership chain. Slow peers, overload, ambiguous framing, unsupported encoded/multipart bodies, shutdown, and fixed-load RSS are exercised on real Linux sockets. Operators can attach their global OpenTelemetry providers and tracing subscriber; the runtime does not select exporters, storage, retention, or inbound trace trust. OpenSDK continues as the provider-neutral extension boundary required by that runtime; public preview publication is not permission to call either API stable.

G2 first closed in 0.2.0-beta.1 and remains a regression gate in 0.4.0-beta.1. Its two-runtime reference application proves progressive authenticated mutation, session rotation and revocation, idempotent replay, typed failures, cache isolation, read-your-writes invalidation, and redacted diagnostics. The included stores and invalidation coordinator are development/conformance adapters; production durability and cross-process delivery remain provider work. Its bundled stores are deliberately conformance-oriented rather than production durability providers.

G3 first closed at preview stability in 0.3.0-beta.1 and remains a regression gate in 0.4.0-beta.1. PBOC v1alpha1 seals the route graph, runtime contract, artifacts, provenance, required host features, cache policy, secret references, and compatibility chain. The same bundle is verified before execution by the native/OCI and Cloudflare adapters. Portable databases, queues, schedules, durable objects, provider billing, and automatic state migrations remain outside this preview.

Packages

All twenty-one workspace crates are public at the exact 0.4.0-beta.1 version. Applications must keep every pliego-* dependency on that same version; mixed framework graphs are outside the compatibility contract.

Install

Install the CLI from crates.io:

cargo install pliego-cli --version 0.4.0-beta.1 --locked
pliego new my-site
cd my-site
pliego check
pliego dev

Pin all framework crates to the coordinated beta explicitly:

[dependencies]
pliego-router = "=0.4.0-beta.1"
pliego-runtime = "=0.4.0-beta.1"
pliego-data = "=0.4.0-beta.1"
pliego-pboc = "=0.4.0-beta.1"
pliego-sdk = "=0.4.0-beta.1"

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
pliego cache status

The commands above are part of the published 0.4.0-beta.1 CLI. They run locally and do not upload project data.

Optional PliegoCSS companion

PliegoRS works with ordinary CSS and does not require PliegoCSS. To opt into the separately released compiler for typed styles and static validation:

cargo install pliego-cssc --version =0.1.0-rc.2 --locked
pliego css check --seed

pliego css check only delegates from the canonical project root. PliegoCSS compilation, watch mode, manifests, and route/island bundles remain explicit pliego-cssc workflows and produce static CSS rather than a styling runtime.

Evaluate OpenSDK

OpenSDK ships in the coordinated beta. Its complete repository conformance path can be reproduced from an exact release checkout:

git clone https://github.com/celiumsai/pliegors.git
cd pliegors
cargo run -p pliego-cli --locked -- sdk compatibility
npm ci
npm run check:opensdk:all

The compatibility report is portable. The complete conformance path compiles a Rust Wasm Component and runs real browser fixtures; it is a release-blocking Linux CI gate and can be reproduced from Linux or WSL.

The Rust Wasm Component toolchain is the reference sandboxed implementation. The TypeScript and Python process bridges are conformance implementations, not sandboxed Component Model SDKs. Browser fixtures prove the explicit adapter lifecycle for React, Svelte, and Lit without replacing those ecosystems.

Evaluate the G2 beta

G2 is published as part of the exact coordinated package graph. Its complete reference application remains in the release source:

git clone https://github.com/celiumsai/pliegors.git
cd pliegors
cargo test -p pliego-data
cargo test -p fullstack-pliego --test two_replicas
cargo run -p fullstack-pliego

The reference server binds loopback by default. Its in-memory resources are conformance fixtures rather than production identity, storage, or cache services. Read the G2 evidence before adopting the source API.

Evaluate portable deployment

Validate a sealed output, prove that a host supports every required feature, and check a rolling transition before any upload:

pliego pboc validate dist/pliego.pboc.json --root dist
pliego pboc admit dist/pliego.pboc.json --root dist --host native
pliego pboc compatibility active/pliego.pboc.json \
  candidate/pliego.pboc.json --direction rolling
npm run check:provider-tck

The provider TCK builds the same PBOC for static musl/OCI and Cloudflare Workers, exercises seven equivalent HTTP cases, rejects unsupported required features, replays rollback, and scans the complete bundle for a secret sentinel. See the portable deployment guide.

Release trust

The v0.4.0-beta.1 release contains artifacts covering five platform targets, two installer formats, checksums, a reproducible source archive, verification tools, a CycloneDX SBOM, SLSA-compatible provenance, and the signed P8 golden matrix. Linux x86_64 and ARM64 are production targets; macOS x86_64/ARM64 and Windows x86_64 are development targets.

Installers verify the pinned Ed25519 release identity, manifest, selected archive, checksum sidecar, and exact asset set before extraction. Separate Sigstore bundles bind the supply-chain attestations and nine-environment golden evidence. Review the distribution guide, supply-chain contract, and security policy before production use.

Installers require Node.js. Download them to disk and verify the complete release bundle before running them; never pipe a network response directly into a shell.

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 --all -- --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:g4-engineering
npm run measure:g4-engineering -- --samples 1
npm run check:telemetry
npm run check:opensdk:all
npm run check:docs
npm run check:distribution
npm run check:phase-1
npm run test:phase-1
npm run check:site
npm run check:site-deployment
npm run check:wasm-lifetimes
npm run check:pboc
npm run check:provider-tck

The complete OpenSDK Component and browser conformance gate runs on Linux in CI. Windows contributors can reproduce that exact path through WSL while still using the native Windows CLI for normal project development.

Core documents

• Online documentation
• Public changelog
• Security and trust center
• Current execution backlog
• G4 engineering readiness
• G4 accepted engineering evidence
• Founding specification
• PliegoRS and Hyphae target protocol
• Hyphae verified sync guide
• Event schema and projection snapshot contract
• DOM lifecycle contract
• Golden developer experience contract
• Candidate distribution contract
• Product constitution and stability policy
• P8 trust and adoption contract
• Diagnostics, reproduction reports, and upgrade checks
• Supply-chain attestations
• Fuzzing and adversarial testing
• Reproducible benchmarks
• Release-only golden environment matrix
• Voluntary telemetry and local funnel report
• OpenSDK foundation and security model
• Multilanguage conformance
• Browser framework conformance
• JSON-RPC and MCP tooling protocol
• Compatibility and deprecation policy
• Canonical product capability manifest
• Full-stack runtime threat model
• G2 full-stack beta evidence
• Optional PliegoCSS companion evidence
• OpenSDK planes and capability RFC
• Portable build output RFC
• Native HTTP runtime RFC
• Full-stack route graph RFC
• Data, actions, sessions, and cache RFC
• Wasmtime security-floor decision
• Projection snapshot decision
• R3 acceptance evidence
• R4 acceptance evidence
• R5 acceptance evidence
• R6 acceptance evidence
• Framework API boundaries
• Native migration gate
• Framework readiness review
• Security, plugins, and adaptive media
• Distribution and release
• Hardening roadmap

Project policies

main is the repository's sole persistent branch. Contributions use short-lived pull-request branches, pass the protected checks, merge linearly, and delete the branch immediately after integration. Automated security alerts, CodeQL, secret scanning, cargo audit, and npm audit remain active.

• Changelog
• Governance
• Contributing
• Security
• Support
• Community code of conduct
• Trademark policy
• Third-party notices
• Identity assets
• Public mailbox Worker

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