Server execution and persistence
Server execution and persistence
Section titled “Server execution and persistence”Elevator Pitch
Section titled “Elevator Pitch”Host developers use Server to compose HTTP/MCP, lifecycle and durable data services.
Why & Value
Section titled “Why & Value”Shared implementations keep authorization, CAS, audit and Outbox consistent. The host retains provider connections, current identity and deployment policy. This MIT package owns its implementation and declarations in the public monorepo.
Key Highlights
Section titled “Key Highlights”- Hono and MCP integration
- Reviewed lifecycle plans
- Durable CAS and audit
- Scoped database and storage
Quickstart
Section titled “Quickstart”Registry installation requires a published release. During pre-publication development, install the checksum-pinned tarballs produced by the workspace build instead of assuming these names exist in a registry.
Public import
Section titled “Public import”Install the owning package and use the exact import in the example below. The subpath is not a separate npm package. Check the selected entry’s runtime and peer requirements in the linked architecture guide.
bun add @alneas/eaos-serverimport { canonical } from '@alneas/eaos-server/lifecycle-engine'
console.log(canonical({ format: 1, operation: 'inspect' }))