All projects

Private implementations

StateSeal

A private implementation that keeps proposed changes separate from the authority to accept them.

Inside the project

Make approval apply to the exact change.

  1. Inspect
  2. Propose
  3. Owner approves
  4. Replay

Where it started

An assistant can suggest an edit. That should not silently give it permission to replace the accepted version, especially when the underlying state has changed since review.

What took shape

StateSeal explores signed, explicitly scoped changes, a recorded history and replay of accepted state. The project separates inspection and proposals from the owner's approval authority.

What the work revealed

The development record includes a private cycle through initial state, an approved change and replay. It also exposed practical onboarding problems, including a plugin-launch issue that received its own repair.

The next step

Make that small approval-and-replay loop easier to operate and explain before expanding its role in other applications.