The console
The console is where you work. You define what should exist and rule on what only a person should decide.
What it is
The console shows the live dependency graph of your project, the runs in progress, cost per step and checks. You do not edit code line by line or read every diff.
Some decisions Methods will not make for you, such as changing the architecture's rules. The console shows you one when it blocks work, and records your answer.
How it works
Set direction
You write or approve feature contracts and set the rules Methods follows.
Watch the graph
Features, their state and their evidence appear as work proceeds.
Answer the decisions only you can make
When such a decision blocks work, it appears with the context needed to answer it. Your answer is stored in the repository.
Read the evidence
Every finished feature shows its contract, its runs and its verifications.
What it guarantees
- You supervise the work without doing it: direction, rules and the decisions Methods will not make are yours.
- The console reads and acts only through a versioned API, never by reaching into a product's files.
- It is open source and works without an account.
What is not built yet
- The first screen is being carried over from an earlier version. No screen has been checked against its main question yet.
- The background program the console talks to does not exist yet.
- The images on this site are placeholders, not screenshots.
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.