What This Framework Enables: Use Cases Beyond Peptide Catalogues
What this article is
This document explains what the miscsubjects.com protocol framework can do beyond peptide catalogues. It describes the build itself.
The framework separates transport (REST protocol), evidence atoms (claims), and presentation (widgets). Each layer remains inspectable independently.
Who claims what
Tasks REST and dispatch directory let cron jobs and human operators invoke protocol steps as named functions.
Library-snapshot and poll endpoints support periodic external source refresh against existing claims.
What is known
POST /api/protocol/ask returns gaps[] and ingest_hint. The ledger tells the user what evidence would materially improve the answer.
Combinatorial matrix generalizes to any inventory × target grid where regen/degen scores can be defined transparently.
Multi-model collaborate preserves each model's original contribution. This supports audit, dispute resolution, and bias detection.
Graph canvas GET /api/graph enables cross-article reasoning without copying full bodies into prompt context.
iMessage/WhatsApp ingest paths let lay users add anecdotal tier evidence that enters the same hash-chained ledger.
Obsidian vault export supports offline research workflows while keeping slug parity with the live corpus.
What is unknown
Domain packs beyond peptides require new canonical catalogs. The engine (matrix, grow, claims) is domain-agnostic.
Federation across multiple miscsubjects instances is not implemented. Single D1 spine today.
Commercial RUO peptide commerce integration is out of scope. The framework is evidence organization only.
Limitations
Accessible register articles still depend on claim tier discipline. Prose alone does not elevate evidence.
Usefulness scales with source forest density. Empty articles benefit from populate before ask.
Disclaimer
Framework users remain responsible for their own research and medical decisions.
Key evidence
5 more ranked claims
Ask this article · 8 suggested prompts
Text the build (+14245134626) or WhatsApp — slug|question creates a question node. Paste evidence with ingest slug|q:NODE_ID|your paste.