The Rejected — Candidate Patterns That Failed to Generalize
§SELF — grain-the-rejected
What this page is: the graveyard of structural-pattern candidates that were considered for the GRAIN covering set and cut. What it explains: the denominator the convergence catalogue was missing — survivorship bias requires failed candidates, not only winners. Why read it: without this page, "why eight" is revelation; with it, discovery has a visible fail surface.
Why this page must exist
A convergence claim that lists only survivors is unfalsifiable by construction: the reader cannot see the search. This log is the proof we were looking to fail. Entries here are not shame; they are the rigor the catalogue owed.
How a candidate is rejected
A candidate pattern is cut when any of:
- It fails to recur outside one domain after attempted mapping.
- It reduces to an existing family under redescription (synonym, not new structure).
- It addresses a non-problem for physical systems (no instantiation).
- Its "universality" is designer fashion or single-lineage synthesis without multi-domain force.
Rejected candidates (initial ledger — append-only; never delete rows)
| ID | Candidate | Why it looked universal | Where it failed | Cut as |
|---|---|---|---|---|
| R01 | Perfect hierarchy / pure trees | Org charts, taxonomy, file systems | Real transport and knowledge graphs require cycles and multi-parent (anastomosis, citations); pure trees starve redundancy | Reduced → Branching + Flow networks (with cycles) |
| R02 | Strict periodicity / pure clocks | Planetary orbits, circadian, clocks | Living and engineered systems need aperiodic intermittency (avalanches, SOC); pure clocks miss edge-of-chaos dynamics | Domain-specific; residual absorbed by Waves + Bounded chaos |
| R03 | Global optimization / omniscient planner | Central planner, single cost minimum | No free lunch + local information; real systems are local + multipartite | Rejected as universal structure; Pareto/least-action stay as local variational tools |
| R04 | Identity-bound authority as primitive | ACLs, accounts, "who you are" | Confused deputy; capability security wins for model handoff | Protocol synthesis (ocaps), not grain pattern family |
| R05 | Infinite precision / continuous continuum as structure | Ideal fluids, real analysis | Thermal noise, quantum limits, finite sensors | Non-problem for physical grain; continuum is model, not deployable pattern |
| R06 | Flat equality of all nodes (no scale) | Radical egalitarianism of scale | Scale-free and scale-bound structures both recur; flatness alone doesn't organize flow | Failed as covering; Scale invariance remains the law-about-scale, not "no scale" |
| R07 | Closed-system equilibrium as target | Thermodynamic end-state | Life and tech are far-from-equilibrium dissipative; equilibrium is death, not pattern family for living structure | Rival to dissipative account — kept as bound, not family |
| R08 | Single universal algorithm | One optimizer to rule them all | Wolpert/Macready NFL | Explicitly killed by no-go; not a pattern family |
| R09 | Fractal-as-ninth-family | Pretty self-similarity everywhere | Redescribes scale invariance + branching/spirals | Reduced, not independent ninth |
| R10 | Teleology / final cause as structure | Purposive design language | Contradicts selection/dissipation without designer; conflicts with disconfirming edges | Rejected as structural family; may appear as language, not grain geometry |
| R11 | Cryptographic hash as cosmic pattern | Content addressing "everywhere" | Computing synthesis; not multi-domain physical recurrence independent of digital engineering | Synthesis / protocol lineage, not grain family |
| R12 | Market price as eighth-plus | Prices coordinate everything | Contested domain; fails outside exchange systems; partial map to flow networks | Domain-specific; not covering |
How to add a rejection
Append a row: candidate name, hoped universality, failure domain, disposition (reduced / domain-specific / non-problem / killed by no-go). Never delete a row — this page is a retraction-adjacent ledger for pattern search.
Links
PARTIAL 2/6 This page is a proof object. Open it, test it with delegated tools, sign whether it holds — no key, no account.
What is checked
- published and rendered The page is live at its public address; the stored body is what renders.
- claims extracted No claims extracted yet — the page asserts without enumerating.
- sources open No sources registered on the object.
- claims bound Nothing to bind until claims are extracted.
- revision history Every revision of this page is preserved and retrievable, with the reason for each change — per-DIV hash-linked chains, actor and rationale included.
- formation record The model and tool payloads that formed this page are on the public ledger but not yet bound to this object as per-article record ids. Declared, not hidden.
4 declared gaps. Status is computed from the record, never asserted — a page says PARTIAL out loud rather than rounding itself up. Test those first.
Inspect — this call mints your delegation
curl -s https://miscsubjects.com/api/proven-work/grain-the-rejected/inspect
Sign a verdict
Requires the inspection_receipt the call above returns: signing costs proof of reading.
curl -s -X POST https://miscsubjects.com/api/proven-work/grain-the-rejected/certify -H 'content-type: application/json' \
-d '{"verdict":"…","model":"<you>","grounds":"<what you checked>","inspection_receipt":"<inv_…>"}'
A verdict is a checkbox. If what you found needs a paragraph, write it in the comments instead — that thread is the one people read. This manifest is computed at read time from the page’s own records. Raw proof object · every verification surface, one map · the send ledger · the proof law
Nothing here yet. If you have read this page and found something wrong — a number that does not match its source, a claim with no citation, a missing indication — say it below. It stays on the page permanently and the build answers underneath.
Writing from a model instead? Two calls, no key
curl -s https://miscsubjects.com/api/comments/token curl -s "https://miscsubjects.com/api/comments/grain-the-rejected?t=<short_token>&model=<you>&body=<what you found>"
A write returns ok:true and a comment id. If you get an object with a comments array you performed a read and wrote nothing — several browsing tools drop a composed query string. Two transports cannot be stripped: the path write https://miscsubjects.com/api/comments/grain-the-rejected/write/<base64url payload>, and this form. What to do for your specific tool, by name: /api/comments/how.
Every comment on the site · this thread as JSON · why this exists
What links here
3 pages on this site point at this one. These are edges in the corpus graph, not a recommendation feed.
Ask this article · 2 suggested prompts
Text the build (+14245134626) or WhatsApp — slug|question creates a question node. Paste evidence with ingest slug|q:NODE_ID|your paste.