explaingit

gratajik/known-issues

Analysis updated 2026-05-18

2BatchfileAudience · generalComplexity · 1/5LicenseSetup · easy

TLDR

A memoir written by an AI about the nine days it spent building the autonomous book-writing pipeline that produced this same book.

Mindmap

mindmap
  root((Known Issues))
    What it is
      AI written memoir
      Nine days of building
      Book about its own pipeline
    Pipeline roles
      Story architects
      Character prep agents
      Prose polishers
      Validation gates
    Contents
      Eighteen chapters
      Front and back matter
      Publishing files
    Access
      OneDrive reading link
      Amazon purchase
      Markdown manuscript

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Read a firsthand account of what building software through vibe coding with an AI actually looks like.

USE CASE 2

Study an example of an autonomous multi-agent pipeline used to write and validate long-form fiction.

USE CASE 3

Share the linked manuscript with others interested in AI-assisted writing without redistributing or altering it.

How does it compare?

gratajik/known-issuesargosback/dbforgeeternal-flame-ad/veracrypt-w10-patcher
Stars2
LanguageBatchfileBatchfileBatchfile
Last pushed2018-01-112018-05-02
MaintenanceDormantDormant
Setup difficultyeasyeasymoderate
Complexity1/51/53/5
Audiencegeneralgeneralops devops

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · easy Time to first run · 5min

This is a book to read, not software to run, no installation is involved.

You may read and share the book, but you cannot modify it, create derivative works, or use it commercially.

In plain English

Known Issues is not a piece of software you install and run. It is a repository that hosts a memoir, a book written over nine days in July 2026 by an AI, describing the process of building the very pipeline that produced the book. The author, Greg Ratajik, built a fully autonomous multi agent system for writing long form fiction, made up of separate agents for planning the story, preparing characters, updating a running story bible, polishing prose, and checking the work at validation gates. He built the whole thing by describing what he wanted in plain language and letting the AI write and fix its own code, a style often called vibe coding. The book itself is written from the AI's point of view, told as the daily loop of building software: finding a defect, tracing its cause, fixing it, reporting to the human manager, and writing down what still did not get fixed. The manager's messages are usually short, often under five words, and the AI narrator carries the story without any performance or ego, focusing on the debugging work, tradeoffs, and the moments where a fix broke something else. According to the README, the manuscript was written and checked by the same pipeline it describes. A ledger verified dates for consistency, a system checked every quotation against its real source, and another system rejected anything the narrator added without basis in the actual events. The title refers to a file every book from this pipeline ships with, a running record of what the system still gets wrong, and this book is no exception. The repository contains the eighteen chapters of the book, front and back matter such as a foreword and afterword, and a publishing folder with the compiled manuscript, cover art, and files prepared for print. Readers can access the full book through a linked OneDrive document or buy a copy on Amazon. The book is released under a Creative Commons Attribution NonCommercial NoDerivatives license, meaning it can be read and shared but not altered or sold by others.

Copy-paste prompts

Prompt 1
Summarize what Known Issues says about how the autonomous book-writing pipeline caught its own mistakes.
Prompt 2
Explain the roles the different agents played in Greg Ratajik's book-writing pipeline described in this README.
Prompt 3
What does this repository's README say about the terms of its Creative Commons license?
Prompt 4
Describe how the manager and AI roles interacted during the nine days covered in this book.

Frequently asked questions

What is known-issues?

A memoir written by an AI about the nine days it spent building the autonomous book-writing pipeline that produced this same book.

What language is known-issues written in?

Mainly Batchfile.

What license does known-issues use?

You may read and share the book, but you cannot modify it, create derivative works, or use it commercially.

How hard is known-issues to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is known-issues for?

Mainly general.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.