Docs. Sparse on marketing, dense on reference.
Powerloom is early. The product docs that matter most right now live next to the code — the API reference in the repo, the manifest schemas in the CLI, and the in-app tour inside the console. This page is where they'll consolidate as the product matures.
For operators
Getting started
Create your first workspace, import your directory, deploy an MCP server, bind a role. 20-minute walkthrough.
OU model & RBAC
How organizational units, role bindings, and deny precedence compose. Worked examples from real tenants.
Audit & compliance
The hash-chained audit log, how to query it, how to export to your SIEM, and what records we retain.
MCP deployment
Starter templates (Postgres-RO, Jira-reader, GitHub-scoped) and the pattern for authoring your own.
For developers
CLI reference
Every command, every flag, every exit code. Generated from the source.
Manifest schema
OU, role-binding, agent, and MCP manifests. JSON Schema + worked YAML examples.
API reference
REST endpoints, authentication, pagination, and error shape. OpenAPI spec downloadable.
Meta-agent
The Claude-powered agent that drafts manifest diffs against natural-language change requests. How to invoke it, how to review its work.
Why this page is thin
We decided not to write glossy docs before the product stabilized. Documentation that drifts from the code is worse than no documentation — the operator reads confidently and acts wrongly. This page fills in as each area lands a stable surface.
In the meantime, the in-app tour inside the admin console walks new operators through the default workspace, and the CLI--help output is authoritative for every command.