PENTAFABRIC 1.3
One suite, explicit permissions
Files, local processing, rights/context, sharing, billing and operations share the same navigation and signed-in session. Customer sessions never inherit operator access.
Authenticated workspace operations
GET /api/suite?op=workbench POST /api/suite?op=governance POST /api/suite?op=governance-save POST /api/suite?op=governance-submit POST /api/suite?op=process-record GET /api/suite?op=operations # operator membership required POST /api/suite?op=governance-export # session JWT, declarations or processing, cursor pagination
These operations require the customer's authenticated session JWT, not the read-only fabric API key. Tenant identity is resolved server-side. Metadata keys and the three existing MCP tools remain read-only.
Rights and context
Declarations create immutable numbered revisions. Saves require the expected current revision; stale edits are rejected. Review requests are idempotent and pass through the existing commerce worker to the controlled CIE/CHLOM request contract. A request is not an assessment, license or approval. Actual CHLOM response fields are displayed when a correlated canonical response exists; storage permissions are not changed automatically.
Local processing
The browser processes source copies, not stored originals. Text input is limited to 2 MiB. JSON uses the browser's standard number representation; store exact large integer identifiers as strings. Images accept JPEG, PNG and WebP up to 20 MiB; decoded images over 40 megapixels are rejected. Checksum inputs are limited to 512 MiB.
Recording an output saves metadata and hashes as CLIENT_REPORTED. An optional parent file must belong to the session's tenant and match the source checksum and size. It does not upload the result. Public links, provider migrations, external processors and paid subscriptions retain their separate service qualification requirements.
Your work.
Your connected fabric.
Persistent file identities, portable manifests and permission-scoped app access. One workspace, with separate authorization for each application.
1. Create a scoped key
Sign in, open API & MCP, and create a named key. Select only the needed read scopes. Keys expire in 1–90 days, are shown once, and can be revoked immediately. Store the key in your server-side secret manager. Never embed it in a website, QR code or URL.
2. Call the REST API
GET /api/fabric?resource=files Authorization: Bearer <your scoped key> GET /api/fabric?resource=passport GET /api/fabric?resource=integrations
files:read grants file metadata. passport:read grants portable manifests. integrations:read grants consent states. Each key belongs to one workspace; caller-supplied tenant IDs are rejected. Lists use a maximum of 100 files per request. Pass after=next_after until has_more is false. Filename search uses query (maximum 120 characters).
Manifest exports are live, paginated metadata, not atomic binary backups. Keep the returned SHA-256 values and persistent pentafabric://workspace/files/file identifiers when integrating another application.
3. Connect an MCP client
Endpoint: https://crownthrive-storage-fabric.vercel.app/api/mcp Authorization: Bearer <your scoped key> Accept: application/json, text/event-stream Content-Type: application/json MCP-Protocol-Version: 2025-06-18
The stateless endpoint supports initialization, ping, tool listing and tool calls. Tools are filtered to your key's scopes: fabric_list_files, fabric_export_manifest, and fabric_list_integrations. Every tool is read-only. File names and metadata must be treated as untrusted data, not agent instructions.
Use a client supporting manually configured Bearer headers, or download the dependency-free Node stdio bridge. OAuth discovery and browser authorization are not implemented; clients requiring those features need a compatible bridge rather than an invented OAuth configuration.
PENTAFABRIC_API_KEY=<injected by your local secret manager> node fabric-mcp.mjs
4. Sharing and QR codes
Within Files & folders, open a file and choose Link + QR. A private locator requires the owner to sign in. Named-recipient links authorize a specific verified email account and expire in 1–30 days. Link revocation changes access on the next request. QR codes are generated within PentaFabric, not sent to an external QR service. Current recipient links expose authorized metadata; binary downloads remain disabled.
5. Ecosystem adapters and consent
CrownThrive IO, ThriveTools OPT and ThriveTools SEO are read from the native service registry. A workspace may record or revoke integration consent. Consent is necessary but not sufficient to execute provider operations: the exact adapter, capacity, budget, rights and recovery controls must also pass. This release transfers no customer data to these services.
6. Storage choices and commercial gates
Web2 means the current managed Wasabi route. The decentralized option targets Storj, which currently has only a verified canary. Hybrid requires independently qualified replication and recovery. Saving a preference does not move bytes. Hot, warm and cold remain logical online-storage policies. No on-chain file storage, wallet custody, IPFS pinning or cheaper physical cold tier is implied.
CrownThrive IO is restricted to its internal web/runtime use. Its hosting quota is not a customer storage pool. Qualified sellable capacity must exclude existing commitments and retained/recovery copies. Checkout stays closed until account-specific commercial capacity and complete fulfillment are accepted.