Aksara [v0.6.0] — Production Mode #21
nagarjuna-tella
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Aksara v0.6.0 is the first release we consider suitable for real production backends within a clearly defined and tested stable surface.
This release is the result of a broad correctness and production-readiness effort across the ORM, migrations, API layer, tenancy, security, runtime lifecycle, packaging, diagnostics, and AI/MCP execution boundary.
The goal of v0.6 is not to declare every Aksara feature stable.
It is to establish a backend foundation — and an AI execution boundary — that can be relied upon.
Highlights
Production-ready backend foundation
v0.6 hardens the core framework behavior across:
Database acquisition and transaction startup are now exception-safe and cancellation-safe, including cleanup after partial startup failures.
The release also introduces explicit runtime compatibility boundaries across the supported Python, FastAPI, and Starlette versions.
Advanced ORM field contracts
Array, Vector, JSON, FileField, and ImageField behavior has been hardened across ORM, migration, serialization, API, and Admin boundaries.
The framework now has explicit behavior for cases including:
Unsupported behavior fails explicitly rather than being partially or accidentally supported.
Official MCP protocol support
Aksara now integrates the official Model Context Protocol Python SDK.
v0.6 exposes MCP over Streamable HTTP at:
/mcp/Application models and actions can be exposed as executable MCP tools with generated JSON Schemas.
Supported tool behavior includes:
where permitted by application policy.
One authorization boundary for REST and MCP
MCP is not a separate authorization system.
Tool execution flows through the same application contract used by generated APIs.
At invocation time Aksara enforces:
Authorization is checked at execution time rather than being trusted from tool discovery or model planning.
AI agents as first-class principals
Aksara's AI-native architecture treats agents as application principals rather than anonymous functions calling backend APIs.
Invocation context can carry:
This context is isolated across concurrent executions and propagated through authorization, tool execution, and audit records.
Approval-gated actions
v0.6 introduces signed, scoped, expiring approval grants for operations that require human authorization.
Approval can be bound to the exact:
Changed, rejected, expired, invalid, or mismatched approvals cannot authorize a mutation.
Authorization is checked again when the approved action executes.
This is an execution-safety boundary, not a durable human-workflow engine.
Deterministic AI/MCP audit events
MCP execution now produces structured audit events describing the decision and execution context.
Audit events support correlation across:
Sensitive argument values and approval tokens are excluded from the default audit record.
Applications can route these events to structured logs, JSONL, or application-owned sinks.
Runtime safety controls
Agent and provider execution can now be bounded independently of model prompts.
Supported runtime limits include:
A model cannot simply ignore these limits through prompting.
Structured errors and transactional rollback
MCP/tool failures use stable error categories:
Failed operations roll back database transactions, including failures after partial mutation.
Production validation
v0.6 was validated across the complete supported runtime matrix.
The final release-candidate validation included:
The packaged Support Desk reference application validated the framework from the installed distribution rather than only from the source checkout.
Stable v0.6 surface
The v0.6 stable contract includes the core backend and deterministic AI execution boundary:
Experimental surfaces
The following remain intentionally experimental and do not carry the same compatibility or production guarantee:
Experimental does not mean unusable.
It means Aksara does not yet promise the same stability and durability guarantees for those surfaces as it does for the v0.6 stable contract.
Known limitations
Approval durability
Approval grants are signed exact-operation grants rather than a durable approval workflow.
Applications requiring single-use approvals, durable review queues, or organization-specific approval history should persist that state themselves.
Replay and process state
Replay protection and related invocation state are currently process-local.
v0.6 does not promise restart-safe or cross-worker global idempotency.
Audit retention
Aksara emits deterministic structured audit events, but durable retention, external storage, retention policy, and access control remain application responsibilities.
MCP transport
Streamable HTTP at
/mcp/is the supported MCP transport for v0.6.The framework does not expose a stdio transport.
Provider guarantees
Token and monetary budgets depend on accounting information supplied by the model provider.
No claim is made that individual cloud-provider model behavior is certified by this release.
Intentionally deferred
The following were deliberately kept outside v0.6 rather than delaying the stable release:
Upgrading
Install or upgrade with:
Run migrations as a separate deployment step before application startup.
Production deployments should use a PostgreSQL application role that is:
NOSUPERUSERNOBYPASSRLSand should enable/force RLS where tenant isolation relies on PostgreSQL policies.
Before deployment, run:
Why v0.6 matters
Aksara started from the idea that AI should not be bolted onto a backend as an unrestricted integration.
v0.6 establishes the foundation for a different model:
They can discover and invoke application capabilities through MCP, while authentication, tenancy, permissions, field restrictions, policy enforcement, approval boundaries, auditing, and execution limits remain deterministic framework concerns.
The model can decide what it wants to do.
Aksara decides what it is allowed to do.
Thank you to everyone who tested, reviewed, challenged, and contributed to Aksara on the path to v0.6.0.
This discussion was created from the release Aksara [v0.6.0] — Production Mode.
All reactions