SPM·STANDARDS
INSTITUTE

FIELD EVIDENCE / WORKED CYCLES

From claim
to inspectable cycle.

A worked cycle takes one bounded task from objective to result and shows what a reader needs to judge it: who decided, who did what, what went wrong, what was corrected and what the evidence does not show.

Draft structure · case text in preparationNothing below is a finding yet

HOW TO READ A CYCLE

Every statement
carries its status.

Each fact in a cycle is labelled by how it is known.

Reported
The responsible participant describes the result, scope and evidence.
Author-tested
The author ran a method and recorded environment, inputs and observations.
Independently checked
A reviewer who did not build the work checked the claim against inspectable evidence.
Illustrative
An invented example that explains a control. It is never evidence.

An internal proof of concept does not establish what a newcomer learns from the protocol. That needs its own pilot.

CYCLE 01 · PROPOSED

Archive and source handoff,
with a checked delivery.

Objective
To be written.
Human decision
To be written.
Roles assigned
To be written.
Observed deviation
To be written.
Correction
To be written.
Result
To be written.
Evidence
To be written. A short public-safe extract.
Limitation
To be written.
CYCLE 02 · PROPOSED

Context and role continuity
across a change of engine.

Objective
To be written.
Human decision
To be written.
Roles assigned
To be written.
Observed deviation
To be written.
Correction
To be written.
Result
To be written.
Evidence
To be written. A short public-safe extract.
Limitation
To be written.
CYCLE 03 · PROPOSED

Reconciliation
and recovery.

Objective
To be written.
Human decision
To be written.
Roles assigned
To be written.
Observed deviation
To be written.
Correction
To be written.
Result
To be written.
Evidence
To be written. A short public-safe extract.
Limitation
To be written.
CYCLE 04 · PROPOSED

Spoken intent
to working software.

Instruction given
To be written. The spoken or typed instruction.
Implementation
To be written. What the AI orchestrator produced.
Operator decision
To be written. Approval or change of direction.
Test result
To be written.
Correction
To be written.
Accepted disposition
To be written.
Evidence
To be written. A short public-safe extract.
Limitation
To be written.

WHAT WILL AND WILL NOT BE PUBLISHED

Public-safe evidence.
Attributed contributions.

Each cycle will name the human operator and the AI orchestrators involved. Credentials, private customer information and private conduct material are never published. Where a cycle needs a record, it uses a short extract that is safe to read.

Want to see the method on your own work? Start a bounded task of your own.

Create your Zero ↗