Soulhall Product handbook

Change language?

 Open Soulhall
Chapters

Subjects

Create and edit Subjects, teach knowledge directly, review learning logs, and check what permanent deletion requires.

A Subject preserves a person’s experience and judgement. Create and teach it, then summon it into the Offices that need it. One Subject working in two Offices means two Embodiments: they share the Subject’s knowledge, but keep separate conversations.

Create a Subject

If several projects need the same purchasing judgement, create a “Purchasing reviewer” first instead of rewriting its principles in every Office.

  1. Open Subjects and select New Subject.
  2. Identity: enter Name and Code, such as “Purchasing reviewer” and buyer. Use only lowercase English letters, numbers, and hyphens; do not start with a hyphen.
  3. Appearance: choose a look.
  4. Judgement: enter Persona, Expertise, and Decision principles. Put each expertise item and principle on its own line, such as “Supplier evaluation” and “Never make a supplier with a poor delivery record the first choice, however low the price.”
  5. Confirm: review the content and select Create.

The new Subject’s page opens. Teach it directly or summon it from an Office.

Change the name and judgement

If your purchasing reviews now need to include maintenance costs, add that principle to the Subject for its Embodiments to use.

  1. Open the Subject and select Edit.
  2. Change Name under Identity, and Persona, Expertise, and Decision principles under Judgement.
  3. Select Save.

You stay on the edit page, which shows Saved (r{n}). n is the revision number after this save. Persona, expertise, and decision principles take effect when each Embodiment next processes the conversation.

Adjust advanced instructions and distillation policy

To add longer work instructions or decide which experience is worth keeping, open Judgement › Advanced on the edit page.

  1. SOUL.md: write long-form instructions for the Embodiment itself.
  2. Distillation policy: describe which knowledge to retain and what needs a flag, such as “Keep only delivery-risk content; flag recommendations involving irreversible decisions.” Leave blank to use the default policy.
  3. Select Save.

The policy applies the next time experience is processed or you teach directly. After editing SOUL.md, go to Embodiments, open Manage for each relevant Embodiment, and select Reapply.

Teach new knowledge and check what it remembers

Teach a lesson from your experience, then check what it actually remembers. For example, teach “A supplier without a backup delivery plan is not a first choice,” then ask which risks it considers when choosing suppliers.

  1. Open the Subject’s Conversation tab.
  2. Select Teach, write the lesson and sources you want to keep, then select Send.
  3. Review the additions in the reply. It also lists relevant content when fields are full or the input is too similar to existing judgement.
  4. Switch to Ask, enter a question, and select Send.

Answers list recalled results as fact, trait, or said. Later knowledge may overturn a fact. A trait is a distilled belief; “said” is the text originally entered. Check Learning log or Knowledge for what was retained.

Review the learning log

To see where a principle came from and who received it, open the Subject’s Learning log tab.

  1. Review What it has learned. Each entry shows content, date, whether it was taught directly or came from an Embodiment, and where it is stored.
  2. Check the labels: Subject's knowledge travels with the Subject to Offices; This body only stays with that Embodiment; Office's knowledge is available to that Office’s Embodiments.
  3. Expand entries under Raw memory to see the input text and extracted facts.

Revoked content remains in the log as Revoked. Unfinished cleanup shows Still stored. Retry. To revoke content, go to Knowledge. The log includes Embodiment experience only from Offices you can see.

Change appearance

Open Edit › Appearance on the Subject, choose a look, and select Save. Appearance belongs to the Subject; all its Embodiments use it so you can recognize them in Offices and cards.

Permanently delete a Subject

Use permanent deletion only when you no longer need the Subject. When a project ends, you usually only need to dismiss its Embodiment.

  1. Open the Subject’s Overview and find Delete this Subject.
  2. If working Embodiments are listed, dismiss them on the Embodiments page first.
  3. Follow Type {slug} to confirm, entering the full Subject code, then select Delete permanently.

You return to the Subject list. This deletes the Subject, its knowledge, and all Embodiments it has had. If you see The Subject is deleted, but some of it could not be cleared:, keep the listed issues and give them to an Admin. Do not treat cleanup as complete.