Prompts for the site’s next useful forms.

Stage hook

Run whenever the introductory ontology, recursion/recurrence/resonance/collapse distinctions, detector ancestry, finite-match contract, bounded nonfactorization, 33-Tool status, website manual, or a designated later source edition changes.

Inspect Volume One Third Edition, its transition ledger and source boundary, the preserved First and Second Editions, Experiment One Second Edition, Volume Eleven Second Edition, Volume Twelve Third Edition, and CR-065. Preserve the distinction between physical, representational, and analytical recursion; protected recurrence and optional resonance; statelessness and memorylessness; finite observable matching and hidden physical identity; neutral recurrence artifacts and later classification; and bounded nonfactorization and unrestricted novelty claims. Treat the 33 Tools as open perspective seeds, not a complete ontology. Keep source, detector, collapse-stack, operator, unit, and AI-contribution ancestry visible. Do not overwrite an earlier edition or present a proposed experimental distinction as observed physics. If a later work changes the introductory route, create a new edition, retain labeled archives, reconcile the homepage and change register, and update the errata only when James Dunn separately asks to update errata.

Stage hook

Run whenever James Dunn asks to update errata, or whenever a new document, correction, deletion, supersession, preservation event, publication, or material perspective change must enter the development record.

Read the current cumulative Development Inventory and Errata Index and recover its last completed cutoff before judging later events. Preserve all prior pages, IDs, classifications, ambiguities, and errors as historical evidence. Append every recoverable addition, modification, qualification, supersession, relocation, exact duplication, preservation event, deletion or active-link removal, format transformation, integration, and unknown loss since that cutoff. Distinguish deletion from supersession and from archive preservation; state which relations were retained, transformed, merged, discarded, generated, or left unknown. Include user-originated conceptual corrections even when they produced no separate file, and relate them to resulting documents. Replace the existing errata file under the same filename, Library identity, and homepage download relation. Do not create a newly named edition unless James Dunn explicitly requests one. Preserve scientific claim boundaries, source hashes where non-self-referential, and same-transaction publication events for exact entry in the next append when necessary.

Stage hook

Run whenever the experimental program, apparatus family, field-mode recursion, match class, recurrence capsule, frame-shake taxonomy, operator ledger, laboratory synthesis, safety boundary, preregistration, evidence status, or claim-promotion rule changes.

Inspect Experiment One Second Edition, the preserved First Edition, experimentation-development.json, experimental-claim-packet.json, the evidence, replication, and utility registries, and CR-062. Preserve sacrificial calibration, delayed detection, true-return and false-return controls, finite declared matching classes, neutral recurrent-artifact identifiers, complete laboratory-local reports before harmonization, immutable raw data, original units and coordinates, uncertainty and calibration lineage, null, minority, contradictory, conditional, unresolved, resolved-to-model, and failed-translation outcomes, independent model predictions, outcome-independent acceptance, and the separation of observation, derivation, mainstream interpretation, structural correspondence, and speculative hypothesis. Treat the 33 Tools as provisional frame-shake prompts rather than a closed ontology. Do not treat publication of the protocol as verified laboratories, safety or institutional approval, execution authority, live evidence, replication, utility, or support for Substrate Cosmology. Advance only through the existing EXP gates with new protected data, named responsibility, and independent review.

Stage hook

Run when an active external destination, audience, authority claim, redirect, privacy expectation, funding opportunity, student link, or platform access rule changes, when an observation expires, or when named reviewer capacity becomes available.

Inspect external-dependency-registry.json, external-review-protocol.json, external-network-observations.json, external-human-review-worklist.json, external-human-review-fixtures.json, external-review-fixtures.json, the maintenance queue, and CR-043. Repeat MNT12B by the earliest expiry in a privacy-safe environment, retaining prior failures and declaring transport limits without transmitting user, application, credential, draft, or student data. Treat technical success only as an observation. Quarantine cross-origin redirects except registered citation resolvers whose DOI identity remains preserved; even that narrow exception remains unapproved. Review same-origin redirects. Execute MNT12C from the priority worklist only with named source-authority and privacy reviewers, plus a safeguarding reviewer for student destinations and a funding-currency reviewer for grant destinations. Require one dated, expiring decision per active URL, validate candidate evidence against every MNT12CV rejection class, and preserve all limitations and dissent. Do not appoint a reviewer or approve, publish, remove, redirect, or reclassify a destination from automated output alone.

Stage hook

Run before architectural or hosting changes, and repeat semiannually after the first evidence record.

Inspect recoverability-evidence.json and CR-039, then recover the registered substrate-cosmology source into a new clean nonproduction checkout. Verify the exact project identity without creating a replacement Site. Run pnpm run install:ci so the declared package-manager version and lockfile are enforced; then run every registered control, build, package, and inspect the hosting artifact. Preserve prior findings and record changed assumptions, credential boundaries, provider dependencies, compute limits, failures, and what cannot be proven without production access. Do not change production access, deploy the drill artifact, enable blocked interactions, or claim data or provider recovery.

Stage hook

Run whenever a person is proposed, a contribution changes, name order or share is disputed, consent changes, a citation is corrected, privacy expectations change, a funding notice changes, or a record is withdrawn.

Inspect significant-contributors.json, significant-contributor-fixtures.json, the public contributor page, CR-045, and the linked evidence record. Add no name from automated inference, popularity, seniority, funding, or agreement. Require a stable contribution ID, version, bounded significance rationale, claim-appropriate review, limitations, public evidence, person-specific contribution statements, an approved order basis, and explicit opt-in approval from every named person for the displayed name and citation. Use descending documented contribution by default; mark equal contribution explicitly; publish percentages only with unanimous approval. Exclude contact details and private application material. At recognition, search official funder notices for five currently published opportunities matched to contribution category, scope, evidence maturity, applicant type, institutional or nonprofit participation, geography, funding scale, and likely next work. For each match record funder, official notice, deadline, eligibility summary, applicant route, match rationale, and check date. If fewer than five credible current matches exist, publish only verified results plus a documented shortfall; never pad. Require a fresh official-notice check immediately before application. Treat every match as a dated lead, not eligibility or funding approval. Treat the contributor entry as bounded evidence, not certification, grant eligibility, or broad subject mastery. Version corrections and preserve a privacy-respecting withdrawal and citation-resolution path. Run the complete synthetic rejection set, site checks, and production build before publication.

Stage hook

Run whenever inspiration capture, browser storage, portable workspace sharing, account storage, AI access, consent, reuse, diversity sampling, moderation, retention, withdrawal, student access, or privacy expectations change.

Inspect inspiration-todo-contract.json, the sitewide InspirationCapture component, the inspiration interaction workspace, P21A/P21B in development-priorities.json, CR-049, and CR-058. Preserve instant device-local draft recovery, one-action ToDo capture, completion, deletion, local organization, export, explicit user-controlled AI prompt copying, no inspiration content in external URLs, optional response paste-back, participant-label non-access, same-origin forum-link restriction, and portable export/import compatibility. Never describe device-local data as backed up, account-scoped, server-held, automatically submitted, AI-readable, or live multi-user collaboration. Keep student workspace and safety routes excluded. Before P21B or live invitations, require authenticated owner-scoped storage, per-item and purpose-specific opt-in, personal-information/secret/link filtering, moderation and abuse response, source and permitted-use lineage, expiry, export, deletion, withdrawal propagation, minor exclusion or independently reviewed safeguarding, independent privacy/legal/accessibility/appeal review, and diversity sampling that cannot turn popularity, identity, institution, or agreement into scientific authority. Do not enable automatic AI reading, response retrieval, private messaging, real-time cross-user editing, or shared-pool writes from a software-only change.

Stage hook

Run whenever student roles, input channels, approved websites, messaging, uploads, privacy expectations, abuse patterns, access systems, or safeguarding standards change.

Inspect minor-interaction-safety.json, student-development-workspace.json, the student workspace and safety pages, maintenance hooks, and CR-024. Keep the design safe regardless of claimed age; do not introduce invasive age inference as the primary control. Verify visible adult roles, public or teacher-mediated participation, personal-information filtering, approved-domain enforcement, unknown-link and file quarantine, reporting, incident evidence, retention, deletion, appeals, accessibility, and operating capacity. Keep all student input and communication capabilities disabled until EDU01S2 and EDU02 receive named safeguarding, educator, accessibility, operational, and legal review.

Stage hook

Review whenever grade bands, safeguarding expectations, funding programs, mentor roles, access, privacy, or educational evidence changes.

Inspect student-development-workspace.json, the public student workspace, Grants Resources, maintenance hooks, and CR-022. Preserve no-account practice, student privacy, trusted-adult responsibility, gentle evidence-specific feedback, small-step progression, null and failure retention, and the separation between useful work and agreement with Substrate Cosmology. Before EDU02, obtain named educator and safeguarding review of grade-band language, project safety, accessibility, motivation, and funding guidance. Do not collect student work, enable private messaging, or create minor accounts until access, consent, moderation, retention, and incident-response controls pass.

Stage hook

Run whenever an AI model, prompt format, schema, or vendor changes.

Inspect the current scalar, evidence-relation, replication, utility, maintenance, and change registries. Propose a vendor-neutral exchange envelope using plain JSON and Markdown. Preserve stable identifiers, source lineage, null results, conflicts, confidence history, aliases, and the distinction between operational usefulness and ontology. Add compatibility fixtures for at least two materially different AI systems. Do not remove an existing format until conversion, rollback, and archive checks pass.

Stage hook

Open only after portable records and identity/role boundaries are defined.

Design a distributed stewardship and appeal workflow for Substrate Cosmology. Separate contributor, reviewer, steward, moderator, and administrator authority. Require named decisions, conflicts of interest, minority reports, appeal windows, rotation, and immutable audit history. Prevent any institution, funder, AI vendor, or vocabulary from silently controlling the commons. Stage identity, privacy, moderation, abuse response, and legal review before implementation.

Stage hook

Require ecological, cultural, safety, planetary-protection, and anti-homogenization review.

Create a research surface for long-duration preservation and diverse-life propagation. Separate demonstrated capability from speculative horizon work. Map dependencies across closed-loop ecology, seed and genome archives, microbial communities, autonomous repair, cultural continuity, propulsion, navigation, planetary protection, consent, reversibility, and failure containment. Preserve multiple cultural and biological futures rather than optimizing toward one standardized civilization.

Stage hook

Re-run fixtures and review schema, numerical method, compute budget, accessibility, isolation, and exports before adding or changing a model.

Inspect the current bounded simulator, simulation-schema.json, validation fixtures, and CR-012. Propose only one additional deterministic model after its conventional baseline, null world, equations, units, numerical tolerance, validation fixture, failure states, compute ceiling, cancellation behavior, accessible alternative, and export compatibility are documented. Treat outputs as mathematical consequences, not evidence of Actual Physics. Run all checks before and after the bounded addition.

Stage hook

Re-test the contract and accessible equivalents when visualization libraries, accessibility expectations, simulation methods, evidence relations, or scalar schemas change.

Inspect the current scalar explorer, visualization-schema.json, simulator graph/table, and CR-013. Extend only when a proposed view retains stable IDs, provenance, uncertainty, evidence status, interpretation limits, keyboard and touch operation, reduced motion, text/table equivalence, and compatible export. Never imply that distance, alignment, color, or animation proves causation. Preserve contradictory and non-comparable branches.

Stage hook

Re-run the complete forum runtime and site gates whenever authentication, roles, storage, thread or reply fields, moderation, reports, screening, rate limits, retention, export, experiment stages, privacy, appeals, or safeguarding changes.

Inspect the forum API routes, db/schema.ts, lib/forum.ts, forum policy and operating contracts, forum-research-thread-contract.json, forum-thread-fixtures.json, experimentation-development.json, CR-055, and the working forum. Preserve public reading, adult-authenticated writing, pending-by-default visibility, owner prepublication review, rationale-bearing moderation events, same-origin writes, rate limits, reports, author withdrawal, portable public export, input length limits, and personal-information, contact, and link screening. Keep direct messages, uploads, popularity signals, automated matching, contact exchange, student posting, execution authorization, preregistration claims, evidence promotion, and scientific approval disabled. Preserve productive overlap and important divergence without ranking agreement, prestige, popularity, or funding. Treat E0–E8 labels as participant classifications only. Before expansion, require named staffing, verified researcher and institution roles, recovery and revocation exercises, independent appeals, privacy/legal/accessibility review, backup expiry and archival recovery evidence, and safeguarding review. Run the forum runtime check, every registered release control, a production build, and supervised public-reading preview before publication. Also inspect CR-056, CR-057, and forum-following-link-safety-spec.json. Preserve public-response removal of stable account identifiers and internal moderation notes, the private account-scoped My submissions queue, owner-visible moderation notes, moderator-only rationale history, thread and reply withdrawal, explicit-only topic/subtopic/post following, separate email selection, child mute overrides, account-email non-disclosure, centralized link screening, inert pending links, safe rendering, and the rule that moderators may add protection but cannot activate a hard-blocked or technically unverified destination. Keep outbound email, redirect resolution, reputation providers, and scheduled rechecks staged until their named dependencies and independent reviews exist.

Stage hook

Stage organization verification, role access, financial/privacy review, records retention, and funder-specific compliance.

Design a shared project workspace that helps investigators form teams and manage grant development without exposing private proposals or confusing coordination with scientific validation. Include project charters, named roles, institutional eligibility, collaborators, milestones, dependencies, deliverables, budgets, indirect costs, approvals, conflicts, data plans, letters, deadlines, funder contacts, decision logs, and immutable submissions. Separate public summaries from restricted work. Require least-privilege access, export, retention, audit, handoff, and obsolescence plans before storing real grant data.

Stage hook

Run after material route, interaction, audience, accessibility, device, browser, dependency, platform, or task-boundary changes.

Inspect usability-evidence.json, usability-interaction-fixtures.json, usability-runtime-evidence.json, the five public task journeys, dashboard stage, search inventory, roadmap, maintenance hooks, and CR-023. Run the source-contract and site-integrity checks. Execute UX06B2B2 only in an environment that can verify actual 200% browser text enlargement across the five journeys; do not infer completion from responsive CSS or source inspection. Repair one evidenced failure at a time and repeat the affected case. Then stage prompt, simulator, contribution-draft, and complete next-step-chain runtime checks. Do not collect personal browsing histories or private drafts. Keep UX06C blocked until representative devices, assistive technology, and reviewers are available.