ABOUT / PLIEGORS

The web is a medium. Reliability is a system.

PliegoRS is a Rust-native framework for authored interfaces whose state, output, and behavior can be inspected and reproduced.

PLG.RS / 01Why it exists

Expressive sites should not become opaque systems.

Modern browser work can be visually ambitious and operationally fragile at the same time. PliegoRS begins from a different premise: state is a fold of typed events, delivery is a verifiable artifact, and enhancement is attached through explicit lifecycles.

The ledger is part of the interface, not an implementation detail.
PLG.RS / 02The position

Four boundaries. One coherent framework.

PliegoRS does not replace the browser, the graphics ecosystem, or a durable data plane. It makes their responsibilities explicit.

01 / EVENTS

History before mutation

Typed events preserve intent. Folds derive state. Replay verifies the result.

02 / OUTPUT

Artifacts before claims

HTML, assets, manifests, checksums, and diagnostics make delivery inspectable.

03 / BROWSER

Lifecycle before glue

Rust/WASM owns application behavior. Mature JavaScript libraries remain behind capability and cleanup contracts.

04 / DATA

Boundaries before lock-in

Static projects stay static. Durable projects can use Hyphae through a versioned, verified protocol.

PLG.RS / 03Stewardship

Open source with accountable authorship.

PliegoRS is stewarded in Medellín by Celiums Solutions LLC. The source is Apache-2.0; the project name and symbol remain protected marks. Governance, security reporting, compatibility, and releases are documented public contracts.

PLG.RS / 04Current state

0.0.1 / PUBLIC PREVIEW

The first release is evidence, not a countdown.

Source, documentation, crates.io packages, platform builds, checksums, security posture, and R0-R7 evidence agree on the 0.0.1 public preview release. Support is intentionally bounded to the published matrix and pre-1.0 policy.

PLIEGORS / MEDELLÍN

The authored web, with a memory.

The public preview carries the completed R0-R7 hardening: documented, inspectable, independently exercised, and owned from source to output.

hello@pliegors.dev