The story
Watch a project grow.
Each step below describes the project at that point; the animated graphic beside it shows the same.
01An idea
It starts with an idea.
A few notes on what to build. There is nothing to review yet.
One idea, with no checks.
02Artifacts
The plan and specification become Artifacts.
Choose pieces to review separately. An AI checks whether the specification covers the plan.
The plan and specification become two Artifacts with one AI review.
03Evals
Code arrives, and checks connect the parts.
Compare pieces with each other. Alice approves the specification before work builds on it.
The code is compared with the specification; Alice signs off the specification.
04Tests and style
Tests and a style review check the code.
Tests check the code. AI checks its style against a guide approved by Alice.
Tests, an AI style review and Alice’s approval are three different checks.
05Modules
The code splits into modules.
Give smaller code pieces their own checks so changes can be reviewed where they matter.
The code splits into three parts, each with its own tests and review.
06Beyond code
A website and docs pages join the graph.
Check writing and design too: compare the guides with the app connections they describe.
Documentation and website checks join, with Dana’s design approval.
07A change
Change one module, and only what depends on it runs again.
Change those app connections. Only their checks and the checks that use them run again.
The changed app connections and their users are checked again; unrelated results still apply.
08It keeps growing
New Artifacts and relations keep arriving.
Add new work and connections without redesigning the project’s review process.
A sync part, a brand guide and their checks join the project.
09Work in parallel
Work on your own copy of the project.
A shared review store lets teammates reuse reviews earned in each other’s project copies.
Alice, Bob and Carol work separately and share their review results.
10Merge and check
Bring changes together and check only what is new.
Bring changes together. The team checks review the new combinations and read shared results without changing them.
The combined project reuses existing reviews and checks the new combinations.
