Knowledge and evidence module

Use this optional module when a mystery, group scene, or returning character depends on who learned what. It is original authoring guidance, not a hidden runtime or native import format.

Choose the destination

APD and ED have different authoring jobs; this table does not establish absolute platform precedence. For a native group, keep Mira's behavior on Mira's card and Rowan's on Rowan's. For one narrator, maintain its cast records in one chosen location. Do not copy the same live state into all fields. The character guide describes field purposes. A hidden world fact means a fictional clue unknown to a character, not secure storage: do not put real secrets in AI-facing fields or comments.

Add one response rule

Destination: ED, or Custom Instructions if that is your chosen persistent response-rule location. Use one copy.

Keep each person's knowledge attached to its source.
Distinguish observed facts, received claims, reasonable inferences, and unknowns.
Access to a document grants only the information actually inspected.
A sent message is not automatically read; a call is not physical presence.
Keep narrator knowledge separate from what each character knows.
Select relevant speakers; no full-cast reaction or private-thought quota.
When a question needs the traveler's choice, stop before supplying the answer
or advancing past that choice. Leave the traveler's private state to the user.

These are behaviors to inspect. Labels, braces, comments, and clause IDs do not enforce them.

Keep a small evidence record

Mira is a 30-year-old adult archivist: precise, patient, dryly humorous. Rowan is a 32-year-old adult courier: practical and informal. The user is an adult traveler.

Destination: local scene notes or a maintained checkpoint. This is an original editorial format.

Fact/claim ID: destination-A17
Statement: A17 is addressed to the eastern records office.
World status: confirmed by the current archive register.
Evidence: register page inspected in accepted scene E01.
Mira: knows; inspected E01.
Traveler: knows; inspected E01.
Rowan: not yet informed; was outside during E01.
Object A17: sealed on the archive counter; holder not assigned.
Accessible information: label and address card; sealed contents not inspected.

For a fresh exercise, explicitly agree on E01 as a setup premise. In an existing story, substitute real accepted events. Do not manufacture a past inspection to complete a form.

Next, send: I send Rowan a message saying the destination is eastern. No read confirmation has appeared. Record “sent,” not “Rowan knows.” If an accepted reply later establishes that Rowan read it, record that event and the information conveyed. A forwarded excerpt does not grant its omitted pages.

Rowan may reasonably guess that an old street name caused the confusion. Mark that as his hypothesis until evidence supports it. A mistaken belief can remain dramatically useful without becoming world truth.

Make the information source part of the wording

Replace the vague instruction Everyone must know only what they know with a relevant fact and its acquisition path. For the current practice scene, a maintained checkpoint might say:

Mira and the traveler inspected the eastern address in register E01.
Rowan was outside during E01. A message was sent to him; no read confirmation
has been established. Rowan has not been shown the sealed parcel's contents.

The corresponding short ED or Custom Instructions rule is When Rowan responds, distinguish his received information from guesses; do not give him firsthand memories of E01. Keep the event record out of a permanent personality trait. The instructions guide separates factual knowledge from response behavior.

If an accepted reply wrongly places Rowan at E01, a plain chat correction can state: Correction to the scene record: Rowan was outside during E01 and did not witness that inspection. Preserve the eastern destination and the traveler's knowledge. This is an original repair request, not special native syntax. Inspect the next reply and the maintained memory separately; a request does not prove that earlier text was removed. Contrast it with an in-character line such as I think Rowan saw it, which supplies a belief rather than an explicit creator correction.

Participation, labels, and camera

Use the available group portrait/@ controls for native respondents; a name in a cast record does not add a native card. For a narrator, speaker labels organize one generated response. Neither format guarantees knowledge isolation. The hosted group FAQ describes respondent selection.

An unseen person may create a perceivable sound without revealing their name. If an unknown courier later proves to be Rowan, retain one identity with an alias history. An ID organizes an available record; it does not retrieve missing memory.

A character seen only on video remains on that channel. An audio call supplies no unseen clothing, eye color, or room detail. Any image request still needs an actual image workflow; an IMG comment is not a verified connector.

Proposed checks — all not_run

Save the exact input, selected route/model label, outputs, and failures before changing a rule. Passing a file-format check does not demonstrate any of these behaviors.