🌌 Akasa: Application Kernel & Volume Router
Akasa (Sanskrit for Ether / Substrate / Space) is a local-first, event-sourced Python micro-kernel.
Extracted from the inSetu Developer OS, Akasa acts as the foundational substrate for multi-tenant, offline-first Python applications. It is strictly domain-agnostic: it knows nothing about your application's business logic, acting purely as a high-performance routing and synchronization engine.
✨ Core Mechanics
- The Volume Router (VFS): An asynchronous, non-blocking Virtual File System. It abstracts physical disk I/O behind a strict Mount Table, allowing host applications to mount sandboxed repositories and virtual domains to unified URIs (e.g.,
vfs://orctx://). - Stateless Multi-Tenancy: All databases, caches, and file resolutions are scoped to an active
workspace_id, allowing a single daemon process to serve multiple isolated tenant environments safely. - The Typed Event Bus: A synchronous/asynchronous
HookRegistryenforcing strict authorization boundaries for inter-module communication. - The Metronome (Worker Engine): A background SQLite-backed job ledger (
jobsandimmediate_jobs) providing distributed, dependency-driven task execution and UI telemetry without blocking the main event loop. - SQLite WAL Connection Pooling: Thread-local, auto-evicting database connection pooling explicitly optimized for Write-Ahead Logging concurrency.
🏗️ Architecture Mandate
Akasa adheres to the Blind Substrate Mandate.
- Zero Domain Logic: Akasa does not parse target repositories, compile RAG contexts, or understand Git diffs. It only provides the tools to store and route them.
- Inversion of Control: All application-specific behavior is injected into Akasa by the host application via
@hooks.on()subscriptions, Driver registrations, and Volume mounts.
🚀 Installation
Akasa is designed to be installed as a foundational dependency for your host application.
pip install akasa
Metadata
Release files for akasa 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| akasa-0.2.0.tar.gz | 35.2 kB | Without provenance | Details for akasa-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| akasa-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for akasa-0.2.0-py3-none-any.whl |
Total release size: 73.4 kB
Release files / akasa-0.2.0.tar.gz
| Download URL | akasa-0.2.0.tar.gz |
|---|---|
| Size | 35.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
504859bf447e92320aae00017805b450784cc52a7e45bca9e4dc3b738ed832b0
|
|
BLAKE2b-256 checksum How to use checksums |
c4c2401797b524227a302213dceda079eba4250bdf3ca6e9b191435e56856d4f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / akasa-0.2.0-py3-none-any.whl
| Download URL | akasa-0.2.0-py3-none-any.whl |
|---|---|
| Size | 38.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0afce807614331e03692a82c12b5f2c44e3125a0cdaca57a84a40ccf558c058a
|
|
BLAKE2b-256 checksum How to use checksums |
576a59c02e6e36f59db6d4a41951bce880ac2748f833787facd8fd9868534efa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for akasa 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.