Knowledge
Check knowledge audiences and sources, write facts manually, revoke incorrect content, and handle items that need a look.
Knowledge shows what Subjects and Embodiments have retained, where it came from, and who can read it. Review content distilled after work, knowledge taught directly to a Subject, and facts you wrote manually.
Find knowledge to review
Before using a supplier-risk judgement, check who it was retained for, then its source.
- Open Knowledge to browse recent records you can access.
- Choose a filter for what you need:
| Filter | What it shows |
|---|---|
| All | Recent knowledge and items that need a look. |
| Needs a look | Items the system has flagged for someone to review. |
| Subjects | Knowledge retained for a Subject, readable by its Embodiments. |
| Offices | Knowledge written for the whole Office, readable by its Embodiments. |
| Embodiments | Experience retained only for one Embodiment. |
| Revoked | Revoked records, including unfinished cleanup. |
| Unreachable | Stored knowledge with no searchable content. |
The list shows content, audience, date, and From a conversation or manual labels. Select Show more to continue.
Check an entry’s audience and source
Select an entry to open its Knowledge drawer.
- Check Who can read it, Written by, Date, and Source. Non-fact content also shows Kind.
- Check State and notices to see whether it is still processing, revoked, or awaiting complete revocation.
- If a source exists, read Original text. It may be conversation messages or directly taught text.
If a source is recorded but its text is no longer available, you see The original messages are gone. If no source was recorded, Source shows No source. Missing original text does not mean the claim was verified.
Write a fact and choose its audience
If you have confirmed a supplier’s minimum order is 200 units, record that fact directly instead of waiting for conversation processing.
- In Knowledge, select Write a fact.
- Enter Content, stating the confirmed fact and necessary evidence clearly.
- Choose an audience under Who should know this?:
| Option | What to retain | Who can read it |
|---|---|---|
| One Embodiment | Progress or temporary context useful only for this project. | Only the selected Embodiment. |
| Every Embodiment of one Subject | Knowledge or principles that remain true across Offices. | This Subject’s Embodiments. |
| Everyone in one Office | Shared information the whole Office needs. | This Office’s Embodiments. |
- Choosing a Subject also shows Kind: Fact, Preference, Procedure, Strategy, Decision principle, Expertise, or Persona. Content for an Embodiment or Office is stored as a fact.
- Select Send.
You see Saved., and the audience appears in the list. Manual writing retains the content you provide without extracting it from a conversation first. It still needs a search index afterward.
Revoke incorrect knowledge and confirm cleanup
If a stored returns rule is wrong, revoke the entry instead of only saying “That was wrong” in the conversation.
- Open the entry’s Knowledge drawer and select Revoke.
- Confirm when Remove this? appears.
- If you see Revoke unfinished or Still stored. Retry., reopen the entry, select Retry revoke, and confirm.
Once cleanup finishes, the entry is Revoked and unavailable to knowledge search. Its record stays under Revoked. If content was added to the Subject’s judgement fields, the system also tries to remove that original addition.
Handle items that need a look
If a new principle is too similar to an existing one or a Subject has reached its accumulation limit, the system leaves a flag explaining why no judgement was added.
- In Knowledge, select Needs a look.
- Open an item and read Why it needs a look and any available Original text.
- Select Mark as seen after reading. Managers, Admins, and Owners can do this for flags they can see.
The item leaves the default unread list, but the system keeps a record that it was seen. This acknowledges reading only: it neither approves knowledge nor revokes content. To remove incorrect knowledge, use Revoke on the knowledge entry itself.
Understand how conversations become knowledge
Distillation extracts content worth keeping from an Embodiment’s conversation experience, using the Subject’s Distillation policy to decide what to retain.
- After an Embodiment works in an Office, the system processes new conversation content.
- Knowledge that remains true elsewhere goes to the Subject. Experience specific to this work stays with this Embodiment.
- Check audiences and sources in Knowledge and revoke when needed. You can also review retained content in the Subject’s Learning log.
Content that passes the policy is retained directly, without waiting for human approval. General decision principles, expertise, and persona may also be added to the Subject’s fields. Flags do not block processing.