RECENTLY COMPLETED
P18I · Profile, following, notification-preference, and link-safety foundationAccount-scoped profiles now consolidate explicit topic, subtopic, and post follows; separate email selections; child mute exceptions; authored activity; and profile editing without exposing account email. Profiles, threads, and replies share one fail-closed link intake. Submitted destinations remain inert until staged redirect-chain and reputation checks pass; moderators may disable links but cannot activate or bypass them. Outbound email delivery is not enabled.
MNT01 · Development-state consistency layerP13, P14, and P15 continuation labels corrected to implemented; future priority claims checked against this queue and the maintenance registry.
EDU01S2A · Synthetic minor-interaction safety fixturesEleven synthetic cases now test reference handling for personal information, precise location and schedules, approved and unknown links, shortened URLs, files, off-site contact, safety reports, and ambiguous numeric patterns. No interaction channel was enabled.
UX06B2B2P · Portable 200% enlargement verification protocolA versioned evidence contract now defines the measurable entry gate, five public journeys, result fields, privacy boundary, hooks, and re-entry path. The test itself remains blocked and unclaimed.
UX06B2B2V · Fail-closed enlargement evidence validatorSix synthetic cases now verify the portable evidence format, reject missing measurements and journeys, reject CSS substitutes and privacy violations, and prevent unmeasured pass claims. UX06B2B2 remains blocked.
MNT02 · Platform compatibility and obsolescence registerA versioned registry and automated checker now detect drift in runtime, package manager, framework, storage bindings, access assumptions, change hooks, and replacement requirements without performing automatic upgrades.
MNT03 · Feature interconnection registryEight major capabilities now map to their routes, source surfaces, public artifacts, feature dependencies, maintenance hooks, checks, limitations, and successor paths; missing or stale connections fail the standard site check.
MNT04 · Maintenance-hook dependency validationThirty-nine evolution hooks now undergo unique-identifier, known-prerequisite, cycle, required-response, stage-gate, stop-condition, and successor-path validation while blocked product stages remain closed.
MNT05 · Public artifact lifecycle registryEvery public JSON artifact now belongs to one dependency domain with a lifecycle class, maintenance hooks, public nonpersonal boundary, retention rule, same-release change rule, and successor path; additions, removals, renames, and orphaned files fail the standard site check.
MNT06 · Route lifecycle and access-boundary registryAll public pages and API routes now belong to dependency domains with explicit access, interaction boundaries, maintenance hooks, and successor paths; route additions, removals, renames, source mismatches, or orphaned handlers fail the standard site check.
MNT07 · Dependency-ordered verification control registryEvery release checker now declares its dependencies, protected scope, evidence class, failure policy, hooks, limitations, and successor path; missing, unwired, reordered, or silently disabled checks fail the standard site check.
MNT08 · Change-impact routing contractEvery tracked source file now routes through at least one rule that identifies required hooks, controls, update surfaces, stage gates, limitations, and stop conditions; unrouted files or stale impact fixtures fail the standard site check.
MNT09 · External dependency and link lifecycle registryEvery literal HTTPS destination now belongs to a use class and exposure state with authority, audience, privacy, review, and replacement boundaries; additions, removals, duplicates, unsafe active fixtures, and unregistered references fail the standard site check without claiming live network availability.
MNT10 · Maintenance cadence and evidence freshness controlPer-release, monthly, quarterly, semiannual, and annual maintenance stages now declare controls, hooks, owner classes, evidence types, authority limits, review dates, missed-run responses, and successor paths. A separate maintenance queue advances MNT11 without reopening externally blocked product stages.
MNT11 · Clean-room recoverability drillA new nonproduction checkout recovered the registered remote source, restored pinned dependencies through the project-owned install path, passed all controls and the production build, and produced a validated but undeployed hosting package. The evidence records package integrity, recovery findings, and explicit limits on access, data, provider, and production recovery claims.
MNT12A · Portable external-review evidence protocolA public protocol and ten synthetic cases now separate source inventory, network observation, and named authority, funding, and safeguarding review. The fail-closed validator rejects privacy violations, nonpublic references, unrecognized cross-origin redirects, stale observations, and missing reviewer roles without approving any destination.
MNT12B · External-destination network observationsThirty active destinations now have dated, nonpersonal observation records, declared transport limits, expiry, and named-review handoffs. The protocol now permits only DOI-preserving citation-resolver redirects while retaining non-approval and quarantine boundaries; MNT12C remains blocked on named reviewers.
MNT12CP · Named-review worklist preparationFive priority-ordered batches now cover all thirty external observations with required reviewer roles, checks, finding questions, per-URL decision fields, expiry, privacy limits, and successor rules. Every review and decision field remains empty, so MNT12C stays blocked until named reviewers act.
MNT12CV · Fail-closed human-review evidence validatorTwelve synthetic cases now accept only complete, per-destination, role-complete, nonpersonal, unexpired records and reject missing authority, funding or safeguarding roles, personal information, stale or absent expiry, group-level approvals, unknown destinations, invalid decisions, and incomplete records. No live review was performed.
P20A · Consent-gated contributor registry with grant matchingA public, initially empty categorized registry now defines evidence, review, significance, privacy, consent, attribution-order, correction, withdrawal, and CV-citation requirements. At recognition it also requires a dated official-source search for five related current grant opportunities, eligibility routes, match rationales, pre-application rechecking, and a documented shortfall rather than padded results. Eleven synthetic cases enforce the combined boundary; no real person or grant search was fabricated.
P18F2 · Groupthink-resistant effort introductionsA read-only forum surface, portable contract, and thirteen synthetic cases now require immutable independent positions, work-based matching, meaningful divergence, mutual opt-in, comparison charters, preserved branches, perspective rotation, neglected-area protection, recognition and funding separation, and teacher- or guardian-mediated minor boundaries. Matching, identity disclosure, messaging, and contact exchange remain disabled.
P21A · Device-local moment-of-inspiration capture and portable AI workspaceA persistent adult-workspace dock recovers an unfinished draft, sends a thought to a private browser ToDo list, or prepares one portable interaction workspace. The explicit ChatGPT handoff copies the prompt and opens the official origin without placing content in a URL; users review, paste, and send it. The local workspace supports optional response paste-back, participant labels, same-origin forum topic/post links, JSON export/import, and device sharing. Labels grant no access, and automatic submission, response retrieval, server storage, live invitations, private messaging, real-time editing, student routes, and the cross-user inspiration pool remain disabled.
P22A · Role-specific human and AI bibliographic attributionBibliographic annotations and contributor examples now preserve original source authorship while separately crediting James Dunn for originating concepts and program direction and OpenAI ChatGPT for documented synthesis, drafting, cross-reference organization, software implementation, or editorial coordination. The contract rejects claims of independent verification, scientific authority, or source authorship from AI participation.
EXP01 · Prioritized experimentation development registerA public machine-readable roadmap now orders twelve experimental-research improvements from claim-packet preparation through identity, preregistration, safety, laboratories, raw evidence, analysis, replication, claim promotion, utility, federation, and recovery. Fourteen evolution hooks preserve dependencies and stop automatic progression before external authority or evidence is required.
EXP02 · Portable experimental claim packetA public non-collecting contract now preserves identity, question, candidate relation, conventional and null comparisons, detector and frame, preregistration, safety, runs, raw evidence, analysis, review, replication, attribution, AI assistance, claim decisions, corrections, withdrawals, licensing, and exchange. It cannot authorize physical execution or scientific promotion.
EXP03 · Fail-closed claim-packet readiness fixturesFifteen synthetic cases now accept complete E0, E2, E3, and externally authorized synthetic E4 structures while rejecting missing comparisons, missing predictions, AI self-approval, popularity promotion, Site-generated execution authority, mutable raw evidence, private contact fields, unsupervised minors, unsupported cross-site maturity, and missing export provenance. No live experiment or approval was represented.