THE THRESHOLD / READING-CIRCLE HANDBOOK

The Threshold reading circle: rollout and handoff

Owner direction: Dominique, November 10, 2026. This handbook establishes the self-paced reading practice and its contribution route. It does not schedule meetings, appoint facilitators, create membership or change story/game canon.

Start here

  1. Open https://loptrlab.com/training/threshold.html. Training home also links to The Threshold · read 15 minutes a day. Holdings discovery and its desktop Projects window link to this same reader, rather than Mayhem.
  2. Choose one accessible book. Ask your local public library about print, ebook, audiobook and interlibrary loans. Search Open Library; a catalogue result is not a promise of a loan. Check resale bookshops, library sales and book exchanges before buying new. Independent bookshops can help; Amazon is an optional last resort. No purchase is required to participate.
  3. Read for 15 minutes a day, at your own pace. The timer is optional. Reading takes the fifteen minutes; reflection afterward is optional, not a quota.
  4. Write a question or a few thoughts in your own words if useful. Name the book and use your edition's chapter/page/audio locator. Different editions and reading speeds are welcome. Missing a day never locks anyone out.
  5. Keep notes private or choose an excerpt to discuss. The existing community entrance is https://made-sick.org/join.html. Introduce your book and one question there using its normal flow. No notes, identity or consent flags are carried in the link. This reader has no group feed or submission API.
  6. Explore https://loptrlab.com/training/pixie-contributors.html when ready for a bounded contribution. Reading alone is a valid place to begin.

Comprehension practice, without grading people

Choose one or two questions; do not turn the whole list into homework.

PracticeSample questionA useful response contains
RecallWhat happened, or what claim did the author make?Two sentences in the reader's own words.
EvidenceWhich action, detail or example supports that interpretation?An edition locator and a distinction between observation and inference.
ClarificationWhat word, motive or reasoning step is unclear?A question and the surrounding context; uncertainty is acceptable.
PerspectiveWhose viewpoint is available? What other explanation could fit?An alternative reading and what evidence could change the reader's mind.
ApplicationWhich project thread does this illuminate? Where does the comparison fail?A specific connection with limits, rather than declaring two stories identical.
ReflectionDid writing or another reader's question change your understanding?A revision or an explanation of why the initial reading still fits.

Example scaffold: “I think ___ because the detail at ___ shows ___. Could ___ also explain it?” For craft writing: “The author claims ___. Would it still hold in this playtest situation?” These are scaffolds, not model answers. Accept a spoken contribution, private audio note or sketch as alternatives. Do not diagnose a reader, demand personal disclosures, or require programming or advanced mathematics to enter the circle.

Where people can contribute

Role someone wants to trySmall first contributionReview destination
ReaderOne question, observation or alternate interpretationOptional existing community discussion.
WriterA short original scene exploring one book-card promptOwning story source; Dominique accepts story canon.
ArtistAn original study from documented visual observationsOwning design bible and approved assets; name influences.
DesignerOne existing decision mapped to rule, feedback and consequenceOwning game design/rule source; label any change proposed.
Tester/developerA reproducible question, accessibility observation or bounded testExisting contributor task and owning repository's review process.
FacilitatorA short discussion summary with unanswered questionsShared only with participants' permission through existing channels.

These are participation choices, not appointments, ranks or automatic task assignments. Check current issues and coordinate through the existing contributor route before taking a task; avoid duplicate or overlapping work.

Facilitation format another person can pick up

Self-paced participation is available without a host. A volunteer who wants to host a discussion must first agree a time, channel, accessibility arrangements and spoiler boundary with participants through existing community channels. No standing meeting or named host is announced by this release.

For a small optional discussion, use this adaptable 25-minute format:

  1. 3 minutes: name the book/edition and spoiler boundary; offer the right to pass.
  2. 7 minutes: invite one recall or clarification question, then locate evidence.
  3. 7 minutes: compare interpretations without scoring or forcing agreement.
  4. 5 minutes: choose one possible story, art or design connection; state its limits.
  5. 3 minutes: ask whether anyone wants a bounded original task. Record unresolved questions and consent to share a summary. Passing is a complete response.

Readers need not be at the same chapter. Separate groups or use passage-level spoiler labels when positions differ. Avoid unsolicited plot reveals, long copyrighted extracts, book scans or copied comic panels. Refer to editions and locations; summarize in your own words. A facilitator does not accept canon.

Source authority and influence

Notes and privacy

The optional timer and notebook operate in the browser, without accounts, network requests, analytics, publication, membership or cross-site transfer. The notebook keeps each book's notes separate. Saving to browser storage is unchecked by default and requires an explicit choice. This is local storage, not encryption or an account backup; avoid private information on shared devices. Download notes before clearing browser data or changing devices. Clearing the notebook cannot remove downloaded files. Share a chosen copy yourself through existing channels. There is no automatic submission or facilitator access.

Rollout and release responsibilities

  1. Maintainer: verify reader and Holdings previews, source checks, library links, comprehension prompts, mobile layouts, keyboard controls and notes.
  2. Release maintainer: release Training first; verify the public reader and assets. Then release Holdings through its existing Pages/Vercel workflows and test its discovery and desktop links. Preserve PR #60 security protections and the single persistent PIXIE control.
  3. Maintainer: keep the stable reader URL in the blog copy. Never substitute a temporary protected preview link in a published article. Record release commits, URLs and actual checks in review-packet/THRESHOLD_RELEASE.md.
  4. Dominique/editor: review the PIXIE blog draft, byline and AI disclosure, attach its original graph with alt text, and publish through the existing pckt workflow if desired. Writing a draft does not publish it. Link its final permalink from appropriate existing discovery surfaces afterward.
  5. Future facilitators: read this handbook, invite opt-in discussion through the existing community, and agree logistics before announcing a session.

The published practice is asynchronous. Future live sessions, automatic feeds, notifications, reading analytics and publication integrations are proposals, not release capabilities. No one is assigned to an unconfirmed event.

Maintainer checks and rollback

Run node scripts/build-threshold.cjs after source changes, then node scripts/build-threshold.cjs --check, node scripts/build-threshold-handbook.cjs --check, node --test test/threshold.test.cjs, node --check docs/threshold.js, npm run typecheck and node scripts/validate-ai-literacy.cjs. The existing engine starter deliberately contains Not implemented methods; preserve its documented CI starter policy. Run Holdings' npm test separately.

To reproduce the browser evidence without publishing anything:

  1. From Training, run python3 scripts/stage-threshold-preview.py to create a separate local fixture at /tmp/threshold-preview. This includes the reader and its rendered handbook; the blog draft stays Markdown in the review packet.
  2. In one terminal run python3 -m http.server 4203 --bind 127.0.0.1 --directory /tmp/threshold-preview (on one command line).
  3. In a second terminal, from the Holdings repository, run node --input-type=module -e 'import {createAppServer} from "./src/lib/app.js"; createAppServer().listen(4197,"127.0.0.1");' (on one command line).
  4. Use a separate Playwright tooling installation and Chromium. From Training, run THRESHOLD_PLAYWRIGHT_MODULE=/absolute/path/to/playwright node scripts/test-threshold-browser.cjs (on one command line). Set THRESHOLD_CHROMIUM if Chromium is not /usr/bin/chromium.
  5. Read review-packet/threshold-evidence/checks.json and screenshots. Stop the local servers when finished. These fixtures block unrelated external services; check stable public routes separately after release.

In a browser, verify seven books, edition searches, book-specific prompts, timer start/pause/reset/completion, per-book notes, default no-storage behavior, opt-in persistence, export, opt-out and clear. Check keyboard focus, no-JS reading content, reduced motion and 320/390/768/1024/1440px layouts. Record physical-device Safari/VoiceOver separately; Chromium emulation is not proof.

Rollback by reverting the release commits through each owning repository's normal review/release process; do not force-push or alter historical sources. Keep an accessible reader destination while repairing a discovery link rather than routing reading back to Mayhem. Preserve reader exports; reverting the site does not erase browser notebooks or previously downloaded files.

Finished state: stable Training and Holdings entry links work, this handbook is reachable from the reader, source and browser checks are recorded, and a new reader can choose a book, ask a question and find a contribution route without this chat. Blog publication is separately marked ready or completed.

Delivery correction — November 10, 2026

The facilitator handbook is a readable web page at docs/threshold-book-club.html, linked directly from the reader and reviewable on Vercel. This Markdown remains its maintained source. Regenerate the page with node scripts/build-threshold-handbook.cjs after editing this handbook.

The PIXIE blog draft is delivered as review-packet/threshold-blog/post.md, with its original PNG/SVG figure. Its earlier Training-themed HTML preview was the wrong delivery format and is no longer maintained. Publication, layout and theme belong to the existing pckt editor and remain Dominique’s choice.

Required collaboration preparation — November 16, 2026

The Threshold now includes a required business-reading lane alongside the unchanged seven-title story catalogue. Start the original fit-check class at https://loptrlab.com/training/threshold-fit.html. Its publisher source is Dr. Kevin Burns’s Instructor’s Guide to The Power of Broke, the book by Daymond John with Daniel Paisner. The class carries the direct PDF citation and reading locators. No affiliation or endorsement is claimed.

Ask prospective parties to identify needs, actual resources, mutual value, a time-capped task, boundaries and evidence for continue/revise/stop. Reading is required preparation for scoped collaboration, not a gate on public reading, feedback or access help. Offer accessible discussion and accept disagreement. Do not grade people or require personal financial/medical disclosures.

Maintainers keep this class in Training and link here from future onboarding updates instead of copying a new curriculum into each project. Update the primer, reader generator and class together. Do not mirror the publisher PDF or introduce forms, analytics, automated approvals or manga-download unlocks.