🔁 SKRSI
SKWorld · Incubating v3 · Apache-2.0

The improvement loop that cannot promote itself

SKRSI is the evidence-first improvement control plane for SK software lifecycle orchestration. It measures delivery, evaluates bounded experiments, records lessons, and proposes safer changes. Then it stops and hands the decision to somebody else.

Canonical expansion

SK Recursive Systematic Evaluation, Learning, and Feedback Improvement

Three things it will never do

Most "self-improving" systems fail in the same place: the thing that measures the work is also the thing allowed to approve it. SKRSI is built so that collapse is structurally impossible.

Never

Grant authority

A valid SKRSI record confers no merge, deployment, credential, or actuation power. Feedback is proposal-only, and it routes through the adopter's existing authorization gates.

Never

Approve its own work

Producer and independent evaluator identities must differ, enforced through an ordered, unique evaluation participant tuple. The measurer does not get to certify the measurement.

Never

Launder an observation

An observation does not become an actuation by passing through the system. An inconclusive experiment stays inconclusive, and no model, agent, or operator can relabel it as a success.

SELF, the operating loop

Four ordered stages. Each one constrains the next, and the order carries the guarantee.

  1. S

    Systematic

    Work from declared targets, cohorts, metrics, and stop rules. A target registers its own invariants, expiry, and rollback owner before anything is measured.

  2. E

    Evaluation

    Compare evidence without inventing causality or hiding missingness. A PASS needs numeric baseline and treatment values for every metric, no failed guardrail, and no explicit missingness entry.

  3. L

    Learning

    Preserve outcomes and lessons as versioned, attributable records. Failed and inconclusive runs are kept with the same care as successful ones, because those are the ones that carry information.

  4. F

    Feedback

    Route bounded proposals back to the responsible lifecycle agent. The existing gates stay authoritative. SKRSI never becomes the thing that says yes.

Where the evidence goes

Every edge has one producer, one consumer, a bounded queue, a timeout, a retry policy, a recovery owner, and immutable terminal evidence.

Public contracts

Metadata-only records, each declaring an exact schema URI. A consumer must reject unknown major versions, and must not infer authorization from a valid record.

ContractSchemaPurpose
Target target-v2 Registers a bounded objective with measures, invariants, stop rules, expiry, and a rollback owner.
Event envelope event-envelope-v1 Carries attributable metadata, lineage, hashes, and redaction class.
Evaluation evaluation-v3 Records independent participants, complete PASS metrics, quality gates, missingness, and an evidence-bound outcome.
Feedback handoff feedback-handoff-v1 Routes a proposal to an existing authority without granting permission to act.

Compatibility is deliberately strict

  • Every published schema identifier and file is immutable.
  • Any field addition, removal, type change, or constraint change requires a new schema identifier and file, even when the change looks additive.
  • Consumers process only explicitly supported exact schema identifiers. There is no same-identifier forward compatibility.
  • Unknown properties fail validation. Extensions belong in a new versioned contract.
  • Timestamps are RFC 3339 UTC. Digests are lowercase SHA-256 hex.
  • Identifiers are opaque, and must not carry credentials, protected content, personal filesystem paths, or private host names.

Conformance levels

Three cumulative levels. Each one contains the one before it, so a claim at the top implies everything below.

01

Record conformant

  • Every emitted record validates against its declared schema.
  • Unknown schema versions and unknown properties fail closed.
  • Digests, timestamps, required identities, and redaction classes are valid.
02

Evidence conformant

  • Exact source and evidence digests are reproducible.
  • Retries are idempotent, and conflicting replay is rejected.
  • Missing, negative, null, and aborted outcomes stay visible.
03

Lifecycle conformant

  • Producer and independent evaluator identities differ.
  • A PASS carries numeric baseline and treatment values for every metric, with no failed guardrail and no missingness entry.
  • Feedback is proposal-only and passes through the adopter's existing authority.
  • Stop, expiry, rollback, and recovery behavior is tested.
  • No valid record grants merge, deployment, credential, or actuation power.

Start here

Validate a checkout
git clone https://github.com/smilinTux/skrsi
cd skrsi
python3 -m unittest discover -s tests -v
python3 scripts/validate_public.py .