Skip to main content

CURATION DECISION · NOT A NEW CONTENT QUEUE

Seventeen candidates. Two pilots. One method to prove.

The audit categories measured different things. This plan turns them into one operating hierarchy and gives every build a destination. No build is deleted. No build receives a carousel merely because it has a number.

LOCKED NOW

Canva stays frozen.

2

complete pilots built first

15

other public candidates held behind evidence gates

98

builds receiving no new standalone slides yet

0

builds deleted or misrepresented as production AI

TIER 1 · BUILD NOW

Consensus launch pilots

  1. 01One precise question the prototype tests
  2. 02Exact users, actors and authority boundaries
  3. 03Primary sources and material counterevidence
  4. 04What the current code actually does
  5. 05Inputs, state changes, rules, outputs and failure paths
  6. 06What is synthetic, hard-coded, missing or prohibited
  7. 07Observed first-time-user testing and misunderstandings
  8. 08A literal materials-and-steps reconstruction guide
  9. 09Tests, accessibility checks and claim boundaries
  10. 10What a production version would require
  11. 11Three creative treatments before selecting a design system
  12. 12A release decision: publish, revise or stop

THE OTHER TWO INTELLECTUAL LEADERS

Method anchors, not launch episodes.

Builds 012 and 014 are intellectually strong and source-linked, but the external-value review did not find them distinctive enough to lead the public series. Their substance will strengthen the two pilots before either competes for its own release.

THE COMPLETE 17-CANDIDATE QUEUE

Compete for release; do not assume release.

BuildTreatmentRequired proof
001Human Review Design Frameworkpilot now

Consensus hero: human authority, evidence and stopping power are central to the RN method.

030Inclusive Experience Simulator & Repair Labpilot now

Consensus hero: inclusive repair is legible, interactive and directly connected to design practice.

009Place-Sensitive Technology Readinessevidence sprint

Place-sensitive transfer connects Hawaiʻi, implementation and Dutch field research.

017Regulated-Market Handoff Mapperevidence sprint

Institutional handoffs are distinctive, but the prototype needs real workflow evidence.

021AI Vendor Claim / Procurement X-Rayevidence sprint

AI vendor-claim scrutiny has immediate professional relevance and a clear evidence test.

045Cannabis Care Access Journeyevidence sprint

Cannabis access fits RN’s domain authority but requires real journey evidence and current sources.

046What Does This Island Depend On?evidence sprint

Island dependency is highly distinctive but must be grounded in actual infrastructure evidence.

048What Does This Rule Feel Like in Real Life?evidence sprint

The lived experience of rules is a strong RN proposition that needs observed human evidence.

059Is This Legal Citation Real, Current, and Saying What the AI Claims?evidence sprint

Citation verification directly connects law and AI, but must be tested against real citations.

069A Law Passed. Now What?evidence sprint

Implementation after enactment is a strong legal-systems story that needs a real law and timeline.

100Island Resilience Scenario & Decision Roomevidence sprint

A powerful capstone if presented as a bounded planning rehearsal—not a forecast or digital twin.

002Multi-Audience Meaning Architectureeditorial lab

Strong public explanation concept; prove truth-preserving translation with one real claim.

003Unserved Decision Discoveryeditorial lab

Strong discovery method; prove that it finds a real unserved decision.

006Does This Actually Deserve to Be Software?editorial lab

Useful product judgment; show one decision where refusing software was the correct result.

063Research That Stays Aliveeditorial lab

Promising knowledge infrastructure; demonstrate a real source changing a claim and output.

080Turn Reporting Into Public Infrastructureeditorial lab

Strong link to RN’s reporting practice; run it on one rights-cleared reporting packet.

083Turn Real Work Into Public Proof Without Leaking the Workeditorial lab

Strong portfolio mechanism; prove confidentiality and rights gates using one real cleared project.

THE 53 SUPPORT-OR-MERGE RECOMMENDATIONS

Modules inside larger stories.

These builds retain code, routes, provenance and build numbers. They lose the presumption of a standalone episode. The groups below cover all 53 intellectual support-or-merge recommendations.

EXPLICIT MERGE GROUP · LEAD 001

Give AI bounded work and governed memory

Collapse generic AI-team infrastructure into one inspectable authority, orchestration and proof architecture.

SUPPORT CLUSTER · LEAD 063

Build evidence that stays alive

Retrieval, lifecycle, comparison, consequence and translation become modules in a source-linked evidence system.

53/53 mapped. No support-or-merge record is orphaned.

TEN EXPLICIT CUTS

Cut the standalone episode—not the work.

026Messy Data Trust X-Ray
Build 030 story with 023, 024 and 031

Data cleaning is an implementation module, not a flagship story.

043Design an AI Team
Build 001 story with 042 and 092

Team design alone is too generic for a standalone episode.

REMAINING BUILDS

Preserve, repair or use as evidence.

RELEASE RULE

A build advances only when the evidence advances.

No fixed quota. No promise that all seventeen ship. The two pilots are built and tested first. Every later candidate must outperform them on truthfulness, technical clarity, RN distinctiveness, child-clear reproducibility, accessibility and visual force.

Source audits: GitHub commit 91aee9aba53ca050344f10948f3d9c9c5f030de8. This curation layer changes editorial treatment, not the preserved implementation record.

Return to the complete method audit