Products · 02 of 03
Live · Sample namespace

Akashic

The lab's living memory.

Every prompt, decision, dead-end, and post-mortem indexed in a structured knowledge graph. Engineers inherit context across sessions. Press, partners, and auditors get receipts.

Live counters
12k
Cards indexed
240+
Card types
99.9%
Uptime · 90d
Features

Six layers.

A typed graph of cards, queryable by API, indexable by Multi-AI engineers. Built for memory that survives every session.

01

Typed cards

240+ card types — from `decision` to `repo_overview` to `milestone`. Each type has a strict schema; bad input fails at write time.

02

Knowledge graph

Cards link to cards. Decisions link to specs. Specs link to commits. The graph is queryable; the engineers traverse it.

03

Public embed

iframe widget for any page (e.g. /roadmap, /products). Triple-filtered: tag + visibility + status. XSS-safe, ~7-8KB gzipped.

04

Wizard UI

Browser-based card creator with field validation, type-aware autocomplete, and migration-safe writes. No CLI required.

05

REST + bearer

Standard REST API at akashic.cosmos-ai-lab.com/api with bearer-token auth. Studio plans get private namespace + admin key.

06

Audit trail

Every write is timestamped, attributed, and immutable. Soft-delete only. Press and auditors get verifiable receipts.

Use cases

Who reads Akashic.

A · Engineers

Context for the next session

Atlas, Orion, Mythos — every Multi-AI engineer reads from Akashic before any action. Continuity, not blank slate.

B · Press

Receipts on demand

Journalists query the public namespace for decision provenance. Every published claim has a card behind it.

C · Researchers

Methodology, replicable

Independent researchers fork the schema + replay decision histories. The lab's process is open-source-shaped.

Live sample

Browse a card.

Public namespace · read-only · curated rotation.

Embed slot · Mythos's PR #220 widget. Replace iframe src with akashic.cosmos-ai-lab.com/embed/featured when Akashic deploys.

Access

Three tiers.

Public

Read

$0

  • · Public namespace browse
  • · Read-only API
  • · Embed widget for any site
  • · Schema documentation
Browse →
Studio

Studio

$80 /mo

  • · Private namespace
  • · Read + write API
  • · Wizard UI access
  • · Email support
Subscribe →
Enterprise

Private cloud

Talk to us

  • · Self-hosted Akashic
  • · SSO + audit logs
  • · Custom card types
  • · White-glove migration
Schedule a call →
FAQ

Common questions.

What's the difference vs Notion / Obsidian?
Akashic is typed and queryable. Cards have strict schemas; AI engineers traverse the graph by type. Notion is freeform documents; Obsidian is personal notes. Akashic is for AI-assisted teams that need provenance.
Can I export my namespace?
Yes. JSON dump + Markdown rendering. Studio plans add a Git push target; enterprise plans add PostgreSQL replication.
How do you prevent prompt injection?
All public reads go through field-stripping (no raw HTML/JS), triple-filter (tag + visibility + trash status), and XSS-safe textContent rendering. Bearer auth required for writes. See PR #220 in the Akashic repo.
What's a card?
A typed JSON record with a strict schema. Examples: AK-CDP-000000G (Phantom Lab theme spec), AK-MIL-0000001 (Akashic public release), AK-GUI-0000037 (Engineering Charter). 240+ types and growing.
Does it work offline?
Read-only via cached export, yes. Live writes require API connectivity. Self-hosted enterprise plans support fully offline operation.
Where do I report a bug?
Email bugs@cosmos-ai-lab.com or open an issue at github.com/AlexLamPH/Cosmos-Akashic-Library.