Knowledge-authority maturity ledger
What is built is not the same as what the public has validated. This ledger separates local capability from production proof, real community outcomes and independent scrutiny.
There is no honest overall percentage. Software tests can verify registries, routes and boundaries. They cannot prove that keepers understood the guidance, that an outside expert agrees, that another community adopted the work or that Molt & Moss is the top source.
- Verified locally
- 8 capabilities
- Requires production validation
- 1 capabilities
- Requires real community evidence
- 4 capabilities
- Requires independent scrutiny
- 2 capabilities
Counts describe ledger rows, not weighted progress, confidence, importance or evidence strength. A locally verified row can still require maintenance; an externally gated row may need months of observation.
Verified locally
Bounded Neocaridina evidence registry
Current evidence: Structured biological records separate methods, experimental units, results, limits and guide usage, with source-role-specific appraisal questions.
Evidence needed next: Keep registry integrity, source access, appraisal parity and scheduled review checks passing.
Answerable open-question research agenda
Current evidence: Every named evidence gap has a public brief connecting the decision at stake to a primary endpoint, minimum design, required reporting, participation boundary and closure rule.
Evidence needed next: Keep every brief synchronized with its canonical gap and reproducible search trail, and require complete method review before any gap state changes.
Finite research allocation and stopping system
Current evidence: Every named gap has an operating state, allocation reason, next permitted unit, activation trigger and stop decision, with exactly one bounded validation active.
Evidence needed next: Keep portfolio entries synchronized with gap, search and answerability changes, and activate work only after the named trigger and method boundary are satisfied.
Practical guide library
Current evidence: Twenty-seven detailed guides connect bounded action to evidence, authorities, gaps and revision history.
Evidence needed next: Keep every guide connected to its generated evidence dossier and correction path.
Keeper-language and cross-type retrieval
Current evidence: Deterministic search covers all detailed guides and the governed public knowledge inventory, with every matched guide connected to its registry-derived first-decision card.
Evidence needed next: Keep positive routing, no-match, meaningful refusal and exact guide-to-card bridge benchmarks passing.
Beginner teaching and evidence literacy
Current evidence: The readiness path, foundation course, glossary, claim checks, reply standard, one bidirectionally linked tank-side decision card per detailed guide, accessible social descriptions and an append-only grouped-signal decision and follow-up lifecycle are implemented and regression tested.
Evidence needed next: Keep teaching language, decision cards, guide links and accessibility descriptions synchronized with governing guides, and preserve each signal-derived decision and denominator-aware follow-up.
Transparent correction and maintenance system
Current evidence: Named gaps, searches, evidence challenges, publication-status states, maintenance schedules, correction-impact paths, public change history and exact-snapshot live social reviews share stable identities.
Evidence needed next: Complete scheduled literature and source-integrity reviews, inspect every affected consumer and live social receipt, preserve unfavorable findings and publish accepted corrections through every required layer.
Machine-readable and citation-portable knowledge
Current evidence: Versioned JSON, JSON Schema, CSL-JSON and RIS derive from governed registries.
Evidence needed next: Preserve schema parity, stable identifiers and bounded reuse language.
Requires production validation
Current knowledge architecture available on the canonical public site
Current evidence: The 46-migration release passed its complete preflight. The 2026-08-12 baseline found production through 0016; the authorized 2026-08-12 migration advanced production through 0045 with 0 pending, 0 foreign-key violations and the protected pre-release backup preserved. Release version 9a63695d-c39e-4725-abf0-5d0d2d0b436e received 100% of traffic, the public smoke passed across 34 routes plus the Access boundary, and version 9730c2e8-4cfc-4216-84c3-f248873808a4 remains the pre-release rollback identity. Authenticated administrator inspection, the live consent surface, the attribution handoff and invalid-token unsubscribe refusal passed. A controlled enrollment, stored attribution and POST-confirmed unsubscribe receipt remain required.
Evidence needed next: Preserve one controlled enrollment, stored attribution and POST-confirmed unsubscribe receipt alongside the public release, authenticated inspection and rollback receipts.
Requires real community evidence
Real keepers understand and act on the guidance
Current evidence: Anonymous feedback, question intake, privacy-minimized readiness measurement, eight frozen open-response scenarios, a private pseudonymous session ledger and a denominator-aware teaching-decision follow-up are designed locally.
Evidence needed next: Run protocol-compliant sessions, preserve unfavorable and unusable records, and show repeated comprehension gaps decline after documented edits without treating votes as truth.
Real keeper questions are covered at a useful boundary
Current evidence: Fifty-four routing scenarios, twelve scope refusals, a six-outcome real-question coding kit, a privacy-safe service-session denominator and a server-derived signal-to-retrieval-decision lifecycle pass locally.
Evidence needed next: Moderate real questions, measure honest no-matches and improve retrieval or open named gaps when recurring needs remain uncovered.
Bounded answers travel through existing communities
Current evidence: Portable claim replies, teaching cards, reviewed-answer text, the seven-part reply standard, a voluntary-reuse protocol and a private public-receipt ledger with fixed qualification rules are implemented.
Evidence needed next: Observe voluntary reuse, substantive replies and corrections outside owned pages without automating community participation or counting paid, owned or publisher-initiated use.
More new hobbyists enter and remain successfully
Current evidence: A six-lesson permissioned path, social acquisition plan, prospective enrollment snapshots, sent-lesson-gated action records, optional 30-day and 90-day outcomes and storage-derived cohort reviews are ready locally.
Evidence needed next: Verify live consent, delivery, return actions, missingness and longer-term keeper outcomes across real prospective cohorts without calling enrollment records unique people or claiming causation.
Requires independent scrutiny
Editorial method survives independent expert scrutiny
Current evidence: A public reviewer packet, predeclared protocol, frozen eight-assignment first round and private event ledger separate invitations, declines, conflicts, source barriers, linked critiques and propagation-complete public responses.
Evidence needed next: Obtain documented critique from qualified independent aquatic, taxonomic, statistical or evidence-method reviewers and publish finite responses.
The resource is trusted and adopted beyond its publisher
Current evidence: Stable public identities, citation exports, tank cards, an open standard, an independent-use protocol and a private ledger requiring unaffiliated external decisions are designed for bounded reuse.
Evidence needed next: Document independent citations, standard use, correction participation or sustained community referral across unaffiliated settings without equating followers with trust.
How a row changes state
A row moves only when the named proof exists. Shipping local code does not prove comprehension. A follower count does not prove trust. One friendly endorsement does not prove independent review. A test pass proves only the behavior its assertions actually cover.
Ledger reviewed 2026-08-12. It is an accountability record, not a launch forecast, marketing claim or scientific confidence scale.