Documentation

DOC / 29 / REFERENCE

Crates and API

Choose the public crate that owns each contract, generate exact-version Rustdoc, and avoid depending on implementation-only internals.

In this guideCrates and API
Getting startedProject structureCLI referenceDeveloper loopIncremental buildsRouting and pagesRust viewsEvents and foldsSchemas and snapshotsHyphae verified syncTyped contentBrowser runtimeDOM ownershipNative runtime previewPortable deploymentFull-stack betaOpenSDK previewComponents and languagesBrowser framework conformanceTooling protocolCompatibility and deprecationAdaptive assetsArtifact trustRelease trustPerformance evidenceErrors and diagnosticsVoluntary telemetryBuild and deployCrates and APILicensing and policy

Choose the owning crate

pliego-dom / pliego-macros
Escaped views, authored DOM, typed components, SSR adoption, and mounted ownership
pliego-log / pliego-fold
Typed history, schemas, upcasting, projections, replay, effects, and snapshots
pliego-reactive / pliego-resume
Owned signals, memos, effects, and resumable standard browser actions
pliego-content / pliego-assets
Bounded content ingestion and reproducible adaptive media plans
pliego-artifact / pliego-ssg / pliego-inspect
Portable output, documents, routes, receipts, graphs, staged publication, and verification
pliego-adapters / pliego-hyphae
External browser lifecycle and verified durable sync boundaries
pliego-starters / pliego-cli
Maintained first-use projects and the complete command surface
pliego-router / pliego-runtime (0.4.0-beta.1)
Public G1 beta: sealed routes, streamed layouts, bounded HTTP/1.1 and HTTP/2, OTel, failures, receipts, and three SSR modes
pliego-data / pliego-sdk (0.4.0-beta.1)
Public G2 and OpenSDK beta: data authority, manifests, capability admission, Component Model runtime, effects, compatibility, and tooling
pliego-pboc / pliego-cloudflare (0.4.0-beta.1)
Public G3 preview: exact portable output, host admission, native/OCI and Cloudflare execution, rolling compatibility, and rollback

Core public entry points

pliego_ssg::{Site, Page, Head, Asset}
Author complete documents and publish a deterministic static site
pliego_dom::{View, Element, IntoView, el}
Compose escaped semantic views; use MountScope for owned browser lifetimes
pliego_reactive::{Signal, Memo, Effect}
Model owned reactive state with equality and disposal semantics
pliego_log::{EventSchema, Log, EventCatalogBuilder, SealedEventCatalog}
Encode typed durable history and seal version admission
pliego_fold::{Reducer, Projection, ProjectionSnapshot}
Project accepted events transactionally and restore bound state
pliego_artifact::BuildContext
Capture exact source identity for verified publication
pliego_adapters::{AdapterIsland, AdapterPolicy}
Declare external browser modules and their admission policy
pliego_hyphae::{ReceiptVerifier, VerifiedAppendResponse, VerifiedPullPage}
Cross the durable authority boundary through verified typestate
pliego_runtime::{NativeRuntimeBuilder, TransportLimits, LayoutStreamDocument}
Build against the exact public G1 preview with bounded transport and route-owned streams
pliego_data::{DataContext, LoaderPolicy, ActionPolicy, SessionManager, CachePolicy}
Build against the public G2 beta for typed full-stack data contracts
pliego_pboc::{PbocManifest, HostProfile, verify_bundle}
Validate exact deployment output and negotiate one target before upload
pliego_cloudflare::Application
Bind an admitted PBOC to an exact Rust Worker function registry
pliego_sdk::{ExtensionManifest, HostContract, CapabilityPolicy}
Build against the exact public OpenSDK admission preview

Generate exact-version Rustdoc

shell
git checkout <accepted-revision>
cargo doc --workspace --no-deps --locked
# open target/doc/pliego_ssg/index.html

The repository Rustdoc is the symbol-level reference for an exact revision. This guide explains product contracts and crate ownership; it does not replace signatures, trait bounds, feature flags, or per-item safety notes emitted from the source.

Respect the pre-1.0 boundary

PliegoRS 0.4.0-beta.1 is public pre-1.0 software. Crate names identify stable ownership boundaries, but public signatures may change between prereleases or minor releases. Pin one exact released version across every pliego-* dependency and never mix framework versions inside one application graph.

Read the normative boundaries