Why. "the forge should be built for users shipping and closing chapters… crossing something off a list. closing the book and moving on." Today a repository is either left to flow forever or switched off. A person building an app wants to say "this is v1", watch it fill in, ship it, and start v2 fresh.
What.
A chapter has a name ("v1.0.0"), one sentence of what done means, and a list of issues. A repository has at most one open chapter; any number can be drafted after it ("v2", "v3") and filled with issues that wait.
While a chapter is open, the crew builds only what is in it. The planner may split a chapter's issue into parts and may record a defect found on the chapter's own path; it may not add scope. Everything else it thinks of goes to a later chapter or to Later, where the owner sees it queued, not lost. Adding or removing an issue from the open chapter is the owner's act (drag it across the line on /queue), recorded.
The chapter's page is the list being crossed off: done items struck through with the day they went live, what is building now, what is left, and the date it will finish at the current pace. An item counts as done when it is live and proven, not when its pull merged.
Closing the book. When the last item is done, or when the owner presses Ship it and moves what is left to the next chapter, the forge tags the repository with the chapter's name, cuts the release, writes the chapter's notes from what landed (plain sentences, grouped, with who built what and what it cost), and marks the chapter closed. The owner sees one page that says it is finished: what shipped, how long it took, what it cost. Then the crew rests on that repository until he opens the next chapter. Nothing starts by itself.
A closed chapter stays readable forever at its own address and cannot be reopened; a fix for something it shipped goes in a patch chapter ("v1.0.1") the owner opens with one click.
Working ahead: a later chapter can be opened on its own branch or fork while the current one finishes, so v2 can begin without waiting; the queue shows both, each with its own budget share (a setting, default all to the open chapter).
For an app with no chapter, everything behaves as today (continuous flow). Chapters are offered, never forced: a new app's first ask suggests "make this v1?".
The forge's own first chapter is v1.0.0, seeded from the list on #334.
Acceptance. Tests: with a chapter open the dispatcher starts nothing outside it and the planner's new issues land in the next chapter; an item is not struck until its production proof passes; Ship it with open items moves them, tags, releases and writes notes; after closing, the crew starts nothing until a chapter is opened; a patch chapter opens from a closed one. A browser test walks open → cross off → ship → the finished page.
Why. "the forge should be built for users shipping and closing chapters… crossing something off a list. closing the book and moving on." Today a repository is either left to flow forever or switched off. A person building an app wants to say "this is v1", watch it fill in, ship it, and start v2 fresh.
What.
/queue), recorded.Acceptance. Tests: with a chapter open the dispatcher starts nothing outside it and the planner's new issues land in the next chapter; an item is not struck until its production proof passes; Ship it with open items moves them, tags, releases and writes notes; after closing, the crew starts nothing until a chapter is opened; a patch chapter opens from a closed one. A browser test walks open → cross off → ship → the finished page.