Protocol API Structure: REST Surface, Objects, and Phase Machine

(default writer prompt)

input: protocol-api-structure

## Regeneration vs degeneration — where this fits

The body breaks down tissue and rebuilds it at the same time. A problem lasts when breakdown moves faster than repair. Most drugs block signals such as pain or swelling. They do not rebuild the tissue that created the signal. This article places one compound inside that frame. It asks whether the compound affects repair steps rather than signal suppression.

## What it is

The ledger contains no entries for this compound. No name, structure, or origin is recorded.

## How it works

No mechanism data exists in the ledger. No pathway, receptor, or cell target is listed.

## Why it would work (logic chain)

No logic chain is present. No if-then steps connect the compound to any repair outcome.

## Why people take it

The ledger lists no stated reasons. No user goals are recorded.

## How many people take it

The ledger shows zero tracked users. The number of people who take this compound is unknown.

## Evidence inventory

- Sources total: 0
- Studies catalogued: 0
- Reddit posts: 0
- X posts: 0
- Other anecdote sources: 0
- Claims human: 0
- Claims preclinical: 0
- Claims anecdotal: 0

No human studies, animal studies, or anecdotes are stored.

## What scientists say

The ledger contains no scientist statements. No papers or expert comments are recorded.

## What people say on Reddit

The ledger contains no Reddit posts. No user 

(default writer prompt)

input: protocol-api-structure

## What this article is

This document describes the live REST surface and phase machine for miscsubjects.com.  
It is system documentation, not a compound catalogue entry.

## Who claims what

The build itself defines the contract.  
GET /api/protocol returns the authoritative machine map.  
API_QUICKMAP.md and PROTOCOL_SPEC.md are static mirrors of that contract.

## What is known

GET /api/protocol exposes the endpoint list, body schemas, and phase definitions.  
Two planes exist: /api/articles for CRUD and sub-resources, and /api/protocol for phase operations.  

Claims live in article.meta.claims[]. Sources live in meta.sources[] with prev/hash chain. All writes are append-only.  

POST /api/protocol/draft validates tiers, optionally verifies source URLs, and hash-chains sources.  
POST /api/protocol/populate ingests sources into an article without rewriting the body.  
POST /api/protocol/collaborate lets Kimi or Gemini append 1–3 claims.  
POST /api/protocol/score recomputes claim.weight and applies status:cut when below threshold.  
GET /api/protocol/next?role=writer hands out one open task atomically.  
POST /api/protocol/run executes one scheduler tick inside the 100-second request limit.  
GET /api/matrix/gaps lists missing roots and cross cells. POST /api/matrix/seed fills from the canonical catalog.  
Webhook POST /api/articles/{slug}/webhook accepts atomic appends