Session boundary¶
Point stores the participant-visible Session event stream supplied by an Agent integration, plus source and Git metadata in manifest.json. Point does not prescribe a closed set of participants or event types; an adapter can preserve the native semantics of the runtime it connects.
It does not claim access to hidden model reasoning.
Preserve the source¶
Point does not replace the Session with a summary or rewrite a participant’s intent. session.jsonl remains the source; titles and terminal rendering are indexes and views.
Publishing boundary¶
A Stash Point or Commit Point is local until its point-context/v1/* branch reaches a remote. point push is the controlled publication command: it publishes the selected Point and the immutable ancestors needed to reconstruct it, without including unrelated local directions.
Because Point Refs are ordinary branches, a raw Git command such as git push --all or a broad push refspec can also publish them. Point never pushes automatically, but repository Git configuration is part of the publication boundary.
Inspect a Point before publication when needed:
Point 0.4.0 does not provide a redaction engine. The integration decides
which participant-visible Session is intentionally supplied, and the user decides
when that lineage becomes team-visible.
Published Point tips are stored as ordinary branches under point-context/v1/*.
They are visible to repository readers and can be fetched by a normal clone.
Repository permissions therefore define the publication boundary;
Point does not add a second access-control layer.