System / public projection

The sum of what you save.

Sources become signals. Stable owners change only through named loops, versioned workflows, exact authority, and proof.

Architecture JSON API

Goals

6

measurable promises

Workflows

14/16

ready command contracts

Owners

192

stable write targets

Reviews

3295/3376

final source decisions

GoalsOperations / change view

01 / durable outcomes

What the system is trying to make true

Goals govern loops. They are measurable promises, not a second task list.

G01active

Compound every useful signal

Every saved source becomes replayable evidence and every useful signal interrogates at least one durable owner.

  • No source is counted as integrated only because it appears in a report.
  • Every extracted signal is object-bound or carries an explicit blocker.
  • Every change verdict has a writeback and retrieval or routing proof.
G02active

Keep one inspectable system truth

The wiki, registries, agent interfaces, API, and public system view describe the same current state.

  • Generated projections include their source digest.
  • Doctors fail on broken references, phantom capabilities, or stale projections.
  • Public surfaces expose honest readiness and completeness states.
G03active

Turn intent into proof-carrying work

Any agent can route a job into a bounded workflow with explicit context, authority, execution, proof, and writeback.

  • A workflow can explain every loaded object and capability.
  • Completion claims name independently inspected proof.
  • Repeated corrections update the workflow rather than remaining chat advice.
G04active

Encode taste as reusable constraints

Design references and preferences become inspectable rules, fixtures, project requirements, and visual proof.

  • Visual sources retain their artifact and the quality they demonstrate.
  • Design changes are compared against named rules and fixtures.
  • Motion, accessibility, responsiveness, and performance are proven in a browser.
G05active

Realize the product program

Project instructions from Discord, X, and the wiki become sequenced, testable product slices instead of dormant notes.

  • Every active project has a current owner, next slice, acceptance proof, and reversal path.
  • Project instructions retain source provenance.
  • The public system view distinguishes specified, implemented, verified, and shipped.
G06active

Make the system challenge itself

New evidence and run outcomes continuously test whether instructions, workflows, skills, and architecture should change.

  • Contradictory evidence creates a visible challenge rather than being flattened.
  • No-change decisions include current-owner comparison and digest.
  • System changes are evaluated against holdout sources and run proof.