APRIXITY / IMPACTS
Understand work. Make processes verifiable.
What should the result be? Who checks it? And what happens when something is missing? The IMPACTS Protocol makes these questions the starting point for a reusable process.
01 / THE METHOD
Each step establishes the basis for the next.
The build method moves from observed customer work to a tested target process. Human interactions and approvals belong in the initial diagnosis.
Read the original method ↗01 / Identify
Understand the work.
Which outcome matters? Where does work stall? Which decisions and customer interactions stay with people?
02 / Minimize
Remove unnecessary work.
Question handoffs, waiting and duplicate capture. Keep what contributes to the outcome.
03 / Perfect
Make the process verifiable.
Define inputs, outputs, a verification rule and complete onward routes for every step.
04 / Augment
Assign work deliberately.
Code calculates. AI handles variable language and context. People retain judgement and approval where the work requires them.
05 / Construct
Write the target process.
The Application describes the reusable process in readable files: with instructions, an entry point and routes.
06 / Test
Test against real requirements.
Compare representative runs with a baseline: check the outcome, guardrails, throughput and failure cases.
07 / Scale
Reuse the tested revision.
New runs use the tested Application revision. Existing runs remain bound to their historical revision.
02 / THE PUBLIC CORE
A readable contract for the process.
The published core defines the file structure and validates its rules. A separate agent harness executes the work; capabilities provide tools and deterministic calculations.
- Application
- One main process with an embedded result contract: outcome, metric and acceptance criteria.
- Process step
- Inputs, outputs, verification and routes sit alongside the work instructions.
- Run
- A concrete run binds to an Application revision. Its path records the steps reached.
- Human approval
- A human gate has approval and rejection routes. The decision is recorded in the run.
A valid structure demonstrates conformity with the file contract. Domain quality and usefulness must be tested against the actual process.
03 / SOURCES & SCOPE
Read the source. Check the scope.
This introduction summarises the public repository revision. It describes the method and core; it does not establish customer outcomes or certification.
Melvinanalytics / impacts-protokoll
Source revision: 1a0cf9c92089