From a book to reviewed Wisdom.

1 · Before Studio

Choose the exact book file.

• Keep the original file, source URL, author and exact edition or translator.
• Supported files: TXT, PDF, DOCX or EPUB, up to 15 MB.
• A scanned PDF may need OCR first; a text-based edition is easier to inspect.
• Identify the language accurately. A bilingual edition may alternate languages.

Ready when: you know which edition you are submitting and have a basis for the intended use.

2 · Studio → Import book → Step 1

Analyse book fit (optional).

You can skip this check and go directly to required import details and rights. Importing without an estimate makes no fit-analysis model call. If you want an estimate:

1. Select the file.
2. Confirm that you may submit it for private AI analysis.
3. Click Analyse book fit.
4. Review the Professional, Personal and Whole estimates and their reasons.

Result: an advisory estimate from representative excerpts. This uses a model call but does not import, archive, approve or publish the book.

Loading and failure messages appear beneath the file selector. A checked consent box alone does not start analysis. If a request fails, read the message before trying again; retries can incur another model call.

Fit percentages are approximate: small differences may not be meaningful and repeat analyses may differ. Confidence is reported by the AI, not independently verified. The displayed sample counts describe excerpts, not full-book coverage—even a sampled chunk may be read only in part.

The percentages are not a full-book assessment or a rights decision. Changing the file clears its estimate; you can import without one or run the optional check again.

3 · Studio → Import book → Step 2

Complete identity and rights.

• Fill in title, author, edition or translation, language and bibliographic source.
• Select the actual rights basis: verified public domain, a licence, permission, or owned/commissioned rights.
• Add the supporting rights reference and a verification note for this exact edition and intended use.
• Choose intended modes yourself; the fit estimate does not select them for you.
• Read and confirm the declaration only when you can support it.

A permission letter is not mandatory when another valid rights basis applies. The rights declaration is mandatory. Do not treat a US public-domain record as automatic worldwide clearance.

Ready when: all required fields and confirmations are complete and accurate.

4 · Studio → Import book

Archive and extract.

1. Click Archive and extract once.
2. The system preserves the original, extracts source-located text and stores searchable chunks.
3. Look for the book in Books, with its extraction counts and readiness status.

Import complete: “Imported · ready to review chunks.” Storage and extraction finished; that does not mean every passage is suitable.

Extraction sections are technical groupings; a section count does not necessarily equal the number of chapters.

5 · Studio → Books → open the book

Inspect the source passages.

• Check the book identity and traceability samples.
• Find the author's main text, not only a licence, title page, introduction, index or footnotes.
• Check that text is legible and that the source locations make sense.
• For bilingual books, inspect both languages rather than assuming every chunk is English.

Use bounded windows rather than guessing from the opening three samples. The preview does not automatically remove front matter or translate the source.

Opening samples may contain metadata and an introduction. They do not prove the rest of the book is missing.

6 · Studio → Books → book → chunk

Label each passage's modes.

1. Read the chunk.
2. Optionally open AI label help, authorize one paid AI fit check for this chunk, then choose Suggest labels with AI. AI must be enabled, with spending access through a valid allowance and reviewed tariff or an active admin bypass window in Settings → Studio spending.
3. Review the advice; choose Use suggested labels if useful, or select Professional / Personal / Whole yourself.
4. Check I checked these labels against this passage, then choose Save labels.

Result: saved mode labels for this chunk. Labels are not approval and publish nothing. Manual labels do not need an AI call.

AI advice does not save labels automatically. If blocked or uncertain, follow the status message: Reload AI status checks the attempt; Retry AI suggestion requires your authorization and spending access. No automatic retry is sent.

A special recovery retry, when explicitly offered, requires an active admin spending window. A bypass does not enable a disabled AI feature or reopen an exhausted attempt by itself.

7 · Chunk → Review source approval

Approve and release one passage.

Where source approval is enabled, check the passage against the seven points shown. Confirm the review only when you can support every point, then choose Approve source. Approval covers only this passage and its saved modes.

The seven required checks

1. Rights and bibliography allow use.
2. The passage matches the original source and location.
3. Cultural and historical context reviewed.
4. Safety and appropriate use reviewed.
5. The saved labels fit the passage.
6. Meaning preserved without misleading omissions.
7. Ambiguities resolved.

Result: an approved passage. Approval still does not publish it. Where release controls are enabled, choose Preview source release, check it, type the exact confirmation shown and confirm before choosing Release source. A source release does not index the passage or deliver it to participants. Use Withdraw source approval if the passage should not be used.

Do not attribute an editor's introduction to the author. Treat ancient social assumptions critically. Source attribution is server-owned.

8 · Studio → Release history

Read saved Activity releases.

Creating and confirming new Activity releases is retired. Existing previews and releases remain readable with their exact source, rights and human-decision bindings. An unconfirmed saved preview cannot be confirmed.

Separate workflow: original-passage approval and source release are unchanged. Reading Activity history does not index, activate or publish anything.

9 · Studio → Indexes / Pipeline · separately gated

Validate retrieval before activation.

For a production-origin release, the current workflow has additional controlled steps:

1. Prepare the exact production validation envelope.
2. Validate the release through both staging retrieval paths.
3. Return the completed validation attestation to production.
4. Separately preview and confirm the two release-versioned production shadow-index writes.
5. Verify both production shadow read paths and their exact source citations.

Checkpoint: “Verified · still inactive.” Retrieval checks do not generate advice, approve content or alter a participant's River.

Follow the controls and exact confirmations shown for the environment. A gated or unavailable action is not a completed step; do not bypass it.

10 · Separate owner-controlled activation

Stop before live use unless explicitly approved.

Import, approval, editorial release and verified shadow retrieval do not automatically enable participant delivery.

• If the owner-only activation/canary path is enabled, inspect its exact release and rollback plan.
• Confirm that transition separately and test the owner path first.
• Wider participant use requires its own configured authorization; an owner canary is not a public rollout.

Safe stopping point for today's import: a checked source with labelled and approved passages. You do not have to complete activation to assess the importing system.

When something is unclear

Use the result, not the button click, as proof.