@voltro/plugin-rbac 0.1.0

package/CHANGELOG.md

@@ -0,0 +1,52 @@
+# Changelog
+
+All notable changes to the `@voltro/*` packages are recorded here. The format
+follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
+
+## Stability contract — read this before you pin a version
+
+Voltro is **`0.x` — pre-1.0, and deliberately so.** Under SemVer, `0.y.z` means
+"anything MAY change." We hold to exactly that, stated out loud:
+
+- **Pin exact versions.** Depend on `@voltro/runtime@0.4.2`, never `^0.4.2` or
+  `~0.4.2`. There is no compatible-range promise below 1.0.
+- **Every MINOR may break.** Breaking changes land on a minor bump (`0.4.x →
+  0.5.0`); patches (`0.4.1 → 0.4.2`) are additive or fixes only. This is the
+  standard `0.x` reading of SemVer — the minor slot carries breaking under `0.x`.
+- **Read this changelog before upgrading.** The `⚠ BREAKING` section of each
+  release lists every incompatible change with its migration. It is the only
+  migration path we provide — there is no deprecation cycle, no compat shim.
+- **All packages release together (lockstep).** One coordinated version across
+  the whole framework; the git tag is the source of truth.
+
+This is not a placeholder disclaimer — it is the contract. The framework is
+refactored aggressively while it has no external stability obligations, and that
+velocity is the point. A stable-core tier and per-package `1.0` graduation are
+planned, but not yet; until then, treat the whole surface as movable and pin
+exact.
+
+The **public API** of each package is its `publishConfig.exports` entry points,
+minus anything marked `@internal` (those are cross-package internals and are
+stripped from the published `.d.ts`). Importing a deep path that isn't an
+exported entry point is unsupported.
+
+---
+
+## [Unreleased]
+
+_Changes staged for the next release accumulate here (rolled up from
+`.changes/*.md` at tag time — see `.changes/README.md`)._
+
+---
+
+## [0.1.0]
+
+Initial pre-release baseline. This is the starting point the changelog tracks
+from; it is not an exhaustive history of prior development. The framework ships
+as `@voltro/*` packages spanning the runtime, database/query layer, web client
+and router, durable workflows, the CLI, and the plugin ecosystem
+(auth, storage, mail, billing, observability, and more). Not published to a
+public registry yet.
+
+Subsequent releases record their deltas from here under dated headings, with
+`⚠ BREAKING` first.

package/LICENSE

@@ -0,0 +1,57 @@
+Voltro — Proprietary Software License
+
+Copyright (c) 2026 Voltro UG. All rights reserved.
+
+This software and all associated source code, documentation, and other
+materials (the "Software") are the proprietary property of Voltro UG
+("Voltro"). This is NOT open-source software.
+
+Your access to and use of the Software is governed exclusively by the Voltro
+Terms of Service at:
+
+    https://voltro.cloud/legal/terms
+
+By downloading, installing, or using the Software you agree to those Terms.
+Subject to and conditioned on your continued compliance with them, Voltro
+grants you a limited, non-exclusive, non-transferable, non-sublicensable,
+revocable license to use the Software. All rights not expressly granted in the
+Terms are reserved by Voltro. If you do not agree to the Terms, you have no
+license and may not use the Software.
+
+The Terms of Service — including the scope of permitted use, plan
+entitlements, fees, and pricing — may change from time to time. The version in
+force is the one published at the URL above. Commercial terms and pricing are
+NOT part of this notice and are not fixed by, or granted in perpetuity by, the
+version of the Software in which this file appears.
+
+Permitted use — your own software. Voltro is a development framework. You may
+use the Software to build, run, and commercially distribute your own
+applications and services, and to charge your own customers for them, without
+owing Voltro any share of that revenue or any further permission beyond the
+Terms. Applications you build with the Software are yours.
+
+Prohibited use — reselling Voltro. You may NOT redistribute, resell,
+sublicense, publish, or otherwise provide the Software itself — in whole or in
+part, in source or compiled form — to third parties as a library, framework,
+SDK, template, starter, or development tool for them to build upon, whether
+standalone or repackaged. Shipping the Software as a non-separable, bundled
+dependency inside an application you deliver (for example, compiled into your
+deployed app) is permitted; extracting or re-exposing it as a reusable
+component for others is not.
+
+Except as expressly permitted above or by the Terms, you may not copy, modify,
+merge, publish, sublicense, sell, distribute, or create derivative works of the
+Software, in whole or in part.
+
+Third-party open-source components distributed alongside the Software are the
+property of their respective owners and are licensed under their own terms; see
+THIRD-PARTY-NOTICES.md where provided. Nothing in this notice limits your
+rights, or extends Voltro's, in those components.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT. IN NO EVENT SHALL
+VOLTRO BE LIABLE FOR ANY CLAIM, DAMAGES, OR OTHER LIABILITY ARISING FROM,
+OUT OF, OR IN CONNECTION WITH THE SOFTWARE OR ITS USE.
+
+For licensing inquiries, contact Voltro UG.

package/README.md

@@ -0,0 +1,26 @@
+<div align="center">
+
+# @voltro/plugin-rbac
+
+**Role-based access control — roles compile to scopes on top of @voltro/protocol's scope system. Ships rbacPlugin() (role→scope interceptor + typed Forbidden error), the permission()/assertPermission()/anyPermission() handler guards, the compileRoles() pure compiler, cross-dialect roles + userRoles tables, and a browser-safe useCan() UI affordance.**
+
+[📖 Documentation](https://docs.voltro.dev/docs/plugins/rbac) · [Changelog](./CHANGELOG.md) · [voltro.dev](https://voltro.dev) · [Voltro Cloud](https://voltro.cloud)
+
+</div>
+
+---
+
+```sh
+npm install @voltro/plugin-rbac
+```
+
+> ### [→ Read the documentation for @voltro/plugin-rbac](https://docs.voltro.dev/docs/plugins/rbac)
+
+Installation, guides, the full API reference, and examples all live in the
+**[Voltro documentation](https://docs.voltro.dev/docs/intro/getting-started)** — the single source of truth. This README is
+deliberately short so there is nothing here to drift out of date.
+
+## License
+
+Proprietary. © 2026 Voltro UG. Your use is governed by the
+[Terms of Service](https://voltro.cloud/legal/terms). See the bundled `LICENSE`.

package/SECURITY.md

@@ -0,0 +1,56 @@
+# Security Policy
+
+We take the security of Voltro and the applications built on it seriously. This
+document explains how to report a vulnerability and what to expect in return.
+
+## Reporting a vulnerability
+
+**Please do not open public issues or discuss suspected vulnerabilities in
+public channels.** Report them privately by email:
+
+**security contact: [support@voltro.dev](mailto:support@voltro.dev)**
+(subject line: `SECURITY`).
+
+Include, where you can:
+
+- the affected package(s) and version(s) (e.g. `@voltro/runtime@x.y.z`);
+- a description of the issue and its impact;
+- a minimal reproduction or proof of concept;
+- any suggested remediation.
+
+If you'd like to encrypt your report, ask in a first plain email and we'll
+arrange a key.
+
+## What to expect
+
+- **Acknowledgement** of your report within **3 business days**.
+- An initial assessment (severity, affected surface) and a remediation plan as
+  soon as we've reproduced the issue.
+- **Coordinated disclosure:** we'll agree a disclosure timeline with you and
+  credit you in the release notes if you wish. Please give us reasonable time to
+  ship a fix before any public disclosure.
+
+We do not currently run a paid bug-bounty program, but we genuinely appreciate
+responsible disclosure and will credit reporters.
+
+## Software Bill of Materials (SBOM)
+
+A CycloneDX SBOM of the third-party runtime dependency graph is generated for the
+published packages (`pnpm gen:sbom` → `sbom.cdx.json`). If your procurement or
+security team needs it, request it at
+[support@voltro.dev](mailto:support@voltro.dev).
+
+## Supported versions
+
+Voltro is pre-1.0 and ships in lockstep: **only the latest published minor of
+each `@voltro/*` package receives security fixes.** Please upgrade to the latest
+release before reporting, and pin exact versions in production.
+
+## Scope
+
+In scope: the published `@voltro/*` packages and the framework's own code.
+
+Out of scope: vulnerabilities in third-party dependencies that are already
+tracked upstream (we monitor these via a production-dependency audit gate in
+CI), and issues that require a non-default, explicitly-unsafe configuration. If
+you're unsure, report it anyway — we'd rather hear about it.

package/THIRD-PARTY-NOTICES.md

@@ -0,0 +1,347 @@
+# Third-Party Notices — @voltro/plugin-rbac
+
+This package depends on the open-source software listed below. Each is the
+property of its respective copyright holders and is used under the terms of
+its license. This file is provided for attribution; it grants no rights in
+@voltro/plugin-rbac itself, which is proprietary (see LICENSE).
+
+Generated from the resolved runtime dependency closure (6 packages).
+
+---
+
+## @effect/sql@0.51.1
+
+License: MIT
+
+```
+MIT License
+
+Copyright (c) 2023-present The Contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+```
+
+## jose@6.2.3
+
+License: MIT
+
+```
+The MIT License (MIT)
+
+Copyright (c) 2018 Filip Skokan
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+```
+
+## layerr@3.0.0
+
+License: MIT
+
+```
+MIT License
+
+Copyright (c) 2020 Perry Mitchell
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+```
+
+## typeid-js@1.2.0
+
+License: Apache-2.0
+
+```
+Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.
+```
+
+## ulidx@2.4.1
+
+License: MIT
+
+```
+MIT License
+
+Copyright (c) 2021 Perry Mitchell
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+```
+
+## uuid@11.1.1
+
+License: MIT
+
+```
+The MIT License (MIT)
+
+Copyright (c) 2010-2020 Robert Kieffer and other contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+```
+

package/dist/index.d.ts

@@ -0,0 +1,331 @@
+import { Effect } from 'effect';
+import { Schema } from 'effect';
+import { SchemaTable } from '@voltro/database';
+import { Subject } from '@voltro/protocol';
+import { VoltroPlugin } from '@voltro/protocol';
+
+/**
+ * Effect-form OR guard. Passes if the caller holds AT LEAST ONE of the
+ * listed permissions. Fails `Forbidden` (naming the first option) when it
+ * holds none. The `admin:full` bypass passes.
+ *
+ * ```ts
+ * yield* anyPermission(ctx, ['notes:write', 'notes:admin'])
+ * ```
+ */
+export declare const anyPermission: (ctx: RbacContext, required: ReadonlyArray<string>) => Effect.Effect<void, Forbidden>;
+
+/**
+ * Sync-form guard for async (non-Effect) handlers. THROWS `Forbidden`
+ * when the caller lacks the required permission(s). Array = AND.
+ *
+ * ```ts
+ * const execute = async (input, ctx) => {
+ *   assertPermission(ctx, 'notes:write')
+ *   return ctx.store.insert('notes', { ... })
+ * }
+ * ```
+ */
+export declare const assertPermission: (ctx: RbacContext, required: string | ReadonlyArray<string>) => void;
+
+/**
+ * Build the `userRoles` table. `tenantId` scopes a role assignment to the
+ * active tenant (`null` = a global, all-tenant role).
+ *
+ * - `multitenant: true` → `tenantId` is a nullable FK to the `tenants`
+ *   table (resolved via `requireTenants()`), so the DDL carries the
+ *   foreign key when multitenancy is present.
+ * - `multitenant: false` (default) → `tenantId` is a plain
+ *   `text().nullable()` column, so the package has NO hard dependency on
+ *   @voltro/plugin-multitenancy for single-tenant projects.
+ */
+export declare const buildUserRolesTable: (options?: {
+    readonly multitenant?: boolean;
+}) => RbacTable;
+
+/** Pure boolean check — no throw, no Effect. For branching inside a handler. */
+export declare const can: (ctx: RbacContext, required: string | ReadonlyArray<string>) => boolean;
+
+/**
+ * Compile a caller's granted role slugs into a flat, deduped scope set.
+ *
+ * - Unknown slugs (not present in `roleMap`) are ignored — a stale role
+ *   reference never grants anything, and never throws.
+ * - If ANY granted role lists the `'*'` wildcard, the result collapses to
+ *   `[ADMIN_SCOPE]` (the blanket bypass) — no point carrying the rest.
+ * - Otherwise the result is the deduped union of every listed permission,
+ *   in first-seen order.
+ *
+ * The output is a SCOPE set: feed it straight into `hasScope` / the
+ * `permission()` guard. A project can mix declarative roles AND raw
+ * key-minted scopes; both land in the same resolved set.
+ */
+export declare const compileRoles: (roleSlugs: ReadonlyArray<string>, roleMap: RoleMap) => ReadonlyArray<string>;
+
+/**
+ * A {@link RoleResolver} backed by the `userRoles` table — resolves a
+ * subject's role slugs from the store, scoped to the subject's tenant (so
+ * tenant-aware role assignments Just Work). Drop into
+ * `rbacPlugin({ resolveRoles: dataStoreRoleResolver(userRoleStore(ds)) })`.
+ */
+export declare const dataStoreRoleResolver: (store: UserRoleStore) => RoleResolver;
+
+/**
+ * Raised when a caller lacks a required permission. Distinct from
+ * protocol's `ScopeError` so rbac owns its own wire surface; `rbacPlugin`
+ * registers it via `errorSchemas` so it decodes TYPED on the client.
+ *
+ * Declare it in a mutation's `error:` schema (or rely on `rbacPlugin`'s
+ * cross-cutting registration) so callers can pattern-match on
+ * `_tag === 'Forbidden'`.
+ */
+export declare class Forbidden extends Forbidden_base {
+}
+
+declare const Forbidden_base: Schema.TaggedErrorClass<Forbidden, "Forbidden", {
+    readonly _tag: Schema.tag<"Forbidden">;
+} & {
+    /** The permission (or first missing permission) the caller lacked. */
+    required: typeof Schema.String;
+    /** Optional human-readable context. */
+    reason: Schema.optional<typeof Schema.String>;
+}>;
+
+/**
+ * Compile a subject's roles + raw permissions into one resolved scope
+ * set: `subject.scopes` ∪ compiled(roles) ∪ extraPermissions, deduped.
+ * Pure given resolved inputs — the interceptor awaits the (possibly
+ * async) resolvers, then calls this.
+ */
+export declare const mergeResolvedScopes: (subject: Subject, roleSlugs: ReadonlyArray<string>, roleMap: RoleMap, extraPermissions?: ReadonlyArray<string>) => ReadonlyArray<string>;
+
+/**
+ * Default `RoleResolver` — reads `subject.metadata.roles` if it's a
+ * `string[]`, else `[]`. The framework never reads `metadata`; it's the
+ * IdP slot, so a strategy that wants config-driven roles puts the slugs
+ * there and the default resolver picks them up table-less.
+ */
+export declare const metadataRoleResolver: RoleResolver;
+
+/**
+ * Effect-form guard. Fails with a typed `Forbidden` on the error channel
+ * when the caller lacks the required permission(s). An array means ALL
+ * are required (AND). The `admin:full` bypass passes everything.
+ *
+ * ```ts
+ * export default (input, ctx) => Effect.gen(function* () {
+ *   yield* permission(ctx, 'notes:write')
+ *   // ...
+ * })
+ * ```
+ */
+export declare const permission: (ctx: RbacContext, required: string | ReadonlyArray<string>) => Effect.Effect<void, Forbidden>;
+
+/**
+ * A resolver that yields raw permission strings merged into the resolved
+ * set IN ADDITION to role-derived ones (per-row ACLs, feature flags, …).
+ */
+export declare type PermissionResolver = (subject: Subject) => ReadonlyArray<string> | Promise<ReadonlyArray<string>>;
+
+/**
+ * Anything carrying a resolved subject under `ctx.request.subject` — the
+ * shape every handler executor receives (`AppContext`). Kept structural
+ * so rbac needs no dependency on @voltro/runtime.
+ */
+export declare interface RbacContext {
+    readonly request: {
+        readonly subject: Subject;
+    };
+}
+
+/**
+ * Build the rbac plugin. Returns the `VoltroPlugin` you pass into
+ * `app.config.ts`'s `plugins: [...]` array.
+ *
+ * The interceptor runs once per mutation / query / action, BEFORE the
+ * executor: it resolves the caller's roles, compiles them to scopes,
+ * merges with the subject's raw scopes + any extra permissions, and
+ * stashes the resolved set for `permission()` to read. A resolver failure
+ * is logged and degrades to the subject's raw scopes — never silently
+ * grants.
+ */
+export declare const rbacPlugin: (options: RbacPluginOptions) => VoltroPlugin;
+
+export declare interface RbacPluginOptions {
+    /**
+     * Declarative role → permission map. Each role lists the permission
+     * strings (== scope strings) it grants. `'*'` in any role's list
+     * expands to the `admin:full` blanket bypass.
+     *
+     * ```ts
+     * roles: {
+     *   viewer: ['notes:read'],
+     *   editor: ['notes:read', 'notes:write'],
+     *   admin:  ['*'],
+     * }
+     * ```
+     */
+    readonly roles: RoleMap;
+    /**
+     * Where a subject's role slugs come from. Default: `metadataRoleResolver`
+     * (reads `subject.metadata.roles` as a `string[]`). A project that
+     * assigns roles at runtime supplies its own — e.g. a DB lookup filtered
+     * by `subject.tenantId` for tenant-aware roles.
+     */
+    readonly resolveRoles?: RoleResolver;
+    /**
+     * Extra raw permission strings merged into the resolved set in ADDITION
+     * to role-derived ones (per-row ACLs, feature flags, …). Default: none.
+     */
+    readonly resolvePermissions?: PermissionResolver;
+    /**
+     * Contribute the `roles` + `userRoles` tables via `extendSchema.tables`.
+     * Default `false` — config-only / metadata-resolver projects run
+     * table-less. Set `true` (or `{ multitenant: true }` for a FK to
+     * `tenants`) when assigning roles at runtime against the DB.
+     */
+    readonly tables?: boolean | {
+        readonly multitenant?: boolean;
+    };
+}
+
+/**
+ * The slice of a built `Table` this package exposes: the table name, its
+ * columns, and its indexes. `SchemaTable` is @voltro/database's PUBLIC
+ * structural table type — it names exactly this surface WITHOUT dragging in
+ * the private column-builder class the fully-inferred `Table` generic would
+ * (which is what forces TS4094 across a package boundary). Alias kept for
+ * readability at the annotation sites below.
+ */
+export declare type RbacTable = SchemaTable;
+
+/**
+ * Both rbac tables, ready to spread into `extendSchema.tables`. Pass
+ * `{ multitenant: true }` to make `userRoles.tenantId` a FK to `tenants`.
+ */
+export declare const rbacTables: (options?: {
+    readonly multitenant?: boolean;
+}) => ReadonlyArray<RbacTable>;
+
+/**
+ * Read the role slugs that produced the subject's resolved set, if the
+ * interceptor recorded them. Empty when roles weren't resolved (or the
+ * plugin isn't installed). For introspection only — NOT an authz signal.
+ */
+export declare const resolvedRoles: (subject: Subject) => ReadonlyArray<string>;
+
+/**
+ * Read the resolved scope set for a subject. Returns the interceptor's
+ * compiled set if present; otherwise falls back to the subject's own
+ * `scopes` (raw key-minted scopes still gate). Never returns undefined.
+ */
+export declare const resolvedScopes: (subject: Subject) => ReadonlyArray<string>;
+
+/**
+ * A role: a slug plus the flat permission strings it grants. The
+ * permission strings ARE scope strings — `compileRoles` unions them into
+ * the caller's resolved scope set.
+ *
+ * The wildcard `'*'` in any granted role's permission list expands to the
+ * blanket `ADMIN_SCOPE` bypass — a caller who holds a `'*'` role passes
+ * every `permission()` check.
+ */
+export declare interface RoleDefinition {
+    /** Stable role identifier, e.g. `'editor'`. */
+    readonly slug: string;
+    /** Flat permission strings, e.g. `['notes:read', 'notes:write']` or `['*']`. */
+    readonly permissions: ReadonlyArray<string>;
+}
+
+/**
+ * The declarative `roles:` map passed to `rbacPlugin({ roles })`. Maps a
+ * role slug to the permission strings it grants. `'*'` is the wildcard
+ * that compiles to `[ADMIN_SCOPE]`.
+ *
+ * ```ts
+ * const roles = {
+ *   viewer: ['notes:read', 'comments:read'],
+ *   editor: ['notes:read', 'notes:write', 'comments:read', 'comments:write'],
+ *   admin:  ['*'],
+ * }
+ * ```
+ */
+export declare type RoleMap = Readonly<Record<string, ReadonlyArray<string>>>;
+
+/**
+ * A resolver that yields the role slugs a subject holds. The default
+ * reads `subject.metadata.roles` (a `string[]`) when present; a project
+ * that assigns roles at runtime supplies its own (e.g. a DB lookup
+ * filtered by `subject.tenantId`).
+ */
+export declare type RoleResolver = (subject: Subject) => ReadonlyArray<string> | Promise<ReadonlyArray<string>>;
+
+export declare const ROLES_TABLE = "_voltro_rbac_roles";
+
+/**
+ * Normalise a `RoleMap` into a list of `RoleDefinition`s. Convenience for
+ * callers that want the structured shape (e.g. to seed the `roles` table
+ * or render a role picker).
+ */
+export declare const rolesFromMap: (roleMap: RoleMap) => ReadonlyArray<RoleDefinition>;
+
+/**
+ * The `roles` table: one row per role, carrying its flat permission set.
+ * `permissions` is a portable `json<string[]>()` column (JSONB on pg,
+ * JSON on mysql/mariadb, NVARCHAR(MAX) on mssql, TEXT on sqlite) — never
+ * a postgres-only `text[]`.
+ */
+export declare const rolesTable: RbacTable;
+
+/**
+ * Stash the resolved scope set (+ originating role slugs) for a subject.
+ * Called once per request by the interceptor, before the executor runs.
+ */
+export declare const setResolvedScopes: (subject: Subject, scopes: ReadonlyArray<string>, roleSlugs?: ReadonlyArray<string>) => void;
+
+export declare const USER_ROLES_TABLE = "_voltro_rbac_user_roles";
+
+/** A role assignment as stored: the subject, the role slug, and its tenant scope. */
+export declare interface UserRoleAssignment {
+    readonly userId: string;
+    readonly roleSlug: string;
+    /** `null` = a global (all-tenant) assignment. */
+    readonly tenantId?: string | null;
+}
+
+/** Narrow slice of the framework DataStore the user-role helpers need. */
+export declare interface UserRoleDataStore {
+    query: (descriptor: Record<string, unknown>) => Promise<ReadonlyArray<Record<string, unknown>>>;
+    insert: (table: string, row: Record<string, unknown>) => Promise<unknown>;
+    delete: (table: string, primaryKey: string) => Promise<unknown>;
+}
+
+/** Single-tenant default — `tenantId` is a plain nullable text column. */
+export declare const userRolesTable: RbacTable;
+
+/**
+ * Assign / revoke / read role assignments over the `userRoles` table. All
+ * methods are tenant-aware: `tenantId` scopes an assignment (or query) to a
+ * tenant; `null` (the default) is a global assignment across all tenants.
+ */
+export declare interface UserRoleStore {
+    /** Grant `roleSlug` to `userId` (idempotent — a duplicate assignment is a no-op). */
+    readonly assign: (userId: string, roleSlug: string, tenantId?: string | null) => Promise<void>;
+    /** Remove `roleSlug` from `userId` for the given tenant scope. */
+    readonly revoke: (userId: string, roleSlug: string, tenantId?: string | null) => Promise<void>;
+    /**
+     * The role slugs `userId` holds. With a `tenantId`, returns the tenant's
+     * assignments PLUS global (`tenantId: null`) ones; without, every assignment.
+     */
+    readonly rolesOf: (userId: string, tenantId?: string | null) => Promise<ReadonlyArray<string>>;
+}
+
+/** A {@link UserRoleStore} over a framework DataStore. */
+export declare const userRoleStore: (store: UserRoleDataStore) => UserRoleStore;
+
+export { VoltroPlugin }
+
+/** The wildcard permission string that compiles to the admin bypass. */
+export declare const WILDCARD_PERMISSION = "*";
+
+export { }

package/dist/index.js

@@ -0,0 +1,82 @@
+import { a as e, c as t, d as n, f as r, i, l as a, n as o, o as s, p as c, r as l, s as u, t as d, u as f } from "./permission-1Z68oD-d.js";
+import { Effect as p } from "effect";
+import { definePlugin as m } from "@voltro/protocol";
+import { createLogger as h } from "@voltro/logger";
+import { and as g, boolean as _, eq as v, id as y, json as b, or as x, reference as S, requireTenants as C, table as w, text as T } from "@voltro/database";
+//#region src/tables.ts
+var E = "_voltro_rbac_roles", D = "_voltro_rbac_user_roles", O = w(E, {
+	id: y({ prefix: "role" }),
+	slug: T().unique(),
+	name: T(),
+	permissions: b(),
+	isDefault: _().default(!1)
+}).index("byRolesSlug", ["slug"]), k = (e = {}) => w(D, {
+	id: y({ prefix: "urole" }),
+	userId: T(),
+	tenantId: e.multitenant ? S(C(), { index: !1 }).nullable() : T().nullable(),
+	roleSlug: T()
+}).index("byUserTenant", ["userId", "tenantId"]).index("byRoleSlug", ["roleSlug"]), A = k(), j = (e = {}) => [O, k(e)], M = (e, t) => e.query({
+	table: D,
+	predicate: t,
+	order: [{
+		column: "id",
+		direction: "asc"
+	}],
+	take: void 0,
+	skip: void 0,
+	projection: void 0
+}), N = (e) => {
+	let t = (t, n, r) => M(e, g(v("userId", t), v("roleSlug", n), v("tenantId", r)));
+	return {
+		assign: async (n, r, i = null) => {
+			(await t(n, r, i)).length > 0 || await e.insert(D, {
+				userId: n,
+				roleSlug: r,
+				tenantId: i
+			});
+		},
+		revoke: async (n, r, i = null) => {
+			let a = await t(n, r, i);
+			for (let t of a) await e.delete(D, String(t.id));
+		},
+		rolesOf: async (t, n) => {
+			let r = (n === void 0 ? await M(e, v("userId", t)) : await M(e, g(v("userId", t), P(n)))).map((e) => String(e.roleSlug));
+			return [...new Set(r)];
+		}
+	};
+}, P = (e) => e === null ? v("tenantId", null) : x(v("tenantId", e), v("tenantId", null)), F = (e) => (t) => {
+	let n = ("tenantId" in t ? t.tenantId : void 0) ?? null, r = ("id" in t ? t.id : void 0) ?? null;
+	return r ? e.rolesOf(r, n) : [];
+}, I = h({ scope: "@voltro/plugin-rbac" }), L = (e) => e instanceof Promise ? p.promise(() => e) : p.succeed(e), R = (e) => {
+	let t = e.resolveRoles ?? u, n = e.resolvePermissions, r = e.tables !== void 0 && e.tables !== !1, i = typeof e.tables == "object" ? e.tables : {}, a = (r, i) => p.gen(function* () {
+		let a = yield* L(t(i.subject)).pipe(p.catchAllCause((e) => (I.warn("resolveRoles failed; falling back to raw subject scopes", {
+			tag: i.tag,
+			traceId: i.traceId,
+			cause: String(e)
+		}), p.succeed([])))), o = n ? yield* L(n(i.subject)).pipe(p.catchAllCause(() => p.succeed([]))) : [], c = s(i.subject, a, e.roles, o);
+		return f(i.subject, c, a), yield* r;
+	});
+	return m({
+		name: "@voltro/plugin-rbac",
+		description: "Role-based access control — roles compile to scopes on top of the protocol scope system. Ships the permission() handler guard + a role→scope interceptor + a typed Forbidden error.",
+		permissions: [
+			"rpc:intercept:mutation",
+			"rpc:intercept:query",
+			"rpc:intercept:action",
+			...r ? ["store:write"] : []
+		],
+		interceptMutation: a,
+		interceptQuery: a,
+		interceptAction: a,
+		errorSchemas: [{
+			schema: d,
+			import: {
+				module: "@voltro/plugin-rbac/errors",
+				name: "Forbidden"
+			}
+		}],
+		...r ? { extendSchema: { tables: [...j(i)] } } : {}
+	});
+};
+//#endregion
+export { d as Forbidden, E as ROLES_TABLE, D as USER_ROLES_TABLE, n as WILDCARD_PERMISSION, o as anyPermission, l as assertPermission, k as buildUserRolesTable, i as can, r as compileRoles, F as dataStoreRoleResolver, s as mergeResolvedScopes, u as metadataRoleResolver, e as permission, R as rbacPlugin, j as rbacTables, t as resolvedRoles, a as resolvedScopes, c as rolesFromMap, O as rolesTable, f as setResolvedScopes, N as userRoleStore, A as userRolesTable };

package/dist/permission-1Z68oD-d.js

@@ -0,0 +1,62 @@
+import { Effect as e, Schema as t } from "effect";
+import { ADMIN_SCOPE as n, subjectScopes as r } from "@voltro/protocol";
+//#region src/roles.ts
+var i = "*", a = (e, t) => {
+	let r = [], i = /* @__PURE__ */ new Set();
+	for (let a of e) {
+		let e = t[a];
+		if (e !== void 0) for (let t of e) {
+			if (t === "*") return [n];
+			i.has(t) || (i.add(t), r.push(t));
+		}
+	}
+	return r;
+}, o = (e) => Object.entries(e).map(([e, t]) => ({
+	slug: e,
+	permissions: t
+})), s = /* @__PURE__ */ new WeakMap(), c = /* @__PURE__ */ new WeakMap(), l = (e, t, n) => {
+	s.set(e, t), n !== void 0 && c.set(e, n);
+}, u = (e) => s.get(e) ?? r(e), d = (e) => c.get(e) ?? [], f = (e) => {
+	if (!("metadata" in e) || e.metadata === void 0) return [];
+	let t = e.metadata.roles;
+	return Array.isArray(t) ? t.filter((e) => typeof e == "string") : [];
+}, p = (e, t, n, i = []) => {
+	let o = a(t, n), s = [], c = /* @__PURE__ */ new Set();
+	for (let t of [
+		...r(e),
+		...o,
+		...i
+	]) c.has(t) || (c.add(t), s.push(t));
+	return s;
+}, m = class extends t.TaggedError()("Forbidden", {
+	required: t.String,
+	reason: t.optional(t.String)
+}) {}, h = (e, t) => {
+	let r = u(e);
+	return r.includes(n) || r.includes(t);
+}, g = (e) => typeof e == "string" ? [e] : e, _ = (e, t) => {
+	for (let n of t) if (!h(e, n)) return n;
+	return null;
+}, v = (t, n) => {
+	let r = g(n), i = _(t.request.subject, r);
+	return i === null ? e.void : e.fail(new m({
+		required: i,
+		reason: `missing required permission '${i}'`
+	}));
+}, y = (t, n) => {
+	let r = t.request.subject;
+	if (n.length === 0) return e.void;
+	for (let t of n) if (h(r, t)) return e.void;
+	return e.fail(new m({
+		required: n[0],
+		reason: `missing all of required permissions [${n.join(", ")}]`
+	}));
+}, b = (e, t) => {
+	let n = _(e.request.subject, g(t));
+	if (n !== null) throw new m({
+		required: n,
+		reason: `missing required permission '${n}'`
+	});
+}, x = (e, t) => _(e.request.subject, g(t)) === null;
+//#endregion
+export { v as a, d as c, i as d, a as f, x as i, u as l, y as n, p as o, o as p, b as r, f as s, m as t, l as u };

package/dist/permission.d.ts

@@ -0,0 +1,78 @@
+import { Effect } from 'effect';
+import { Schema } from 'effect';
+import { Subject } from '@voltro/protocol';
+
+/**
+ * Effect-form OR guard. Passes if the caller holds AT LEAST ONE of the
+ * listed permissions. Fails `Forbidden` (naming the first option) when it
+ * holds none. The `admin:full` bypass passes.
+ *
+ * ```ts
+ * yield* anyPermission(ctx, ['notes:write', 'notes:admin'])
+ * ```
+ */
+export declare const anyPermission: (ctx: RbacContext, required: ReadonlyArray<string>) => Effect.Effect<void, Forbidden>;
+
+/**
+ * Sync-form guard for async (non-Effect) handlers. THROWS `Forbidden`
+ * when the caller lacks the required permission(s). Array = AND.
+ *
+ * ```ts
+ * const execute = async (input, ctx) => {
+ *   assertPermission(ctx, 'notes:write')
+ *   return ctx.store.insert('notes', { ... })
+ * }
+ * ```
+ */
+export declare const assertPermission: (ctx: RbacContext, required: string | ReadonlyArray<string>) => void;
+
+/** Pure boolean check — no throw, no Effect. For branching inside a handler. */
+export declare const can: (ctx: RbacContext, required: string | ReadonlyArray<string>) => boolean;
+
+/**
+ * Raised when a caller lacks a required permission. Distinct from
+ * protocol's `ScopeError` so rbac owns its own wire surface; `rbacPlugin`
+ * registers it via `errorSchemas` so it decodes TYPED on the client.
+ *
+ * Declare it in a mutation's `error:` schema (or rely on `rbacPlugin`'s
+ * cross-cutting registration) so callers can pattern-match on
+ * `_tag === 'Forbidden'`.
+ */
+export declare class Forbidden extends Forbidden_base {
+}
+
+declare const Forbidden_base: Schema.TaggedErrorClass<Forbidden, "Forbidden", {
+    readonly _tag: Schema.tag<"Forbidden">;
+} & {
+    /** The permission (or first missing permission) the caller lacked. */
+    required: typeof Schema.String;
+    /** Optional human-readable context. */
+    reason: Schema.optional<typeof Schema.String>;
+}>;
+
+/**
+ * Effect-form guard. Fails with a typed `Forbidden` on the error channel
+ * when the caller lacks the required permission(s). An array means ALL
+ * are required (AND). The `admin:full` bypass passes everything.
+ *
+ * ```ts
+ * export default (input, ctx) => Effect.gen(function* () {
+ *   yield* permission(ctx, 'notes:write')
+ *   // ...
+ * })
+ * ```
+ */
+export declare const permission: (ctx: RbacContext, required: string | ReadonlyArray<string>) => Effect.Effect<void, Forbidden>;
+
+/**
+ * Anything carrying a resolved subject under `ctx.request.subject` — the
+ * shape every handler executor receives (`AppContext`). Kept structural
+ * so rbac needs no dependency on @voltro/runtime.
+ */
+export declare interface RbacContext {
+    readonly request: {
+        readonly subject: Subject;
+    };
+}
+
+export { }

package/dist/permission.js

@@ -0,0 +1,2 @@
+import { a as e, i as t, n, r, t as i } from "./permission-1Z68oD-d.js";
+export { i as Forbidden, n as anyPermission, r as assertPermission, t as can, e as permission };

package/dist/web/index.d.ts

@@ -0,0 +1,46 @@
+import { Context } from 'react';
+import { Provider } from 'react';
+
+/** The blanket bypass scope — mirrors @voltro/protocol's ADMIN_SCOPE.
+ *  Re-declared here so the web subpath never imports the node-side
+ *  package root. */
+export declare const ADMIN_SCOPE = "admin:full";
+
+/** Pure OR check — passes if the set holds AT LEAST ONE of `required`. */
+export declare const canAnyFromScopes: (scopes: ReadonlyArray<string>, required: ReadonlyArray<string>) => boolean;
+
+/**
+ * Pure check against a known scope set. `required` as an array means ALL
+ * are required (AND). The `admin:full` bypass passes everything. Exposed
+ * so non-hook code (loaders, route guards) can branch on the same logic.
+ */
+export declare const canFromScopes: (scopes: ReadonlyArray<string>, required: string | ReadonlyArray<string>) => boolean;
+
+/**
+ * The resolved scope set the current caller holds, as the client knows
+ * it. Fed by the app's SubjectProvider (e.g. from `@voltro/plugin-auth`'s
+ * web `subjectContext`): wrap the tree in `<RbacScopeProvider scopes={...}>`
+ * sourced from the resolved subject.
+ */
+export declare const RbacScopeContext: Context<readonly string[]>;
+
+/** Provider for the caller's resolved scopes. */
+export declare const RbacScopeProvider: Provider<readonly string[]>;
+
+/**
+ * UI-only permission check. Reads the caller's resolved scopes from
+ * `RbacScopeContext` and returns whether they hold `required` (array =
+ * AND). For hiding affordances ONLY — the server `permission()` guard is
+ * the real authorization boundary.
+ *
+ * ```tsx
+ * const canEdit = useCan('notes:write')
+ * return canEdit ? <EditButton /> : null
+ * ```
+ */
+export declare const useCan: (required: string | ReadonlyArray<string>) => boolean;
+
+/** UI-only OR check — true if the caller holds at least one of `required`. */
+export declare const useCanAny: (required: ReadonlyArray<string>) => boolean;
+
+export { }

package/dist/web/index.js

@@ -0,0 +1,5 @@
+import { createContext as e, useContext as t } from "react";
+//#region src/web/index.ts
+var n = "admin:full", r = e([]), i = r.Provider, a = (e, t) => e.includes("admin:full") || e.includes(t), o = (e, t) => (typeof t == "string" ? [t] : t).every((t) => a(e, t)), s = (e, t) => t.length === 0 || t.some((t) => a(e, t)), c = (e) => o(t(r), e), l = (e) => s(t(r), e);
+//#endregion
+export { n as ADMIN_SCOPE, r as RbacScopeContext, i as RbacScopeProvider, s as canAnyFromScopes, o as canFromScopes, c as useCan, l as useCanAny };

package/package.json

@@ -0,0 +1,61 @@
+{
+  "name": "@voltro/plugin-rbac",
+  "version": "0.1.0",
+  "description": "Role-based access control — roles compile to scopes on top of @voltro/protocol's scope system. Ships rbacPlugin() (role→scope interceptor + typed Forbidden error), the permission()/assertPermission()/anyPermission() handler guards, the compileRoles() pure compiler, cross-dialect roles + userRoles tables, and a browser-safe useCan() UI affordance.",
+  "keywords": [
+    "voltro",
+    "typescript",
+    "framework"
+  ],
+  "license": "SEE LICENSE IN LICENSE",
+  "homepage": "https://voltro.dev",
+  "bugs": {
+    "email": "support@voltro.dev"
+  },
+  "author": {
+    "name": "Voltro UG",
+    "url": "https://voltro.dev"
+  },
+  "type": "module",
+  "exports": {
+    ".": {
+      "types": "./dist/index.d.ts",
+      "import": "./dist/index.js",
+      "default": "./dist/index.js"
+    },
+    "./web": {
+      "types": "./dist/web/index.d.ts",
+      "import": "./dist/web/index.js",
+      "default": "./dist/web/index.js"
+    },
+    "./errors": {
+      "types": "./dist/permission.d.ts",
+      "import": "./dist/permission.js",
+      "default": "./dist/permission.js"
+    }
+  },
+  "main": "./dist/index.js",
+  "module": "./dist/index.js",
+  "types": "./dist/index.d.ts",
+  "sideEffects": false,
+  "engines": {
+    "node": ">=24.0.0"
+  },
+  "dependencies": {
+    "@voltro/database": "0.1.0",
+    "@voltro/logger": "0.1.0",
+    "@voltro/protocol": "0.1.0"
+  },
+  "peerDependencies": {
+    "effect": "^3.21.4",
+    "react": "^19.0.0"
+  },
+  "peerDependenciesMeta": {
+    "react": {
+      "optional": true
+    }
+  },
+  "publishConfig": {
+    "access": "public"
+  }
+}