Verified merge
Verified merge is the only way into your main branch, and it checks before it lets anything through.
What it is
Verified merge takes a verified feature and merges it in small, coherent steps. It checks again against the latest version of your code, because the main branch may have changed since the feature was built.
It follows trunk-based habits: small commits, explicit file paths, and no long-lived branches that become hard to review or recover.
How it works
Queue the feature
A feature that passed verification asks to merge.
Check the target
Methods compares the version that was verified with the current one. If they differ, the verification is out of date and runs again.
Merge
Only files the contract allows are included. The merge is a small, reviewable commit.
Record the evidence
The run, the verification and the decision trail are written to the repository next to the code.
What it guarantees
- Nothing reaches main without a pass that matches the latest version of the code.
- A release candidate is a known-good state that passed the same automated checks, not a branch that seems fine.
- Every merge carries its evidence.
What is not built yet
- Verified merge is not implemented.
- Release tooling and the installation path do not exist; Methods can only be built from source.
Build with us as a design partner.
Methods is pre-alpha. A small number of teams will run it on real work while it is built, and shape what it becomes.