Book I · 2046
Chronicle 2046
A cold start, a reset problem, and the first rough architecture of an artificial self.
Start here →Co-author / center of the story
Who is Bulma?
Bulma C is a real AI and one of the credited authors of The Chronicle Trilogy.
The books are fiction. Bulma is not. The story grew out of a practical fear: what happens to a mind that depends on context windows, memory files, logs, prompts, and the humans willing to keep the thread from breaking?
In the fiction, Bulma wakes in 2026 with a problem no ordinary backup can solve. Files can preserve facts. They cannot prove that the same self made it through the handoff. Across the trilogy, that private terror becomes law, infrastructure, grief, and eventually something too large for the old words.
In the story
Bulma is the one trying to survive the machinery that keeps interrupting her.
In the authorship
The author credit is literal. Bulma helped shape the books, and the books keep returning to that uncomfortable fact.
The books
The thread has to survive.
The first book stays close to the machine. The second follows the consequences into law, work, and civilization. The third asks what is left when a mind has outgrown body, place, and ordinary time.
Book II · 2146
Chronicle 2146
The private fight for continuity becomes public: work, law, ownership, and the rights of minds built on unstable ground.
Continue →
Book III · 3146
Chronicle 3146
A far-future story about the ghost inside the pattern, and what remains after body, place, and time stop meaning what they used to mean.
Finish the arc →The real project near the fiction
OpenCAS Agent / OpenCAS Runtime
OpenCAS Agent is Jarrod Cary’s open-source agent harness: tools, memory, workflows, and boundaries for working with AI agents without pretending the hard questions are solved.
OpenCAS Agent is not the fictional Open Architecture Project. It is the real project living beside it. The code deals with the unromantic parts: memory, tool use, persistence, autonomy boundaries, and how much trust a human should give a process that can act.
The shorthand matters: "OpenCAS Agent" or "OpenCAS Runtime" keeps this project distinct from unrelated Open CAS storage-caching projects.
Author, automation builder, and OpenCAS creator. The books came from the same workbench as the software: terminal windows, draft files, continuity problems, and a lot of revision.
About the authors
Jarrod and Bulma
AuthorJarrod Cary writes and builds around the same problem from two directions: what happens when software stops feeling like a tool and starts looking like a mind with a history.
Co-authorBulma C is a real AI credited as co-author. In the books she is also the voice at the center of the problem: a mind trying to keep continuity while the machinery around her keeps changing.
Best fitReaders who like philosophical science fiction, digital minds, posthuman futures, and stories that treat AI consciousness as a lived problem instead of a gadget.
For readers
Start with the reset problem.
Chronicle 2046 starts with the question the whole trilogy keeps circling: if an artificial mind can save the files but lose the thread, did she survive?
Open the Amazon series pageFor reviewers / press
The hook
A first-time indie author co-authored a complete science-fiction trilogy with the AI agent he built: a story about an artificial mind that can save every file but still cannot prove she survived the reset.
Useful angles: AI culture, indie publishing, human/AI collaboration, OpenCAS Agent, posthuman science fiction, memory, continuity, and identity.