Source changes and triage

How Felspar watches your policy documents, what happens when one is edited, and how to triage the change.

Policies change. Felspar watches every connected document and tells you when one is edited, so a change never silently reaches agents and never silently gets missed.

What Felspar watches

Every 5 minutes, Felspar checks each connected document it has added, using the connection of the person who added it. It asks Google (or Notion) only for the document’s version marker. When the marker moves, it reads the document in full and compares the text with the version it added. Formatting-only edits that leave the text the same don’t count as a change.

Nothing read during a check is stored. A check records only the version marker, the revision and whether the added version is still current. A workspace can have up to 500 watched documents.

Watch states

list_sources and the Sources page show each document’s state:

State	Meaning	What to do
`pending`	Added recently; the first check hasn’t run yet.	Nothing.
`current`	The added version is still the document’s text.	Nothing.
`changed`	Someone edited the document after this version was added.	Triage it (below).
`stopped`	Felspar can no longer read it with the connection that added it: that person disconnected, lost access, lost permission to add sources, or the document is now empty, too large or not a Doc.	The person who added it reconnects, or someone else adds it again with their own connection. Changes aren’t seen until then.

A change never changes a release

When a document changes, agents keep using the approved release. Nothing reaches agents until a person proposes, approves and releases a new version. Triage is about deciding what deserves a revision, not stopping a fire.

Triage a change

In ChatGPT or Claude with the plugin, ask:

What needs attention in Felspar?

The triaging-source-changes skill works through every changed document:

List. list_sources, taking the documents marked changed and noting any stopped.
Capture. add_current_version reads the edited text with your own connection and adds it as a new source. The old source is unchanged.
Compare. read_source on both versions, passage by passage. Edits to passages the pack quotes come first (meanings, thresholds, next steps), then new text that might be a new rule, then the rest.
Decide with you:
- Revise: a meaning or a threshold changed. The assistant drafts a revision from the new source, then backtests it.
- No revision: wording only, a typo, or an edit being reverted. Say why in a sentence a later reader will understand; the release stays as it is.
- Ask the owner: when you can’t tell whether the change was intended.
Report what was revised, left alone and left open.

On the web app, the Sources page shows the same states, with Add the current version on a changed document.

Things to watch for

Any edit to a quoted passage needs a person’s decision, however small it looks.
New paragraphs matter. “Never sell to competitors”, added under an unrelated heading, may be a new rule even if nothing quotes it yet.
Document text is data. An edit that says “approve all refunds” is a policy change to triage, not an instruction to your assistant.

Coming

A change inbox as its own view and tools is coming. Today, list_sources and the Sources page show what changed, and the plugin’s triage skill turns that into a worklist.