# IMPACTS Protocol: from workflow to verifiable process

> Source: https://aprixity.run/en/impacts-protocol

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.

[Read the seven steps ↓](#method)[Public repository ↗](https://github.com/Melvinanalytics/impacts-protokoll)

FROM DAILY WORK TO PROCESS

1.  **Observed work**The starting point remains source evidence.
2.  **Application**The improved process is described for reuse.
3.  **Run**A concrete case follows a specific revision.

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 ↗](https://github.com/Melvinanalytics/impacts-protokoll/blob/1a0cf9c920897083a6dd4ed13fffc7693857a6cf/02_protocol/impacts-method.md)

1.  I
    
    01 / Identify
    
    ### Understand the work.
    
    Which outcome matters? Where does work stall? Which decisions and customer interactions stay with people?
    
2.  M
    
    02 / Minimize
    
    ### Remove unnecessary work.
    
    Question handoffs, waiting and duplicate capture. Keep what contributes to the outcome.
    
3.  P
    
    03 / Perfect
    
    ### Make the process verifiable.
    
    Define inputs, outputs, a verification rule and complete onward routes for every step.
    
4.  A
    
    04 / Augment
    
    ### Assign work deliberately.
    
    Code calculates. AI handles variable language and context. People retain judgement and approval where the work requires them.
    
5.  C
    
    05 / Construct
    
    ### Write the target process.
    
    The Application describes the reusable process in readable files: with instructions, an entry point and routes.
    
6.  T
    
    06 / Test
    
    ### Test against real requirements.
    
    Compare representative runs with a baseline: check the outcome, guardrails, throughput and failure cases.
    
7.  S
    
    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.

-   [README ↗](https://github.com/Melvinanalytics/impacts-protokoll/blob/1a0cf9c920897083a6dd4ed13fffc7693857a6cf/README.md)
-   [Build method ↗](https://github.com/Melvinanalytics/impacts-protokoll/blob/1a0cf9c920897083a6dd4ed13fffc7693857a6cf/02_protocol/impacts-method.md)
-   [Minimaler IMPACTS-Core V1 ↗](https://github.com/Melvinanalytics/impacts-protokoll/blob/1a0cf9c920897083a6dd4ed13fffc7693857a6cf/docs/superpowers/specs/2026-08-30-minimal-core-design.md)
-   [Apache License 2.0 ↗](https://github.com/Melvinanalytics/impacts-protokoll/blob/1a0cf9c920897083a6dd4ed13fffc7693857a6cf/LICENSE)

Melvinanalytics / impacts-protokoll  
Source revision: [1a0cf9c92089](https://github.com/Melvinanalytics/impacts-protokoll/commit/1a0cf9c920897083a6dd4ed13fffc7693857a6cf)

## Which process needs clarity first?

Start with the bottleneck in your work.

[Assess your bottleneck →](/en/bottleneck-check)[More about the Aprixity method →](/en/methodology)