# The Leanpub release — two books, one pair

**Status:** ⏸ **WAITING ON THE FOUNDER** — every agent-buildable piece is done (v0.5.19).
What remains is account work only, listed under "the upload-day checklist" below. Nothing
in the repository blocks it, and no agent should start it.
**Date:** 27 August 2026
**Commissioned by:** brief 39 ("release the two books we have all the way to Leanpub…
because shipping is one of the most important things you can do")

## What ships

| | | |
|---|---|---|
| *Fractal Semantic Graphs: Meaning Through Connectivity* | **v0.2.0** | 18 chapters, 38,029 words, 119pp PDF |
| *Creating a Book Using Fractal Semantic Graphs* | **v0.1.0** | 17 chapters, 31,221 words, 92pp PDF |

The Universe volume (v0.1.0, held) is NOT in this release. It stays published on the site
and is returned to later.

**What the version numbers say to a reader.** v1.0.0 is reserved for a book's actual final
release. Shipping at v0.2.0 and v0.1.0 states plainly that these are books under review —
which is exactly Leanpub's own model, and exactly true. The Leanpub description should say
so in one sentence rather than let a reader discover it.

## The account, as it actually stands

`leanpub.com/u/diniscruz` — checked, not assumed:

- **Ten published books** (Generation Z Developers, SecDevOps Risk Workflow, Hacking
  Portugal, Practical Eclipse Plugin Development, Practical Git and GitHub, Practical
  AngularJS, Practical Jni4Net, Practical O2 Platform Tools, Thoughts on OWASP, Exploiting
  MVC Model Binding), one unpublished (Measure Software Quality using Application
  Security), and one published bundle, "All Books".
- **The bundle is a precedent**: these two books are a natural pair and can ship as one,
  the way "All Books" already does.
- **The author bio is years stale.** It still reads "CISO of the Photobox Group and an
  active OWASP contributor". Updating it is on the checklist below, because every new
  listing inherits it.

## The method is already written

`admin/publishing.html` carries the publishing plan from the first book, and it holds up.
Its Leanpub section decides the things worth not re-deciding:

- **Upload our own PDF; do not write in Leanpub's markdown.** "Our pipeline is the
  typesetter; Leanpub is the counter." Both books already build their own PDF.
- **The screen-reading PDF is the book**, because that is what a Leanpub buyer reads.
- **The EPUB slot stays empty** until a reflowable edition exists; Leanpub sells a
  PDF-only book happily and the EPUB joins later without a new listing.
- **Cover**: PNG, 1600 × 2400 or larger.
- **Copy comes from the metadata sheet, unchanged** — the same words everywhere.
- **Pricing** is a minimum plus a suggested price, reader slides between; royalty 80%.

What is new here is only what is specific to these two books.

## What still needs building (agent work, before the founder touches the account)

1. **A cover per book.** `admin/build/gen_cover.py` exists (400 lines) and made the first
   book's cover; it needs a title/subtitle/colour configuration per book and a PNG export
   at 1600 × 2400.
2. **A metadata sheet per book**: title, subtitle, the 150-word store description, the
   one-line hook, categories, keywords, the licence line, the author line, and the
   "this is v0.x, you get every update" sentence. One file, used by every surface, so the
   store page and the site cannot disagree.
3. **A sample PDF per book** — Leanpub takes a free sample; the natural cut is the front
   matter plus the first chapter, generated by the same builder rather than assembled by
   hand.
4. **A landing page per book on the site** that matches the store copy, so a LinkedIn post
   can point at graphs.sgit.ai and a reader can then buy at Leanpub.
5. **The LinkedIn post**, drafted from the same metadata rather than written fresh: what
   the books are, what is honestly unfinished, and where to read them free.

## The upload-day checklist (the founder's hands)

1. Update the author bio on the profile — it is years out of date.
2. Create each book at Leanpub, choosing "upload your own files".
3. Upload the screen PDF and the cover PNG.
4. Paste the description, author line and licence from the metadata sheet.
5. Set the minimum and suggested price (the free-sample slot takes the sample PDF).
6. Publish, then create the bundle if the pair should sell together.
7. Send back the two store URLs, so the site's landing pages and the LinkedIn draft can
   point at real links rather than placeholders.

## What this release deliberately does not do

- It does not touch the books' content. These ship as they are; the review era changes
  them afterwards, under control, and every change moves the book's version.
- It does not go to KDP. `admin/publishing.html` has the paperback plan ready, and brief 39
  is explicit: Leanpub first, because Leanpub gives a release.