@asyra/core
v0.5.7
Published
Public composition core for canvas-based, visual, and domain-driven Asyra products
Maintainers
Readme
@asyra/core
Strict public composition facade and lifecycle coordinator for current Asyra Framework capabilities.
Requirements
- Node.js 24.x
- Yarn 4.3.1 for this repository's maintained workflows
Install
npm install @asyra/coreimport core from '@asyra/core'Use only the package root and the explicitly documented public subpaths.
Owns
- composition closure, startup ordering, readiness, teardown, load coordination, and curated package facades
- one pre-start render-engine provider and engine-neutral default adapter
Does not own
- App-domain rules, UI presentation, concrete engine resources, backend policy, permissions, or the future Core Kernel
Start here
Use Core for supported App composition and extensions that cross canonical package owners. Register composition before the first core.start(...).
Read the Core App implementation guide before building: it connects transaction publications, incremental persistence, scoped subscriptions, computation reuse and lifecycle. Working Undo alone does not establish complete integration.
Lifecycle and composition
Startup validates and closes composition, initializes required runtime owners, loads canonical data, and publishes ready only after success. App-owned migrations form one connected migration chain; an unmatched string version passes through to ordinary owner validation. A failure tears down owned work and never reports false readiness. The current no-provider compatibility branch is not a public Headless lifecycle.
Learn more
Support and policy
GitHub Discussions is the intended public channel for community conversation and general help. Discussions is not enabled for this repository yet, so there is currently no public community support destination. GitHub Issues are not a general public support channel. External pull requests are not accepted by default. Community participation creates no SLA or response deadline.
You may use, inspect, and fork the package under the MIT License. Read the support policy. For suspected vulnerabilities, follow the security policy and report privately.
