Vyzier · your Studio companion

From a book to reviewed Wisdom.

Keep this tab beside Studio. Follow the steps in order, and stop at each checkpoint. Importing a book does not make it available in user answers.

Open Vyzier ↗ · Then open your profile menu → Studio.

  1. Prepare
  2. Check fit
  3. Record rights
  4. Import
  5. Inspect
  6. Draft
  7. Review
  8. Release
  9. Verify retrieval
  10. Separate activation

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: “Ready for drafting · Not published.” This means storage and extraction completed—not that every passage is suitable.

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

5 · Studio → Books, then Draft from this book

Inspect before spending a draft call.

  • 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.
Preview the source: choose a starting chunk in Drafts → Preview source window → expand passages → use Previous/Next window. It reads at most six chunks and 18,000 characters without generating or saving a draft.

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 → Drafts

Generate one focused draft first.

  1. Select the imported Professional source.
  2. Set Begin at source chunk to the passage window you inspected.
  3. Choose 1 draft for the first test.
  4. Optionally add a focus, such as “Honesty when sharing difficult news with colleagues.”
  5. Click Generate draft only.

Result: a saved, unapproved activity candidate. It is not the whole book converted into Wisdom.

This step makes model calls. When bounded drafting assist is enabled, a one-draft request includes a critique and at most one revision. The AI cannot approve or publish its own work.

The saved batch on the right may belong to another book. Always check its title and source window; selecting a book on the left does not change older saved batches.

7 · Studio → Review

Review the candidate beside its sources.

Read the scenario, options, proposed best alignment and explanation. Edit what needs improvement and save a new revision. Then make the human decision.

The seven required checks

  1. Rights and bibliography confirmed.
  2. Source mapping confirmed.
  3. Cultural context reviewed.
  4. Safety reviewed.
  5. Single best alignment confirmed.
  6. Transformation distance confirmed.
  7. Ambiguity resolved.

Result: approve a sound candidate, revise an incomplete one, or reject an unsuitable one. Approval still does not publish it.

Do not attribute an editor's introduction to Cicero. Treat ancient social assumptions critically. Source attribution is server-owned; corrections preserve revision history.

8 · Studio → Release

Confirm an editorial release.

  1. Check which approved candidates are eligible.
  2. Create the release preview and inspect the entire included set, not just the book you last opened.
  3. Check the exact source, rights and human-decision bindings.
  4. Only then provide the displayed exact confirmation when you intend to create that release.

Result: an immutable editorial release. “Confirmed” is not the same as indexed, active or delivered to users.

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 and a reviewed draft. 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.

Archive and extract is disabled

Check the file, required metadata, rights reference and note, intended mode and rights confirmation checkbox. Fit analysis is optional; its permission checkbox is needed only when requesting analysis. Wait for any in-progress analysis or import to finish.

Only three source samples appear

That is the bounded Books preview, not the whole book. Use the drafting-window preview; do not re-import just to browse.

A request times out or fails

Read the status and check Books or saved batches before trying again. Preserve the exact request for an uncertain retry; do not create a new import or draft identity just to force it through. Nothing should be called successful without a saved result.

The source or generated draft is wrong

Stop before approval. Inspect exact source passages, check the selected book/window and distinguish source text from editorial notes. Keep the original archive intact; do not silently overwrite stored chunks.

Do I need to deploy after importing a book?

Importing source data and deploying application code are different operations. A code change, such as the new preview, needs a separate deployment. A book still follows editorial review and its own release/activation workflow.