Solid pods and LWS

Take the Solid pod model further with governed knowledge, executable work and Linked Web Storage access.

Make your Solid data official

Solid puts data under its owner's control. Legra builds on that idea with a much broader workspace: a governed system where people, applications and agents share knowledge and execute accountable work.

Put Solid's ownership model to work with provenance, history, validation and agreements. That is what making knowledge official means in Legra.

What a workspace adds

Versioned knowledge: branches and merges, graph facts, files, deductive reasoning, text and vector search.
Governed collaboration: SHACL validation, reviewed proposals and executable business tests.
Accountable execution: Use Cases and Stories, agent permissions, distributed task trees and transaction-linked evidence.
A working data economy: data products, reusable packages, registry discovery, usage contracts, contribution pricing and multi-party accounting.
Independent infrastructure: choose plaintext-processing Hosts separately from encrypted storage providers, with replication and recovery across failure domains.

Solid's model, LWS compliance

Legra's compliance target is Linked Web Storage (LWS), the W3C protocol carrying the Solid model forward. Each workspace exposes a pod resource interface. LWS supplies the access contract; Legra adds the capabilities above.

LWS is an evolving specification. Conformance refers to a dated LWS draft, rather than implying compatibility with every application built against older Solid protocols.

Your pod, your processing choices

Process health records on your own hardware while the same application uses other workspaces elsewhere. Independent custodians retain encrypted copies; only authorized Hosts receive decryption authority.

Legra distributes executable sub-use cases alongside the knowledge. A mortgage collateral check returns a purpose-specific answer from the customer's workspace while its underlying property records stay private.

Encryption explains trust and durability. Workspaces covers composition.

Developer reference

Technical details

Resource interface over governed state

A workspace maps to one pod. Its default target branch supplies the current resource view. An RDF resource's URL identifies its named graph; file resources reference content-bearing values. Reserved internal graphs stay outside the pod surface.

LWS supplies HTTP resource operations, linked containers, metadata and authorization semantics. Stable resource IRIs and conditional requests bind client edits to the version being changed. Resource permissions remain distinct from full workspace membership.

More than resource CRUD

Legra adds commit-addressed snapshots, branch/merge workflows, SHACL validation, SPARQL queries, derivation provenance and executable Stories. These are Legra capabilities layered behind the pod interface, not features attributed to the LWS specification.

Protocol conformance and cryptographic custody are independent contracts. A pod request executes through authorized serving infrastructure; custodians retain encrypted blocks without acquiring workspace decryption authority.