Core contracts and plugin SDK
Core contracts and plugin SDK
Section titled “Core contracts and plugin SDK”Elevator Pitch
Section titled “Elevator Pitch”Plugin authors use Core to declare portable features, data ownership and entitlement contracts.
Why & Value
Section titled “Why & Value”Pure contracts remain usable without Server, database drivers or browser UI. The trusted host supplies identity and actual execution capabilities. This MIT package owns its implementation and declarations in the public monorepo.
Key Highlights
Section titled “Key Highlights”- Pure plugin SDK
- Versioned data contracts
- Entitlement contracts
- Isolated test harness
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-coreimport { definePlugin } from '@alneas/eaos-core'
export const notes = definePlugin({ id: 'notes', entitlement: { tier: 'public' }, routes(router) { router.post<{ id: string }>('/read', async (ctx, input) => ctx.db.findOne('notes', input.id)) },})