Tessera Patch
A patch workflow built for real upstream software.
Tessera Patch is the broader workflow and product idea behind the comparisons in this repo. The Showroom exists to make that work visible: what changed, why it changed, and how the patch can stay understandable when upstream evolves.
Workflow
Analyze → define → implement → test → record → reconcile
01
Analyze
Start from the upstream product, identify the real constraint, and map the request to the right part of the codebase before changing anything.
02
Define
Turn the request into explicit acceptance criteria so the patch can be reviewed, tested, and revisited later without guesswork.
03
Implement
Apply the smallest coherent change that satisfies the request while respecting the upstream product's patterns and boundaries.
04
Test
Validate the patch against the repo's existing quality gates and the user-visible behavior the change was meant to improve.
05
Record
Capture what changed, why it changed, and how the patch fits the upstream version so it can be reasoned about later.
06
Reconcile
When upstream moves, compare the new version against the recorded patch intent and reapply or retire the customization deliberately.
Why the showroom exists
A patching workflow is only credible if people can inspect the results. Tessera Code turns patch work into browsable proof: case studies, comparisons, and a public explanation of what the workflow is for.