PRAXIS

PRAXIS is the measurement protocol for the AXIS efficiency claim. It defines how to test whether AXIS-governed exchanges produce fewer correction loops, shorter completions, and lower token usage than unstructured equivalents, under controlled, reproducible conditions.

It is not a product, not a service, and not a certification. It is a defined test format. Any operator can run it. The methodology is intentionally simple so that results can be compared across different operators, models, and task types.

The claim PRAXIS tests: structured prompts reduce drift, retry loops, and token waste compared to unstructured equivalents. Token reduction may correlate with compute efficiency under specified conditions, but PRAXIS does not claim energy savings as a guaranteed outcome. It measures what is directly observable: token counts, completion length, retry rate.

A PRAXIS test requires two runs of the same task, one unstructured (baseline), one AXIS-governed. Everything else is held constant: the model, the task, the context, the evaluation criteria.

For a PRAXIS test to be valid, the task must be reproducible. That means:

The task is defined before either run begins. Success criteria are written down before any output is seen. The same model is used for both baseline and AXIS-governed runs, at the same temperature settings. The context window starts fresh for each run, no carry-over. Results are logged verbatim, not summarised from memory.

Any operator can run a PRAXIS test using their own tasks and their preferred AI. Results should be shared with the task definition, model used, and both full transcripts, not just the summary metrics.

PRAXIS is in active development. The framework described here is the current working version, it has been used in informal testing and has produced consistent directional results. It has not yet been independently verified or peer-reviewed.