Skip to main content

Planned / Deferred RFCs

These RFCs are not realised by v0.1.0, or are realised only in part. They describe the intended direction of the framework.

:::caution Design, not commitment The items below are documented design and architectural direction. They are not roadmap guarantees, dates, or promises. Treat them as "where the architecture points", not "what will ship when". :::

RFC-003 — Tenancy​

Designs a dedicated row-level tenancy driver and tenant-resolution model.

v0.1.0 state — partial. Tenant scoping exists — every entity is tenant-scoped and the SQLite driver enforces tenant boundaries (see SQL Persistence). What is not in v0.1.0 is the dedicated ausus/tenancy-row driver package; that name is reserved and ships no code. There is no multi-tenant runtime — an Invoker is bound to a single tenant.

RFC-007 (dedicated audit package) — Audit database​

RFC-007 itself is implemented in subset — the audit trail works. What is deferred is the dedicated ausus/audit-database package: a standalone audit driver separate from persistence-sql. That name is reserved and ships no code in v0.1.0.

RFC-010 — Reporting & maintenance​

Designs a reporting/query subsystem and maintenance-class operations (ReportingDriver, maintenance-class invocations).

v0.1.0 state — not implemented. There is no reporting driver. The kernel distinguishes a Maintenance invocation class in the audit record, but no reporting or maintenance subsystem ships.

RFC-014 — Authorization​

Designs the full authorization model — actor resolution, an authentication bridge, and richer policy composition.

v0.1.0 state — partial. The Actor / ActorRef contracts exist in the kernel, and StubActor provides a fixed in-memory actor. What is not in v0.1.0: any authentication, actor resolution from credentials, or the ausus/auth-bridge package (reserved, no code). Anything exposing the runtime must supply its own authentication — see The HTTP API.

Reserved packages summary​

Four package names are reserved in v0.1.0 and tied to the RFCs above:

PackageRFCStatus
ausus/tenancy-rowRFC-003reserved name, no code
ausus/audit-databaseRFC-007reserved name, no code
ausus/auth-bridgeRFC-014reserved name, no code
ausus/presentation-defaultpresentation (L5)reserved name, no code

See Packages for the full catalogue.

Other deferred items​

Not tied to a single RFC, but documented as deferred from v0.1.0:

  • MySQL / PostgreSQL persistence drivers — the SQL design allows for them; only SQLite is implemented and validated.
  • Supply-chain attestation — npm provenance, GPG-signed tags, and an SBOM are deferred to v0.2.0 (see Package Integrity).
  • DSL enrichments — convention-resolved policy/effect classes, field-level visibility, DSL diagnostics (RFC-011 deferred surface).