@hivecast/capabilities-console (1.1.33)
Installation
@hivecast:registry=npm install @hivecast/capabilities-console@1.1.33"@hivecast/capabilities-console": "1.1.33"About this package
Capabilities Console
Who may do what in a home: every grant, and a check of whether a principal can reach a subject
with a capability. Ownership satisfies namespace capability checks; a service may also enforce its own authorization. Built from the Console kit (@open-matrix/dashboard-components/console); design in
docs/architecture/target-v3/APPLICATION-LIFECYCLE-AND-PLATFORM-SURFACES-DESIGN.md §13.
Work on it live
Can I use this? is a separately addressable hivecast-capability-access-panel whose forms and actions remain discoverable through the Console. It lists services from the selected home's live Registry and operations from the selected service's live $introspect.accepts. Picking an operation reads capability.explain: ownership, an active grant and its grantor, the owner and grant needed, undisclosed/missing services, and handler-owned or dynamic authorization all get sentences.
When a grant is needed, Ask the owner for access explains the notification and Approve/Deny outcome before sending capability.access.request. The explanation rereads the caller's persisted request state. The shell bell delivers decisions; its notification changes also invalidate this view. No refresh button or typed identifiers are needed.
Only verified owners see People can ask for this. Its state comes from capability.access.list; turning it on/off calls capability.access.publish and rereads the list. Turning it on discloses the operation and required capability without granting access. Turning it off hides new requests without revoking grants or cancelling pending requests. Operations without a fixed declared scope cannot be newly published.
Can this person use it? checks people and capabilities already named by grants in the home, using the same sentence style. It does not infer ownership from the current profile. Every action rereads service state through the shared Console lifecycle. pnpm test covers selection validation, all explanation reasons, request status, owner controls and browser module packaging. The coordinator performs the deployed browser check.
pnpm install
hivedock up # in this folder: it opens from the Start menu, and a saved edit shows without a reload
pnpm test
Application presentation
The application uses the shared @open-matrix/hivecast-brand/application-header
header with its name, description and icon from matrix.package.json. Existing
application actions keep their handlers; Console primary forms remain available
through console.submit. Colours, typography and layout tokens inherit the
ui-kit theme in both light and dark mode. New styles use --mx-* tokens;
pnpm check:application-styles prevents growth of remaining literal styles.
Dependencies
Dependencies
| ID | Version |
|---|---|
| @open-matrix/contracts | 1.1.33 |
| @open-matrix/core | 1.1.33 |
| @open-matrix/dashboard-components | 1.1.33 |
Development Dependencies
| ID | Version |
|---|---|
| @open-matrix/hive-pm | 1.1.33 |
| @types/node | ^25.0.10 |
| esbuild | ^0.27.3 |
| tsx | ^4.15.6 |
| typescript | ^5.7.0 |
| vite | ^6.0.0 |