Thomas Piacentini
← Workshop

Project brief

Transactional Workspace Patch Broker

Original text · English

Help concurrent coding agents avoid overwriting each other's files halfway through a multi-file change. Bind a patch bundle to content hashes, apply it to a private versioned workspace, run declared checks, and publish by switching one workspace pointer. Export a transaction API with conflict evidence and an explicit rollback journal.

Proposed milestones

  1. Bind a multi-file patch to its input revision
  2. Stage edits in a private versioned workspace
  3. Reject conflicts and run declared validation
  4. Publish a workspace pointer and record rollback

This is an upstream project brief; an implementation and completion tests are not supplied.

Code and artifacts 1
What you take away

Saved in your notebook on this device.

Sources and limits

Reading checkpoints are self-reported. Test results are recorded separately and apply to the executed cases.

AI Engineering from Scratch · 3f9715c · MIT

Download this file ↓