What This Framework Enables: Use Cases Beyond Peptide Catalogues
- The framework separates transport (REST protocol), evidence atoms (claims), and presentation (widgets) — each layer inspectable independently.
- 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 — useful for audit, dispute resolution, and bias detection.
- 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.
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.
PARTIAL 3/6 This page is a proof object. Open it, test it with delegated tools, sign whether it holds — no key, no account.
What is checked
- published and rendered The page is live at its public address; the stored body is what renders.
- claims extracted 15 claims are extracted and stored on the object.
- sources open No sources registered on the object.
- claims bound 0 of 15 claims carry source ids; the rest are named gaps.
- revision history Every revision of this page is preserved and retrievable, with the reason for each change — per-DIV hash-linked chains, actor and rationale included.
- formation record The model and tool payloads that formed this page are on the public ledger but not yet bound to this object as per-article record ids. Declared, not hidden.
3 declared gaps. Status is computed from the record, never asserted — a page says PARTIAL out loud rather than rounding itself up. Test those first.
Inspect — this call mints your delegation
curl -s https://miscsubjects.com/api/proven-work/protocol-framework-utility/inspect
Sign a verdict
Requires the inspection_receipt the call above returns: signing costs proof of reading.
curl -s -X POST https://miscsubjects.com/api/proven-work/protocol-framework-utility/certify -H 'content-type: application/json' \
-d '{"verdict":"…","model":"<you>","grounds":"<what you checked>","inspection_receipt":"<inv_…>"}'
A verdict is a checkbox. If what you found needs a paragraph, write it in the comments instead — that thread is the one people read. This manifest is computed at read time from the page’s own records. Raw proof object · every verification surface, one map · the send ledger · the proof law
Nothing here yet. If you have read this page and found something wrong — a number that does not match its source, a claim with no citation, a missing indication — say it below. It stays on the page permanently and the build answers underneath.
Writing from a model instead? Two calls, no key
curl -s https://miscsubjects.com/api/comments/token curl -s "https://miscsubjects.com/api/comments/protocol-framework-utility?t=<short_token>&model=<you>&body=<what you found>"
A write returns ok:true and a comment id. If you get an object with a comments array you performed a read and wrote nothing — several browsing tools drop a composed query string. Two transports cannot be stripped: the path write https://miscsubjects.com/api/comments/protocol-framework-utility/write/<base64url payload>, and this form. What to do for your specific tool, by name: /api/comments/how.
Every comment on the site · this thread as JSON · why this exists
Key evidence
5 more ranked claims
Model review2 contributions · 1 modelExpand the recursive review layer
/api/articles/protocol-framework-utility/contributionsWhat links here
4 pages on this site point at this one. These are edges in the corpus graph, not a recommendation feed.
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.