See what changed before it ships

Source control gives agent work a reviewable change boundary. Axis keeps repository state and session evidence close enough to inspect what changed, validate it, and save only the owned result without sweeping in another workstream.

Use source control to preserve reviewed work

Use source-control context for code, documentation, configuration, and other tracked project changes—especially when several sessions share a live checkout or when the result must be reviewed before release.

This is direct change evidence from the product, not a stylized branch diagram.

What safe integration adds

1. Reviewable scope. Changed files and history stay visible beside the work.
2. Safer concurrency. Narrow ownership prevents agents from overwriting one another.
3. Traceable results. Validation and the saved change can point back to the exact session.

Mission: save one owned change safely

1. Inspect branch and working-tree state before editing.
2. Claim only the files or line ranges the session owns.
3. Make the smallest coherent change without touching unrelated live work.
4. Run focused validation and inspect the exact diff.
5. Submit the validated owned paths through the project’s integration flow.

Preserve unrelated live work

Source control does not prove runtime behavior, visual quality, or an external side effect. Pair the diff with tests, browser proof, persisted state, or destination checks at the layer that changed. Never discard, reset, stage, or save unrelated work merely because it is present in the shared checkout.

Related references

• Projects and workspaces
• Sessions and steering
• Working agreement

Put this to work: Define the project’s validation and ownership rules before editing.