The journal remembers
An append-only log of every change. The changelog, the history and the deliverables are all read from it.
Fields tell you what is true now. They can't tell you when it became true, or what it used to be. So Arkaik keeps a journal: an append-only log where every change to the graph lands as an event, and nothing is ever rewritten.
From that single log, everything historical is derived. The changelog, split into Design (what you decided and drew) and Delivery (what actually shipped). The history page, to scroll back through a project's life. Milestones, drawn as timelines of the events they gathered.
Pull requests leave a trace too: a deliverable records what a PR touched and where it shipped, so a changelog card can say "this screen, on iOS, via that merge" instead of a bare line.
Because the past is derived rather than typed in, it can't drift. If the journal says it happened, it happened, and that's what makes the rest of the graph trustworthy.
Journal
- Pull request deliverablesMilestone
- Milestones as timelinesMilestone
- Design and Delivery splitMilestone
- The journal landsMilestone