Release Notes — v0.1.0
Release type: initial public release (release candidate).
This is the first public release of AUSUS. It is suitable for evaluation, prototypes, and learning the model. Public contracts are still stabilizing and may change before v1.0.
What ships
- 4 implemented PHP libraries —
ausus/kernel,ausus/persistence-sql,ausus/runtime-default,ausus/api-http. - 1 project template —
ausus/starter. - 1 metapackage —
ausus/standard-stack(pins the validated v0.1.0 set). - 4 reserved package names —
ausus/tenancy-row,ausus/audit-database,ausus/auth-bridge,ausus/presentation-default. Name reservations only — no source code in v0.1.0. - 1 npm package —
@ausus/renderer-react.
All 11 publishable packages are at version 0.1.0 (10 Composer + 1 npm). See
the full Package Catalog.
Compatibility matrix
| Layer | Tool | Minimum | Tested with |
|---|---|---|---|
| Runtime (PHP) | php | 8.3 | 8.4.18 |
| Runtime (PHP) | ext-pdo, ext-pdo_sqlite | bundled | bundled |
| Tooling (PHP) | composer | 2.0 | 2.9.5 |
| Runtime (JS) | node | 18 | 22.x |
| Runtime (JS) | react, react-dom | ^18 || ^19 | 18.3.1 |
| Tooling (JS) | npm | 8 | 10.x |
| Tooling (JS) | typescript (dev) | 5.4 | 5.x |
Explicit non-dependencies — none of these are required: the Laravel framework, Eloquent, Filament, Tailwind, any UI component library, Vite, Webpack, Babel.
Known limitations
| Area | v0.1.0 state |
|---|---|
| Reserved packages | tenancy-row, audit-database, auth-bridge, presentation-default ship no code |
| Persistence | validated on SQLite only; MySQL/PostgreSQL designed-for, not validated |
| Runtime | single-process, single-tenant, single-actor per Invoker; no distributed runtime |
| Authentication | none — StubActor only; no auth bridge |
| Renderer | no built-in router, theme tokens, optimistic UI, or CSS file |
| Projections | no filtering, sorting, or real pagination |
| Validation | field unique/max recorded in the graph but not enforced at runtime |
| Supply chain | npm provenance, GPG-signed tags, and SBOM are deferred to v0.2.0 |
See each area's page for detail — Runtime, SQL Persistence, React renderer, Projections.
Reproducibility
The release candidate is validated by in-repo gates, each re-runnable from a clean checkout:
| Gate | Result |
|---|---|
composer validate — 11 manifests (root + 10 packages) | pass |
bash scripts/ci.sh | pass — ends [ci] DONE — all 10 steps passed |
bash scripts/clean-room.sh | pass — 8/8 isolated steps |
bash scripts/integration-http.sh | pass — 12/12 live-HTTP assertions |
php apps/playground/run.php | pass — 36/36 assertions |
npm run build && npm run trace | pass — 12/12 render assertions |
Publication
Publication of v0.1.0 to Packagist and npm follows a controlled, phase-gated procedure. The operator-facing detail lives in the Publication Runbook and the dry-run results in the Release Rehearsal. Those documents — not these release notes — are authoritative for the publication process.
Looking ahead — v0.2.0
Items explicitly deferred from v0.1.0 (not commitments, but the documented direction):
- Implementations for the four reserved packages.
- MySQL / PostgreSQL persistence drivers.
- Supply-chain attestation (npm provenance, signed tags, SBOM).
See Planned RFCs for the architectural backlog.