@astrale-os/sdk 0.6.0-beta.58 → 0.6.0-beta.59
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -0,0 +1,6 @@
|
|
|
1
|
+
/**
|
|
2
|
+
* The Kernel's syscall references, without loading the Kernel Schema: `K` from `@astrale-os/sdk/schema`
|
|
3
|
+
* compiles the whole Kernel Schema when its module loads, which a Worker pays at startup.
|
|
4
|
+
*/
|
|
5
|
+
export type { FunctionRef, SyscallRef, } from '@astrale-os/kernel-core/schema/kernel/syscalls/references';
|
|
6
|
+
export { download, execution, function, identity, install, introspect, journal, mutate, query, register, uninstall, upload, view, } from '@astrale-os/kernel-core/schema/kernel/syscalls/references';
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
export { download, execution, function, identity, install, introspect, journal, mutate, query, register, uninstall, upload, view, } from '@astrale-os/kernel-core/schema/kernel/syscalls/references';
|
package/docs/requirements.md
CHANGED
|
@@ -58,6 +58,15 @@ A Role binding is `{ role, members?, granters? }` and names members, granters, o
|
|
|
58
58
|
the same Edge. Build refuses it on a dependency's Role with `A Core Identity of a dependency
|
|
59
59
|
holds only the Domain's own Roles.`
|
|
60
60
|
|
|
61
|
+
Who may install a binding depends on who owns the Role. Toward a Role the installed Domain owns,
|
|
62
|
+
the installer needs no authority over it. Toward a dependency's Role, a Kernel Role included, the
|
|
63
|
+
installer must be Root or hold `can_grant_extension` toward that exact Role, directly or through
|
|
64
|
+
its own compositions: holding the Role, or a bundle that contains it, is not enough. Since only an
|
|
65
|
+
installation writes `can_grant_extension`, an instance's administrators install such a Domain only
|
|
66
|
+
when a release installed under Root names them granters of those Roles, as a Shell release does for
|
|
67
|
+
its administrator profile. Otherwise the install is refused with `SCHEMA_REQUIREMENTS_UNSATISFIED`,
|
|
68
|
+
and its denials name each `extends_with` or `can_grant_extension` Edge the installer may not write.
|
|
69
|
+
|
|
61
70
|
A release binding is the only way a Domain composes Identities into Roles, its own included: the
|
|
62
71
|
Kernel DSL refuses a Core Edge whose Class is not the Domain's own (`DV_CORE_EDGE_CLASS`), and
|
|
63
72
|
Kernel `extends_with` is final. Bundles such as `member` extending `guest`, or a Team extending a
|
|
@@ -111,8 +120,8 @@ never both: `requirements({ roles, functions })` throws. Moving a Domain:
|
|
|
111
120
|
|
|
112
121
|
| Legacy | Roles and scopes |
|
|
113
122
|
| --- | --- |
|
|
114
|
-
| `functions: [f]` | `scopes: [{ on: f, operations: ['call'] }]`; for a protected Kernel callable
|
|
115
|
-
| `classes: [{ class: C, operations }]` | `scopes: [{ on: C, operations }]` |
|
|
123
|
+
| `functions: [f]` | for a callable of another Domain, `scopes: [{ on: f, operations: ['call'] }]`; for a protected Kernel callable, its Kernel Role and no scope, such as `{ role: K.core.nodes['graph.writer'], members: [requirements.domain] }` for `mutate`: a scope toward a Kernel target installs only under Root (A20) |
|
|
124
|
+
| `classes: [{ class: C, operations }]` | for a Class of another Domain, `scopes: [{ on: C, operations }]`; for a Kernel Class, the Kernel Role its Policy admits, such as `domain.reader` to read `K.classes.Class` |
|
|
116
125
|
| `core: [{ subject: s, ... }]` | a Role with the capabilities, and `{ role, members: [s] }` |
|
|
117
126
|
| `authority: { grant, revoke }` | `granters` of the Roles the Domain may grant |
|
|
118
127
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@astrale-os/sdk",
|
|
3
|
-
"version": "0.6.0-beta.
|
|
3
|
+
"version": "0.6.0-beta.59",
|
|
4
4
|
"description": "Schema-first SDK for defining, composing, and deploying Astrale domains",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"astrale",
|
|
@@ -56,6 +56,10 @@
|
|
|
56
56
|
"types": "./dist/platform/schema/addressing/index.d.ts",
|
|
57
57
|
"import": "./dist/platform/schema/addressing/index.js"
|
|
58
58
|
},
|
|
59
|
+
"./schema/references": {
|
|
60
|
+
"types": "./dist/platform/schema/references/index.d.ts",
|
|
61
|
+
"import": "./dist/platform/schema/references/index.js"
|
|
62
|
+
},
|
|
59
63
|
"./value": {
|
|
60
64
|
"types": "./dist/platform/value/index.d.ts",
|
|
61
65
|
"import": "./dist/platform/value/index.js"
|