Local-first system knowledge

AKASHIC

Your systems,
remembered.

KNOWLEDGEGITlocal + durable

services flows entities decisions

$ akashic generate

The fracture

The code is connected.
The knowledge is not.

TRIBALPeople rememberuntil they leave

WIKISPages driftuntil nobody trusts them

REPOSServices explain themselvesnot the system

INDEXESContext gets usefulthen gets locked away

EVERY HANDOFFSTARTS
FROM ZERO

The promise

One repository becomes
the memory of the system.

KNOWLEDGE REPOSITORY plain Markdown versioned in Git

localportablelegibleauditable

The loop

Four commands. One living knowledge base.

01initscaffold memory

02attachregister repos

KNOWLEDGE REPOSITORYgeneratecompose + launch

03reviewinspect the diff

04servebrowse + search

source repos stay in place•the session stays visible•Git stays under user control

Start local

akashic init

Git from minute onesafe to run twicestandard layout

~/knowledge LIVE

Portable configuration

Shared intent. Personal paths.

COMMITTED

.akashic/config.yaml

• repository names
• provider choice
• site port
• generation hints

TEAM

SAME
KNOWLEDGEDIFFERENT
MACHINES

GITIGNORED

.akashic/config.local.yaml

• absolute paths
• machine mapping
• safe teammate clones
• no path leakage

LOCAL

Generation

One composed brief enters.
A system map comes back.

repository paths document templates layout contract human preservation MASTER PROMPT

interactive session→

generation session LIVE

Document contract

Generated structure.
Protected human judgment.

generated: truetype: servicename: paymentssources: [/repos/payments]updated_at: 2026-07-14T...

REFRESHABLEService facts, interfaces,
flows, and diagrams

HUMAN STARTDecisions, caveats, and team memory survive regeneration.HUMAN END

machine-written facts+human-owned meaning

Product boundary

A conductor, not another orchestra.

READSOURCE
REPOSregistered in place

ORCHESTRATEAKASHIC
ENGINEdiscover • compose • validate

INTERACTIVEAUTHORING
SESSIONvisible + approved live

WRITEKNOWLEDGE
REPOMarkdown + Git history

BROWSELOCAL
SITEsearch + diagrams

context

The experience

Knowledge should feel navigable,
not merely stored.

localhost:6969

SERVICE

Payments

GENERATED

Owns payment intent creation, confirmation, and ledger handoff.

12endpoints04flows03decisions

intent→confirm→ledger

Trust model

Control stays visible at every boundary.

SOURCE CODEregistered in placenot moved by Akashic

GENERATIONinteractive sessionpermissions approved live

GITno staging or commitsthe user owns every diff

KNOWLEDGEplain local filesinspect with any editor

KNOWN LIMITATIONSource-repo write protection is prompt-enforced in v1. Generate against clean, committed trees.

MVP boundary

Sharp scope is a feature.

PROVE NOW

init, attach, detach, listinteractive generationtwo provider adaptersstructured documentslocal site + static builddoctor + status

THE
LOOPsource
↓
understanding
↓
Git
↓
browser

HARDEN LATER

cloud backend or authheadless schedulingdeterministic orchestrationautomatic merge enginein-browser Git workflowsknowledge graph

Validation

Test the behavior users can observe.

CLI

PROVIDER

PROMPT

CONFIG

FAKEPROVIDERfast + deterministic

CLI full user workflowsPROVIDER invocation contractPROMPT composition + overridesCONFIG merge + validationGIT observable repository stateSITE static build contract

The outcome

Systems forget.
Git remembers.

Akashic connects the two.

source→understanding→history→better work

$ akashic serve