SYSTEM ERRORSOFTWARE / BERLIN

System Error Worldwide / v0.1.0

THE
LOOP.

One portable agent workflow across five coding tools.

Thirty-one complete portable skills for Codex, Claude Code, Kimi Code, OpenCode and DeepSeek Harness. One contract covers setup, capability routing, bounded autonomy, evidence and clean handoff.

Get THE LOOP on GitHub ↗︎ Quickstart

Open source, MIT licensed and local-first. Created and maintained by Moses Mawila through System Error Worldwide. No hosted account, model lock-in, prompt capture or client telemetry is required.

Release

31 shipped skills

Codex

Verified

Claude Code

Verified

Kimi Code

Verified

OpenCode

Verified

DeepSeek Harness

Verified

01 / Workflow

From clear scope to verified result.

THE LOOP moves one project through six visible stages. Each stage has a purpose, a finish condition and a clear handoff to the next.

  1. 01

    Strategize

    Define the problem, scope, constraints and success criteria.

  2. 02

    Spec-pack

    Write the product, technical and delivery plan before building.

  3. 03

    Build

    Complete one approved piece of work without disturbing anything else.

  4. 04

    Test

    Run reproducible checks and record every issue that remains.

  5. 05 ↺ 04

    Resolve

    Fix the issues, rerun the checks and repeat when needed.

  6. 06

    Close

    Record the final result, remaining limits and next safe action.

02 / Quickstart

Inspect first. Then install.

Setup starts read-only. It shows the harnesses, destinations, collisions and exact file operations before anything changes.

Safe installation sequence

git clone https://github.com/System-Error-Worldwide/the-loop.git
cd the-loop

# Read-only install plan
python3 scripts/the_loop_setup.py \
  --target-root /path/to/project \
  --harness codex \
  --json

# Apply the reviewed plan
python3 scripts/the_loop_setup.py \
  --target-root /path/to/project \
  --harness codex \
  --apply \
  --actor local-user \
  --source-version 0.1.0 \
  --json

# Verify the installed pack
python3 /path/to/project/.the-loop/toolkit/scripts/the_loop_doctor.py \
  --project-root /path/to/project \
  --json
GITHUB UNAVAILABLE What if the repository link fails?

Retry the canonical repository. Do not install a mirror or private copy unless its revision and provenance match the official release.

INSTALL ERROR Setup found an existing file

Stop before overwrite. Review the dry-run operation, inspect Doctor's winning precedence and approve only the exact intended change.

SKILL COLLISION Two packages use the same name

Treat file discovery and behavior as separate facts. Doctor must show both locations, the winner, permission limits and the corrective action.

UNSUPPORTED HARNESS The behavior check did not run

Keep the result UNVERIFIED or UNSUPPORTED. Use a documented target harness or wait for dated conformance evidence. Never invent an adapter.

03 / Operating modes

Bounded first. Broader only after proof.

Setup and Doctor install and verify the pack. Loop, Auto, Parallel, Cloud and Endless are all shipped v0.1 modes. Their supervision model changes; the safety invariants do not.

SHIPPED / v0.1

Setup + Doctor

Plan exact file operations, preserve unknown files, then report roots, collisions, permissions, discovery and behavior separately.

SHIPPED / v0.1

Loop

The attended default. Meaningful gates stay visible while one asset moves through the lifecycle.

SHIPPED / v0.1

Auto

One declared asset to green or a configured gate. It never selects an endless stream of work.

SHIPPED / v0.1

Parallel

Independent lanes with disjoint leases and one integration owner. Shared-file work remains sequential.

SHIPPED / v0.1

Cloud

Restricted or remote planning, drafting and handoff without private infrastructure assumptions.

SHIPPED / v0.1

Endless

Runs an approved queue as a series of bounded Auto missions. It never invents work, and every mission keeps time, token, action, attempt and cost limits.

04 / Complete portable pack

All 31 skills ship in v0.1.

All 31 skills are complete and included in v0.1. They are grouped by what they help you do: install and control, run different modes, manage the build lifecycle and hand work off cleanly.

Install + control / 07

  • the-loop-setup
  • the-loop-doctor
  • the-loop-skill-planner
  • the-loop-skill-creator
  • the-loop-autonomy
  • the-loop-control
  • the-loop-watch

Operating modes / 05

  • the-loop
  • the-loop-auto
  • the-loop-parallel
  • the-loop-cloud
  • the-loop-endless

Lifecycle + feeders / 08

  • strategize
  • spec-pack
  • build
  • test
  • resolve
  • health-check
  • audit
  • portfolio-review

Grounding + handoff / 11

  • live-state-preflight
  • idea-to-brief
  • stack-summary
  • bootstrap-agent-context
  • pre-commit-review
  • feature-tracker
  • decision-log
  • handoff
  • retrospective
  • session-summary
  • close

05 / Skill selection

Use the best available skill.

THE LOOP checks which compatible skills are already installed. When a qualified specialist is available, it uses it. Otherwise the bundled System Error fallback keeps the workflow moving under the same safety rules.

What the task needs

Required capability

  • Can complete the current stage
  • Works with the active harness
  • Available with the required permission
  • Has current behavior evidence

WHEN AVAILABLE

Installed specialist

Used when an installed skill meets the task and safety requirements.

ALWAYS INCLUDED

Bundled fallback

Used when no installed specialist qualifies. The output and safety rules stay the same.

Installed specialists stay in their maintained source. THE LOOP uses them when available but does not copy their code or instructions into the bundled pack.

06 / Authority and recovery

More authority never means less evidence.

Default authority covers local, reversible work inside the declared asset. Outward actions, strategy expansion and self-modification require exact, visible permission.

Levels

  1. Attended: confirm meaningful gates.
  2. Bounded: local reversible work inside one mission.
  3. Scoped: exact confirmed permissions only.
  4. Operational: named operations with expiry.
  5. Full: broad only where explicitly confirmed.

Permanent invariants

  • visible_authority
  • audit_log
  • evidence_required
  • run_ownership
  • leases
  • external_kill_switch
  • faithful_failure
  • no_silent_elevation

External stop

.the-loop/STOP

Detection prevents the next mutation. Removing the file never silently resumes work; explicit resume, a current grant and a fresh lease are required.

07 / Compatibility

Five harnesses. One portable contract.

One canonical skill source, thin harness adapters and the same status, authority, evidence and failure vocabulary in every supported environment.

THE LOOP v0.1 harness compatibility.
Harness Version Adapter Install Discovery Invocation
Codex 0.144.1 INCLUDED VERIFIED VERIFIED Select or mention $the-loop
Claude Code 2.1.221 INCLUDED VERIFIED VERIFIED /the-loop
Kimi Code 0.36.1 INCLUDED VERIFIED VERIFIED /skill:the-loop
OpenCode 1.15.1 INCLUDED VERIFIED VERIFIED Load skill(the-loop)
DeepSeek Harness 0.1.0-rc.6 INCLUDED VERIFIED VERIFIED /the-loop

08 / Two tracks, one evidence contract

Code and non-code finish by the same rule.

Both tracks declare the asset, route, evidence, issue, resolution and limits. The contract changes by track; the completion rule does not.

EXAMPLE / CODE

Add a deterministic slug validator to a Python utility.

Asset
feature/slug-validator
Gate
One function, isolated branch, focused and full Python suites green.
Route
Installed specialist rejected after a stale behavior probe; bundled Build selected.
Evidence
Focused test fails before implementation, then focused and full suites pass.
Issue
An overlapping dirty file would make ownership ambiguous.
Resolve
Halt without widening scope; resume only from a clean owned branch.
State
COMPLETE, no deployment performed.

EXAMPLE / NON-CODE

Produce a one-page community workshop decision brief.

Asset
docs/workshop-decision-brief.md
Gate
One page, three supplied notes, factuality and format review.
Route
A qualified research specialist handles source checks; bundled writing preserves structure.
Evidence
Every factual statement maps to the provided source packet.
Issue
A required fact is absent from all three notes.
Resolve
Mark the gap clearly and halt before publication or invention.
State
COMPLETE WITH LIMITATION, nothing sent externally.

09 / Provenance and trust

Public by construction.

Every shipped file has a public provenance record, a compatible licence and a review trail.

Provenance

Built from public, reviewable sources.

The pack contains System Error originals, clean-room rewrites and approved upstream dependencies. Each shipped file is classified and traceable.

Licence

System Error originals and clean rewrites are MIT.

All System Error original and clean-room rewrite work in the public repository is MIT licensed. Third-party dependencies keep their own licences and are included only with an approved provenance record.

Privacy / default

No telemetry. No prompt capture. No client tracking.

This page adds no cookies, analytics, external fonts or event collection.

Read the source contract

Follow the public repository.

Install the current release, inspect the protocol and verify every capability claim against its public evidence.

Open GitHub ↗︎