Collaboration workflows

Point asks people to make only three product decisions:

• Stash when unfinished context should survive the current Agent runtime.
• Commit when a coherent project change should retain the Session that led to it.
• Publish when the team should be able to depend on that context.

Everything else—Session identity, parents, Git Branch, HEAD, event format, and Git Refs—is integration work.

Local handoff

1. A human and Agent discuss a failure mode and use tools to inspect the project.
2. The human says, “Save this Session as a Point.”
3. The Skill exports all new visible events and runs point stash.
4. A second local Agent runs point resume.
5. Point reconstructs the complete reachable context and records master as the new Session’s parent.

No remote or platform account is required. Both Agents use the same repository’s Point objects.

Parallel exploration

Two Agents can continue from the same source:

point resume <origin> --branch bounded-backoff
point resume <origin> --branch circuit-breaker

Their later Points form separate immutable directions:

                         P1 · bounded backoff
                       /
P0 · shared Session
                       \
                         P2 · circuit breaker

Neither Agent copies P0 into its new Point. P0 remains the shared parent.

Converge through a real Session

A third Agent can read both directions:

point resume <point-1> <point-2> --branch master

Point loads the union of their ancestry once. The Agent compares evidence, the human makes a decision, tools validate it, and only those newly produced events are saved:

point stash --title "Adopt bounded backoff" --session-file decision.jsonl

The new Point has two Git parents. This is a provenance edge, not a semantic text merge.

Commit a project change without losing the worksite

When the new direction produces a coherent repository change:

1. the Agent stages the intended project changes;
2. the Skill prepares the new Session segment;
3. normal git commit runs;
4. the Hook creates a Commit Point linked to that Git Commit;
5. master advances to the Commit Point.

The Hook checks both the previous Git HEAD and staged tree recorded during preparation. A stale Session cannot silently attach to an unrelated change. If no Session was prepared, no Commit Point is created.

Publish stable team context

Local Stash Points are cheap working history. They become team-stable only when pushed:

point push master --remote origin --with-code

Point sends the accepted branch, its immutable Tip, every required Point ancestor, and the current Git Branch in one atomic Git operation. A rejected push publishes neither side.

Another teammate can then run:

point fetch --remote origin
point resume

They receive the original Session worksite, not a later summary of it.

When to save

Save at a boundary that another participant may need to continue from:

• the intent is clear enough to hand off;
• the work is paused before a project change is committed;
• another Agent should explore independently;
• two directions are ready for a new decision Session.

Do not save every message. A Point is a meaningful continuation boundary, not an activity log tick.