@volter/teams
v0.2.3
Published
Volter Teams, the neutral team plane: machine identity and daemon core, the local door and server link, admission from machine grants, product doors, and the Teams server's neutral routes (company RFC 0008).
Readme
@volter/teams
Volter Teams, the neutral team plane (company RFC 0008): what any product needs to be reached by a team, with no harness in it.
- The machine daemon's core (
machine-core.mjs): this OS user's machine identity and hash-chained account log, the owner-only local door, one outbound link to a Teams server with every stream admitted from the machine's own synced grants, and product doors. A product builds onMachineCoreand registers its own doors by stream name; the harness does (@volter/supercode-teams,machine.mjs). - Products behind the daemon (
products.mjs): a product serving its own kind of target writes a receipt; the daemon admits the caller, both sides prove the receipt's token without sending it, and messages are relayed. - Admission (
admission.mjs): grants of capabilities on targets,<kind>:*wildcards,*for operate and view only. - The Teams server's neutral routes (
server/): identity and sign-in, teams, members, groups, credentials, invitations, machines, enrollment and machine grants, the machine link, and the migration chain. The harness's routes attach throughapi.harnessRoutes.
This package is private: nothing is published while nothing is open-sourced.
Public Node clients are @volter/teams/http-client (TeamsClient),
@volter/teams/event-client (selected-context event client), and
@volter/teams/machine-door (an admitted local/remote machine channel).
Context credentials remain inside the custody adapter; consumers use its public client.
