What the client can require before the first line of code
The client should start with a description of the effect rather than a technical solution: who is to do something, in what situation, and what the system should record at that moment. Such a description lets the vendor plan the change and separate it from existing functions. InnerWeb is the software producer, so custom features are built in the same repository and through the same review path as general features.
The contract should specify three things: the scope of the change, the acceptance criteria and the way of proving that the change passed review. Requiring proof is justified, because for work safety features a general assurance that everything works is not enough during an audit.
Does an ordered feature bypass the standard review?
No. Every change in the repository goes through static analysis, style checks and unit tests, and merging is blocked until the result is green. A custom feature has no shortened path.
How to describe the acceptance criteria?
An acceptance criterion should be verifiable by a test: a user scenario, the input data and the expected result. Such a scenario can then be added to the browser test package as a regression test, so the feature stays protected through later updates.
How change control works
Besides automated tests, the documentation describes a second, independent review agent that reads every change on the open merge request and assesses whether the code matches the description of the change and the domain rules. This way the author does not assess their own work.
The review measures the result after merging with the main branch, not just the working branch. A conflict is reported as a separate, blocking error, so a change that works only in isolation does not pass.
What comment classes does the review use?
Comments come in three classes: blocking, weighted warnings and suggestions. A single blocking comment is enough to fail a change. Warnings are weighted, and the pass threshold is 89 points. Suggestions never block.
How can the author respond to a comment?
Only in one of three set ways: fixed, disputed or deliberately left. A deliberately left risk is reported to the product owner, so the decision about the risk is visible and assigned to a person.
How many rounds of corrections are allowed?
The limit is two rounds. After a second failure the author switches to decision mode and reports the open questions instead of iterating endlessly. The client then receives a clear list of decisions, not another version without explanation.
Change control parameters
Tests that confirm the safety of a change
The browser end-to-end test package includes 242 tests in 31 files and runs a real Chromium browser against a real backend. The test database is rebuilt from migrations once per test run, so the result does not depend on data left by the previous run.
A test fails automatically when an uncaught JavaScript exception or a server response with status 5xx appears in the browser. This matters for custom features: an error on a new screen comes to light even if the test scenario did not check for it.
A known, not yet fixed error is marked in the test as an expected failure with a ticket number, never by skipping the test. Once it is fixed, the test itself reports that the annotation must be removed. Nothing disappears quietly.
A note on the state of the control mechanism
For the sake of transparency, we note that the documentation describes the independent review agent as designed and built, but, as of August 2026, not yet deployed to production. The static analysis, style checks and unit tests that block merging are, however, the basis of control for every change. The client should ask the vendor about the current state of both layers before writing them into the contract as requirements.
Video
Frequently asked questions
Can I require that a change passes browser tests?
Yes, it is worth writing this into the contract. The E2E package runs a real browser against a real backend and replays user paths, so it catches errors that unit tests cannot see.
What happens to a known but unfixed error?
The test marks it as an expected failure with a ticket number, without skipping the test. Once it is fixed, the test reports that the annotation must be removed.
Who learns that the vendor deliberately left a risk?
A deliberately left risk is reported to the product owner. The decision is therefore explicit and assigned to a person, not hidden in the change history.
Does the review check the change together with the rest of the system?
Yes. The review measures the result after merging with the main branch, and a conflict is a separate, blocking error.
Order your own feature
Describe the situation in which the system should record something, and we will show the path of the change from the order to the tests. Book a conversation with InnerWeb.
Let's talk