The Sieve Problem: Project Charter and Development Status

A developing project on how institutions preserve the language of their commitments while allowing harmful conditions to recur through accepted procedures.

Development charter v0.1 · 20 June 2026

The recovered source is a treatise charter, not a completed treatise. It is available here so the project has a meaningful reading and status destination. A completed integrated Sieve manuscript has not been recovered. The related partial article and The Audit remain distinct works.

Download this edition (PDF)

Contents
  1. Project Charter — Treatise Track

Project Charter — Treatise Track

Project Title

The Sieve Problem: A Treatise on Protected-Condition Regression

Possible subtitle:

How Harm Passes Through Systems Built to Deny It

Author: Christopher Knorr
Prepared: 2026-06-20, America/Los_Angeles
Status: Planning / treatise architecture v0.1

1. Scope

This project is the full-system work. It is not a single article. It is the treatise-level account of how societies, institutions, and normative orders preserve the language of freedom, dignity, democracy, equality, safety, personhood, or sovereignty while allowing condition-damaging harms to recur through accepted pathways.

The scope includes:

  • theory of harm;
  • protected conditions;
  • institutional passage;
  • regression and devolution;
  • mechanisms of recurring harm;
  • relation-sensitive responsibility;
  • answerability and correction;
  • metrics and audit pathways;
  • applications across the corpus.

The scope excludes:

  • claiming final authority over all harms;
  • claiming to replace existing fields;
  • treating every discomfort or loss as protected-condition harm;
  • turning affected people into case examples without correction authority;
  • editing frozen works such as PRS v5.9 directly.

2. Major Purpose

To name and theorize the recurring failure by which systems claiming to uphold high normative commitments allow condition-damaging harms to pass through their own accepted forms.

3. Minor Purposes

  1. Define The Sieve Problem.
  2. Define protected-condition regression.
  3. Explain why formal commitments do not guarantee real protection.
  4. Identify the mechanisms that let harm pass through.
  5. Build a condition-centered theory of harm.
  6. Show how existing theories partially address but do not fully organize the problem.
  7. Gather your existing works into a single architecture.
  8. Create a bridge from theory into metrics, audit, and repair.

4. Central Claim

A system is not vindicated by the values it announces. It must be judged by whether its ordinary operations protect or degrade the conditions required for those values to be real.

5. Working Definition

The Sieve Problem is the recurring failure of a normative or governing order to prevent harms that contradict its own stated commitments because those harms pass through accepted procedures, categories, exceptions, records, narratives, or institutional routines as if they were legitimate.

Protected-condition regression occurs when a system preserves the language of a value while degrading the conditions required for that value to be meaningfully exercised.

6. Why This Is Treatise-Weight

This is treatise-level because it must answer all of the following:

  • What counts as harm?
  • What conditions make freedom or agency real?
  • How do systems permit harms they claim to oppose?
  • Who is harmed, who is implicated, who benefits, who decides, and who repairs?
  • What have existing traditions already said?
  • Why are existing responses insufficient?
  • How can the framework be tested?
  • What metrics or audits can identify regression?
  • How can institutions be used without trusting them too much?

7. Proposed Treatise Parts

Part I — The Problem

Name the Sieve Problem and show why it recurs.

Part II — Harm as Damaged Condition

Develop harm beyond direct injury, pain, or visible violence.

Part III — How Harm Passes Through

Mechanisms: administrative thinning, security laundering, formalism, non-injury denial, recursive cascade, exception drift, institutional capture, closure without correction.

Part IV — Existing Responses and Their Limits

Engage rights theory, liberal liberty, non-domination, structural injustice, solidarity, care ethics, recognition theory, epistemic injustice, democratic theory, capability theory, and transitional justice.

Part V — The Protected-Condition Model

Define domains, thresholds, actor roles, passage traces, relation-sensitive obligations, answerability, and repair.

Part VI — Metrics and Audit

Turn the theory into a diagnostic method.

Part VII — Applications Across the Corpus

Apply to Agency First, Protected Conditions, PRS, The Audit, Shoreline, Provenance Trace, tax plan, public governance, family care, and public/community infrastructure.

8. Corpus Inputs

Corpus work Function in treatise
Three Pillars Governance value anchor: anti-violence, economic stability, infrastructure resiliency.
Canonical Freedom Architecture Freedom as layered, anti-dominating, meaningful action under real conditions.
Protected Conditions Direct source for condition damage, thresholds, cascade, repair matching.
The Audit / LBCA Method for claim answerability and correction.
People-Rooted Sovereignty Peoplehood, authority, corrigibility, non-capture, living governance.
Agency First Non-conscription, refusal, agency across time, moral weight without domination.
Shoreline Framework Information/record ecology; access is not authority; AI as mediator not record.
Provenance Trace Supply-chain/source-chain trace method; known/contested/null distinctions.
Cascade Trace Mechanism for harms moving through records/systems.
American Tax Plan Applied public-return and economic-governance case.
Pit River Check-In / Long Return Public/community infrastructure and living information practice.
Fractured Authority/Gaza Condition-control, actor-function mapping, evidence ledger use.

9. Development Phases

  1. Problem Map v0.2 — 3–5 pages.
  2. Term Sheet v0.1 — definitions and boundaries.
  3. Corpus Slot Map v0.2 — works-to-parts table.
  4. Mechanism Map — how harms pass through.
  5. Literature Field Map — external scholarly neighbors.
  6. Treatise Outline v0.1 — parts, chapters, sections.
  7. Zero Draft — full rough draft.
  8. Internal Audit — using the ten questions plus claim-ledger discipline.
  9. v0.2 Repair Draft — revised after audit.
  10. External Handoff Brief — for collaborators/readers.

10. Success Criteria

The treatise succeeds if it can:

  • name a real recurring problem;
  • explain why existing vocabularies miss part of it;
  • organize your corpus without flattening it;
  • produce testable audit criteria;
  • avoid overbreadth;
  • preserve affected-party answerability;
  • make the framework useful beyond one case.

11. Risk Register

Risk Repair
Overbreadth: harm means everything Add threshold harm test.
Sprawl: every corpus work enters everywhere Use corpus as control system, not content dump.
Rights-language takeover Keep rights theory as interlocutor, not foundation.
Institutional overtrust Require no-self-validation and correction routes.
Saviorism / appropriation Preserve affected-party correction authority.
Pseudo-metrics Mark calibration as calibration, not validation.
Treatise never becomes draft Use phased gates with concrete deliverables.

Related reading

Project question and status · Browse papers and reports · Inheritance Library