apache / maka
TypeScript  ·  GitHub Trending 23 Aug 2026  ·  49 stars today
Incubating  ·  local-first

Five kinds of event, written down and never revised.

The description names exactly what the workspace records and then names the property that matters more than any of it: the log only ever grows. What an agent did is a fact you can go back to, rather than a state you have to trust.

$ git clone apache/maka
github.com/apache/maka
The recorded eventsNames as published
seqentrykind
001model messagesrecorded
002tool callsrecorded
003tool resultsrecorded
004permission decisionsrecorded
005termination eventsrecorded
> 006 appends here append-only
×no edit in place
×no delete

Permission decisions are entries

Most systems treat an approval as a gate and then forget it happened. Filing it in the same log as the tool call is what makes a run reconstructable afterwards.

Termination is an event

How a run ended is recorded next to what it did. That is the line most agent traces are missing when you go looking for why something stopped.

What is not on this page

No schema, no format, no retention window, no throughput. The trending description publishes five event names and one property, so that is all the ledger carries.

Concept mock, not affiliated with the project. Every entry in the ledger is quoted from the repository's own GitHub Trending description on 23 August 2026: "Apache Maka (Incubating) is a local-first AI agent workspace. Model messages, tool calls, tool results, permission decisions, and termination events are recorded as an append-only log." Sequence numbers are positional only; no sample run, timestamp, or payload is represented here.