@xyo-network/service-kit-aries
v0.2.2
Published
Configured public Aries datalake seeds for Service Kit
Keywords
Readme
@xyo-network/service-kit-aries
Creates an explicitly configured readonly Service Kit seed through the native Aries public datalake reader.
The current public release is 0.1.0, published October 1, 2026 and registry rechecked October 5. It depends on Aries datalake client ~0.2.0. Earlier native HTTP and packed/registry-consumer receipts remain version-specific; publication does not qualify current native/browser behavior, consumer adoption or hosted availability. See implementation status and the B3 contract.
The checkout declares Node ^26: SDK Protocol 8.0.1 confines the selected
graph to that major, and Aries datalake client 0.2.0 admits Node >=26.
Development/CI and current qualification use Node 26.9.0; other Node 26
versions require their own recorded qualification. This corrects the former
adapter Node >=18.17.1 declaration and root Node 24.14.1 pin. Published 0.1.0
metadata remains unchanged until release; older runtime receipts remain
historical. Browser outputs and the configured-reader contract are unchanged.
See implementation status for the current local packed gate and its limits.
import { createAriesDataLakeSeed } from '@xyo-network/service-kit-aries'
const seed = await createAriesDataLakeSeed({
id: 'public-control-lake',
endpoint: 'https://lake.example/v1/datalakes/dl_public',
endpointPolicy: 'public-https',
})The endpoint is the complete Aries datalake resource URL. The adapter derives its opaque native route ID; this is separate from a Service Kit locator's logical dataLakeId.
The adapter accepts no token, signer, headers, redirect policy, writer or discovered locator. Public endpoints require HTTPS. Use explicit-local only when the host has deliberately allowed a local HTTP deployment. The host still owns DNS, resolved-address, port, decompression and egress policy.
