Modules§
- interaction_
flow - Canonical Interaction Flow definition and Core-to-Node wire contract.
- llm
- messaging
- node
Structs§
- Artifact
Delivery Projection Request - Artifact
Delivery Projection Response - Artifact
Upload Projection Request - Artifact
Upload Projection Response - Auth
Config - Auth
Request - Authenticated
Session - Cleanup
WsState Request - Client
Ids - Complete
External Core Events Request - Complete
External Core Events Response - Endpoint
Payload Request - Error
Response - External
Artifact Read Descriptor - External
Artifact Request Context - External
Artifact Upload Descriptor - External
Authorize Artifact Read Request - External
Authorize Artifact Upload Request - External
Commit Artifact Upload Request - External
Core Device Identity - External
Core Error - External
Core Event - External
Core Event Completion - External
Core Health - External
Core Mdns Record - External
Core Request - External
Core Response - External
Core Runtime Metadata - External
Host Runtime Request - A platform capability request emitted by an externally hosted Core.
- External
Open Artifact Request - External
PutArtifact Request - External
Service AppFacade Request - An App Facade request delegated by an externally hosted Core to the application service that owns the target’s business logic.
- Handle
Core Input Request - Handle
Core Input Response - Host
Delivery Request - Http
Payload Request - HubConnection
Proof Request - HubConnection
Proof Response - HubMdns
Instance Record - List
Mdns Records Request - Messaging
Delivery Request - Messaging-only Core -> Host request. A successful response means delivery was accepted by the provider implementation, not merely queued in the Core event pump or read by a user.
- Messaging
Delivery Response - MwsClient
Info - MwsMessage
- MwsMessage
Type - MwsSource
- Node
Auth Request - Node
Auth Response - Node
Challenge Evidence - Node
Challenge Payload - Node
Commissioning Accept Request - Node
Commissioning Accept Response - Node
Commissioning Error Response - Node
Commissioning Prepare Request - Node
Commissioning Prepare Response - Node
Commissioning Status Request - Node
Commissioning Status Response - Node
Describe Request - Node
Description - Node
Instance List Item - Node
Instance List Response - Node
Onboarding Start Request - Node
Onboarding Start Response - Node
Preflight Error - Node
Preflight Readiness - Node
Readiness Reason - Node
Readiness Request - Node
Readiness Snapshot - Node
Token Issue Request - Node
Token Issue Response - Node
Token List Item - Node
Token List Response - Node
Token Revoke Request - Node
Token Revoke Response - Poll
External Core Events Request - Poll
External Core Events Response - Recipient
Id - Recipient
IdError - Register
Local AppClient Request - Register
Node Connection Request - Scope
Authorization Request - Scope
Info - Scope
Member - Scope
Membership - Scope
Membership List Request - Scope
Owned Data Purge Request - Service
AppClient Projection - A service-owned AppClient materialized from an authoritative external model. This boundary intentionally carries no acting user: authorization belongs to the service that owns the source model, while Core validates the projection.
- Service
AppClient Projection Key - Service
Core Output - Storage
Create Namespace Request - Storage
Namespace - Storage
Namespace IdRequest - Storage
Namespace List - Storage
Namespace Update - Storage
Object - Storage
Object List - Storage
Repository Settings - Storage
Repository Settings Update - Storage
Repository Stats - Storage
Session - Storage
Session Request - Unsupported
Storage Overflow Strategy - Update
Callback Base Request - User
Info - User
Setting
Enums§
- Delivery
Acceptance - Delivery
Outcome - Exception
Code - External
Core Event Kind - External
Core Method - External
Host Runtime Method - Host
Connection Control - Connection fencing is control, not delivery. The key must identify an exact session, so delayed control requests cannot close a replacement connection.
- Host
Delivery Destination - Node
Binding Status - Node
Instance Policy - Node
Preflight State - Node
Readiness State - Scope
Access Requirement - Service
Core Input - Service
Core Response - Storage
Overflow Strategy - Storage
Permission - Storage
Write State
Constants§
- ARTIFACT_
CONTENT_ PATH_ PREFIX - ARTIFACT_
UPLOAD_ PATH_ PREFIX - EXTERNAL_
CORE_ PROTOCOL_ VERSION - HUB_
CONNECTION_ PROOF_ PROTOCOL - HUB_
CONNECTION_ PROOF_ TARGET - MWS_
MAX_ FRAME_ SIZE - MWS_
MAX_ MESSAGE_ SIZE - Shared MWS transport limits. Both websocket peers must apply these values so an envelope accepted by one side is never rejected solely due to asymmetric transport configuration.
- MWS_
MAX_ WRITE_ BUFFER_ SIZE - NODE_
DESCRIBE_ SCHEMA_ VERSION - NODE_
ONBOARDING_ CHALLENGE_ ALGORITHM - NODE_
ONBOARDING_ CHALLENGE_ AUDIENCE - NODE_
ONBOARDING_ CHALLENGE_ PROTOCOL - NODE_
ONBOARDING_ ES256_ ALGORITHM - NODE_
ONBOARDING_ START_ TARGET - NODE_
ONBOARDING_ TOKEN_ AUDIENCE - NODE_
ONBOARDING_ TOKEN_ ISSUER_ PREFIX - NODE_
ONBOARDING_ TRANSACTION_ TTL_ SECONDS - NODE_
PREFLIGHT_ SCHEMA_ VERSION - NODE_
READINESS_ SCHEMA_ VERSION - NODE_
SERVICE_ PROTOCOL_ V1_ SCHEMA - NODE_
TOKEN_ ISSUE_ TARGET - NODE_
TOKEN_ LIST_ TARGET - NODE_
TOKEN_ REVOKE_ TARGET - STORAGE_
CREATE_ NAMESPACE_ ROUTE - STORAGE_
DESCRIBE_ ROUTE - STORAGE_
ISSUE_ SESSION_ ROUTE - STORAGE_
LIST_ NAMESPACES_ ROUTE - STORAGE_
NAMESPACE_ STATUS_ ROUTE - STORAGE_
NODE_ TYPE - STORAGE_
PROTOCOL_ VERSION - STORAGE_
READINESS_ ROUTE - STORAGE_
STATS_ ROUTE - STORAGE_
UPDATE_ NAMESPACE_ ROUTE - STORAGE_
UPDATE_ SETTINGS_ ROUTE
Functions§
- hub_
connection_ proof_ signing_ payload - Canonical, domain-separated bytes signed by the Hub for one physical WS connection. Length prefixes keep the encoding unambiguous without relying on JSON object ordering.
- node_
describe_ target - node_
readiness_ target