How Changes Travel

Work here. Capture what matters. Listen before combining. Share when you are ready.

Local is where you work

Local means the copy on your computer.

This is where unfinished thinking belongs. You can write, change direction, and try things without sending them anywhere. Saving a file keeps your work, but it does not yet say, “This is the understanding I want to remember.”

Capture is choosing what to remember

When an idea becomes clear enough to keep, you capture it.

A capture records what changed and why it mattered. Underneath, this is called a commit. You do not need to manage that machinery yourself; you can tell the agent:

“Capture what we just figured out.”

Capturing creates a point in time you can return to. It still remains local until you choose to send it.

A capture is not a claim that understanding is finished. It is one clear position in a process that continues. See knowledge keeps moving for how reflection turns experience into the next capture.

Remote is the shared source of truth

A remote is the shared copy that people and agents compare against. For spaces hosted by IdeaSpaces, that remote lives at ideaspaces.xyz.

You send your captured changes to the remote. Other people bring remote changes into their local copies. Nobody needs to edit the same live document at the same moment.

Listen before bringing changes in

An agent can check the remote without changing your files. Ask:

“What changed while I was away?”

“Check this space for updates, but do not bring them in yet.”

“When I return here, check whether the remote has moved.”

The agent can show:

• what you captured locally but have not sent;
• what changed remotely but is not on your computer;
• and, when your copy came from another space, whether that source has changed too.

Today, listening means checking when you ask or when you have agreed that the agent should check. It is not a background notification service.

Bring changes in, then send yours

Looking and moving are separate on purpose.

First ask what changed. When you are ready, say:

“Bring in the remote changes.”

The agent should make sure your unfinished work is safe before it changes your local copy. After you have reviewed the combined result, you can say:

“Send our captures to the remote.”

Remote changes come in. Your captures go out. Saying the direction prevents surprises.

A conflict starts a conversation

Sometimes two people change the same part in different ways. The machine cannot know which understanding should win.

That is a conflict. It is not damage, and it should not be hidden or resolved by guessing.

The agent should:

1. stop before choosing a side;
2. show you both versions and where they differ;
3. help uncover what each person meant;
4. let the people involved agree on the new version;
5. capture that resolution;
6. then send the agreed result to the remote.

A conflict is the space saying, “Our shared understanding needs attention.” The resolution is new understanding worth capturing.

Two rhythms meet here

The knowledge loop is:

Explore and discuss → Capture and reference

When a remote is involved, captures also travel:

Listen → Bring in → Resolve together → Send

Not every turn needs every step. Local work can remain local. Listening can end with “nothing to do.” A conflict can wait until the right people are present.