DEPENDENCY-ORDERED DEVELOPMENT

Build what the next discovery must be able to trust.

Priority follows dependency and risk—not excitement. A later stage may inspire work now, but it cannot claim maturity until its enabling gates are satisfied.

Immutable boundary

No site improvement may silently alter evidence, governing intents, contributor attribution, or an established Recovery Point.

Completion rule

“Implemented” requires a successful pre-change check, a bounded change, a successful post-change check, and a recoverable release.

NOW

Protect continuity

Make every later change recoverable, attributable, and testable.

STAGE GATEA clean build, route inventory, dependency record, rollback point, and named owner exist.

P01

Automated route and link integrity checks

Depends on: None
Development hook: Run before and after every bounded change

Propose work

P02

Versioned maintenance manifest

Depends on: P01
Development hook: Update when software, access, limits, or assumptions change

Propose work

P03

Public change and deprecation register

Depends on: P01 + P02
Development hook: Record replacement path before removing behavior

Propose work

MNT01

Dependency-verified development queue

Depends on: P01–P03 + maintenance registry
Development hook: Reconcile priorities whenever an implementation state, gate, environment, reviewer, or operating dependency changes

Propose work

UX06

Usability evidence cycle

Depends on: UX01–UX05 + P01 + deliberate feedback
Development hook: Re-run after route, audience, accessibility, device, browser, dependency, platform, or task-boundary changes

Propose work

Broaden safe participation

Let newcomers and specialists contribute at an appropriate level without flattening differences in evidence quality.

STAGE GATEEvery entry path identifies expected output, evidence burden, privacy boundary, and destination.

EDU01

Guided student development workspace

Depends on: UX01–UX03 + P04–P06
Development hook: Keep accounts, messages, uploads, and student submissions disabled while educators review grade bands and examples

Propose work

EDU01S

Minor-interaction safety contract

Depends on: EDU01 + P14 + P18B–P18E
Development hook: Re-run approved-domain and safety-contract checks whenever student links, roles, privacy expectations, or interactions change

Propose work

P04

Role-sensitive onboarding and examples

Depends on: P02
Development hook: Review when audience failures or new contributor groups appear

Propose work

P05

Contribution classification and integrity gates

Depends on: P03 + P04
Development hook: Escalate incomplete submissions to clarification, not integration

Propose work

P06

Mentored replication pathways

Depends on: P04 + P05
Development hook: Open only when a method has reproducible instructions

Propose work

P20A

Significant contributor recognition

Depends on: P03 + P05 + P09 + P14
Development hook: Add a name only after evidence, review, significance, consent, attribution-order, privacy, correction, and withdrawal gates pass

Propose work

THEN

Strengthen relational evidence

Expose dimensional gaps and correlations without converting visual or statistical proximity into ontology.

STAGE GATEEvery candidate relation retains source, detector, frame, null world, counterexplanation, and confidence history.

P07

Machine-readable scalar and relationship registry

Depends on: P02 + P05
Development hook: Re-index when a term, frame, or mapping changes

Propose work

P08

Conflict-preserving evidence graph

Depends on: P07
Development hook: Branch when claims cannot be reconciled without information loss

Propose work

P09

Independent replication and negative-result index

Depends on: P06 + P08
Development hook: Re-score only from traceable evidence

Propose work

LATER

Test operational usefulness

Move from characterization toward safe, bounded manipulation of actual physics in ways not otherwise available.

STAGE GATEPredictions, controls, failure limits, reversibility, safety review, and conventional comparisons are explicit before intervention.

P10

Candidate intervention sandbox

Depends on: P08 + P09
Development hook: Stop automatically when safety or reversibility bounds fail

Propose work

P11

Cross-instrument and cross-site trials

Depends on: P10
Development hook: Advance only after independent protocol review

Propose work

P12

Operational utility register

Depends on: P11
Development hook: Separate demonstrated utility from claims about fundamental existence

Propose work

EXP01

Experimental research development register

Depends on: P01–P03 + P10 + P11
Development hook: Advance portable software-only foundations; stop at identity, safety, institutional, storage, reviewer, and evidence gates

Propose work

HORIZON

Scale without capture

Support global, multi-AI development while preventing one institution, model, vocabulary, or funding source from controlling the commons.

STAGE GATEGovernance, formats, verification, and recovery remain portable across vendors, jurisdictions, and generations.

P13

Model-agnostic prompt and data exchange

Depends on: P07 + P09
Development hook: Compatibility test on every major model or schema change

Propose work

P14

Distributed stewardship and appeal process

Depends on: P03 + P13
Development hook: Rotate authority; preserve named dissent

Propose work

P15

Long-duration knowledge and life-propagation research

Depends on: P12 + P14
Development hook: Require ecological, cultural, safety, and anti-homogenization review

Propose work

ACTIVE

Build bounded public instruments

Turn registered relationships into reproducible comparison tools without presenting simulations or visual proximity as evidence of Actual Physics.

STAGE GATEEvery run exports its inputs, versions, baseline, null world, assumptions, limits, uncertainty, and failure state; unsafe stages remain blocked.

P16

Online multidimensional comparison simulator

Depends on: P07 + P08 + P10 + P13
Development hook: Revalidate schema, fixtures, compute ceiling, cancellation, accessibility, and isolation whenever a method or platform changes

Propose work

P17

Accessible multidimensional presentation

Depends on: P07 + P08 + P16 schema
Development hook: Advance from the current graph/table/export foundation only after zoom, provenance, uncertainty, keyboard, touch, and reduced-motion checks pass

Propose work

P18

Research discussion forum

Depends on: P04 + P05 + P13 + P14
Development hook: Bounded adult beta active: public reading, authenticated submission, private profile and queue, explicit following and mute controls, owner prepublication moderation, reports, withdrawal, and export

Propose work

P18F

Working research-thread runtime

Depends on: P18A–P18E + P17
Development hook: Revalidate thread and reply schemas, authorization, screening, rate limits, moderation, withdrawal, reports, exports, and scientific boundaries on every change

Propose work

P18I

Profiles, following, and link-safety foundation

Depends on: P18F + ChatGPT identity + D1 storage
Development hook: Preserve opt-in-only following, account-email non-disclosure, hierarchical mute overrides, non-clickable pending links, safe rendering, and moderator non-override; keep email delivery and link-provider activation staged

Propose work

EXP03A

Experiment-stage discussion bridge

Depends on: EXP03 + P18F
Development hook: Preserve E0–E8 labels as discussion metadata only; never treat them as preregistration, execution authority, evidence, review, or claim promotion

Propose work

P18H

Independent readiness and expansion review

Depends on: P18G evidence + verified operating capacity
Development hook: Remain partially advanced until named review covers staffing, privacy, law, accessibility, independent appeals, backup expiry, archival recovery, failures, and replacement paths

Propose work

P19

Shared project and grant workspace

Depends on: P11 + P12 + P14 + P18
Development hook: Blocked until P18 controls plus financial, funder, permissions, audit, and handoff requirements pass

Propose work