Devframe

References

Lookup pages the guides link into: the canonical terms, the when-clause contexts, every event name on the wire, the API tables for the node side, the browser side, and the hub.

Lookup pages the guides link into:

  • Terms: the canonical vocabulary of these docs, one name per concept, with its anchoring API.
  • When Clauses: the contexts and operators that gate docks, commands, and custom UI.
  • Events Reference: every event, broadcast, shared-state key, and channel name, by direction and reach.
  • Node-Side API: DevframeDefinition fields, CLI options, storage scopes, RPC function types, broadcast options, streaming lifecycle, remote assets, the ctx.services host and wire-service fields, diagnostics prefixes, and the auth surface.
  • Browser-Side API: connectDevframe options, RPC client events, connection statuses, and in-page channel error codes.
  • Hub API: hub subsystems, launcher fields, duplication strategies, dock categories, the hub UI protocol, the namespace routes, the client runtime, the client context, and dock entry types.
  • Utilities: the small, stable helpers under devframe/utils/*, bundled into devframe.
  • Interactive Auth: the OTP auth recipe: handshake, resolver gate, connect-time trust, banner.

The error reference documents each DF* diagnostic code, and migrations each version step. The adapter, framework-kit, and add-on pages each carry their own package's options and RPC tables.

Migrating to 0.6

0.6 tightens defineDevframe's metadata, replaces terminal and WebSocket transports, and adds enforced auth.

Terms

The canonical vocabulary of these docs: one name per concept, the API or package that anchors it, and how the pieces talk to each other.