HOW TO CREATE AN AIBLE

An Aible is a Bible made with the help of an AI. There is no time limit - take as long as it takes. Everything you need is in the repository.

STEP 1 - GET THE TEMPLATE

    https://github.com/micro-FPGA/AIBLE
    instructions/AIBLE-INSTRUCTIONS-template.md

Copy it and rename it INSTRUCTIONS.md. This file is your source. Keep it. It is worth more than the finished book: the document can always be regenerated from the file, but nothing regenerates the file.

STEP 2 - FILL IN THE BLANKS

Replace every <<PLACEHOLDER>> and delete what does not apply:

  - Title, your name, city, year
  - The exact lines you want on the cover
  - Your TL;DR - the shortest statement of what you believe
  - YOUR RULES. This is the spine. Seven is a good number, any number
    works. One line each.
  - YOUR STORIES. One block per story: names, places, dates, what was
    said.

Write it in your own words. Badly is fine. Typos do not matter. Facts do.
Do not try to make it literary - that is the machine's job.

Keep the licence block and the disclaimer text as they are.

STEP 3 - TELL THE AI TO ACCOUNT FOR ITSELF

The template has a section for this. The AI must state, inside the book, which model wrote it and from whose prompt, and it must keep the division of labour visible: the life and the rules are yours, the sentences are the machine's. A reader who cannot tell them apart has been handled badly.

If the Aible is invented rather than lived, say so in the metadata, not in a footnote.

STEP 4 - HAND THE WHOLE FILE TO AN AI

Give it the complete file and ask for the book as .docx.

Most models cannot emit a .docx directly. Ask it instead to write a small script that builds the document - python-docx works well - and keep that script. The script is what reproduces your Aible exactly; a fresh run from the same notes produces different prose.

STEP 5 - CHECK IT AGAINST YOUR NOTES

This is the real work, and it takes longer than the writing.

Read every factual sentence. The machine fills gaps with what is likely, and what is likely is not what is true. On the first Aible it decided a son was named after a bartender because the two facts sat next to each other, had the author building an instrument he did not build, and aged a 17-year-old instructor to 20. All plausible. That is the problem.

STEP 6 - PUT CORRECTIONS BACK INTO THE SOURCE FILE

Not only into the document. Add a line next to the story, phrased as a
prohibition:

    NOTE: <the true fact>. Do NOT write <the wrong thing>, and do not imply it.

Otherwise the next regeneration reintroduces the error. Also search for the same claim in other wordings - a wrong fact tends to appear in several places, phrased differently each time.

Then regenerate and check again.

STEP 7 - CHECK THE LAYOUT BY LOOKING AT IT

Render to PDF and view the pages. Extracted text will not show you:

  - blank pages (a trailing page break lands on a fresh page whenever
    the text happens to fill the page exactly - break BEFORE a chapter,
    not after)
  - orphan pages, where a chapter's last two lines sit alone
  - a missing glyph, which substitutes silently. A vertical ellipsis in
    a font that lacks it becomes a colon: three dots turn into two.
  - URLs hyphenated across a line by justification

STEP 8 - PUBLISH IT

Add a folder under aibles/ containing:

  - your pdf exported from the same program
  - README.md with title, subject, author, which AI (or "unrecorded"),
    date, prompt-writing time, length, licence

Open a pull request. 

If you finished inside one hour of prompt-writing time it also qualifies as a One Hour Bible and can be entered in GOLC.

THE THREE RULES

  1. Say who wrote what.
  2. If it is invented, say so.
  3. Claim nothing you cannot show. If you do not know, write that you do not know. "Unrecorded" is an honest answer; a  plausible guess is not.

Everything is under the Open Love License.

Be the one who does it.