Islands of Coherence

Diagnostic Cases

These are not critique pieces aimed at the named entities. They are diagnostic instruments. The criterion is meant to catch specific patterns that travel under decorative vocabulary. When the criterion actually catches one, the case is worth holding visibly as a documented example of the discipline working.

Each case below names a structural pattern the criterion is designed to surface, not a moral judgment of the named entity. The cases are held in the audit's working files; surfaced here as transparent examples of what the criterion's tests actually do under pressure.

Case 1 — Vocabulary contamination at canonical-lineage altitude

Worked entity: Las Salinas, Chile (Empresas Copec brownfield real-estate redevelopment using Regenesis Group's Story-of-Place methodology).

Pattern the criterion catches: when canonical regenerative-design vocabulary travels into work that operationally contradicts the lineage's claims, the criterion reads the gap visibly. Decorative use of relational vocabulary by an unrelated entity is one failure mode; canonical lineage vocabulary applied to extractive substrate by the lineage itself is a sharper structural critique. The vocabulary is not being misappropriated — it is being placed in service of work that the lineage's own discipline should refuse.

What the criterion reads:

The criterion's call: FAIL. The relational vocabulary is decorative against the substrate — and more sharply, the canonical lineage's vocabulary is decorative against the substrate. The structural critique the criterion is built to surface is not "the project uses relational language without meaning it." It is "the canonical lineage of regenerative design has applied its own vocabulary to corporate-extractive substrate, and the field's vocabulary ripples contamination forward."

Why this case matters. The criterion's claim — let latent care be load-bearing — depends on a clean signal between structural-relational work and decoration. The decoration case is well-understood. The contamination case is the harder one. When the lineage's own working canon (Regenesis Group, Designing Regenerative Cultures, the Brewer / Mang / Reed / Sanford framework) is the vocabulary being applied to extractive substrate, the field's discipline becomes more, not less, important. The criterion's job is to catch this without becoming a court that prosecutes the lineage. The case stays in the audit's working files; the pattern is named publicly.

Case 2 — Substrate-form mismatch as a clean structural fail

Worked entity: Pioneer Works, Brooklyn (a well-resourced 501(c)(3) cultural institution at the art-science intersection, founded by Dustin Yellin).

Pattern the criterion catches: an entity can be values-aligned, well-resourced, structurally durable, and substantively important to its sector — and still fail the criterion structurally because it does not stake a relational-ontology claim. The criterion is built to test whether a stated relational claim is load-bearing. When no such claim is stated, the criterion's test apparatus does not run, and the entity reads as FAIL not because the work is wrong but because the work is not what the criterion measures.

What the criterion reads:

The criterion's call: FAIL. Not because the entity is doing damaging work or has a misaligned mission. Pioneer Works does substantial cultural work. The criterion's test cannot read the entity because the entity does not present itself as relational-ontology-staking. The criterion is the wrong instrument for this entity. The map's discipline is to read what the entity claims and to test the claim structurally; where no claim of the right shape is made, the map does not have a structural reading to offer.

Why this case matters. The criterion is not a values-rank. An entity can pass the criterion and still be doing damaging work in a constrained context. An entity can fail the criterion and still be doing valuable work in its own register. The Pioneer Works case is the clean other-end demonstration: a well-resourced, values-respected entity that the map cannot include not because the work is wrong but because the work is not staking the kind of claim the criterion is built to read. Naming this is structurally honest. Hiding it would compromise the discipline the criterion exists to hold.

What these cases together teach

The criterion has two failure-detection registers, and the two cases above demonstrate them at maximum density:

  1. Vocabulary contamination — the lineage's own vocabulary applied to substrate the lineage's discipline should refuse. The criterion catches this as structural-relational claim contradicted by extractive substrate. Las Salinas is the worked case.
  2. Substrate-form mismatch — the entity is values-aligned and durable but does not stake a relational-ontology claim. The criterion catches this as test-not-applicable; the entity does not enter the map. Pioneer Works is the worked case.

These are not failures of the entities. They are demonstrations that the criterion does what it claims. A field map that catches neither pattern would be either too lax (everyone passes who uses the right vocabulary) or too strict (good work in adjacent registers is forced through a frame that does not fit). The criterion's job is to hold both honestly.

The audit's working files at evaluations/criterion-readings/ carry the specific case-by-case readings against the criterion's six tests. The patterns surfaced above are the field-level diagnostic insights the curator carries forward.

Diagnostic cases compiled from the v3 audit cycle. Worked entities are named; the writing is about the pattern, not the entity.