Adaptive Dosing-Schedule Twin
Introduction
1 / 3Adaptive Dosing-Schedule Twin is a digital twin specification derived from principle L1-903. It defines the forward operator and a 3-dimensional parameter space Ω over which benchmarks are seeded. Each benchmark drawn from this twin is a concrete measurement instance with fixed Ω values; solvers must invert that specific measurement.
Ω Parameter Space — 3 dimensions
Earn PWM — build a benchmark from this twin
Each accepted L3 benchmark earns 60% of its mining pool + 15% royalty on every verified solution, forever.
Contents
2 / 3On-Chain Artifact Registry
Base Sepolia → Base Mainnet on graduationDigital Twin Specification — L2-903
Ω Parameter Space
| Parameter | Range |
|---|---|
| dose_cap | 0.2 – 1.0 |
| schedule | continuous|adaptive|intermittent |
| trigger_frac | 0.1 – 0.5 |
ε (epsilon)
{
"expression": "\u2264 1 month error on time-to-progression; no schedule that selects resistance early",
"type": "fn"
}
📝 Markdown source — L2-903.md
🎁 Contribute & earn PWM
Improve L2-903 — submit with or without uploading. Accepted submissions earn the 1/16 modify share of A(t).
⬆ Submit by uploading your files earn PWM · unlimited
Upload your .md + .json
as a modification of L2-903 — the main way to contribute & earn. Unlimited submissions.
✨ Or try a free one-click check free · 1×
No files, no typing — we submit a check of L2-903 for you once; it goes through review and earns the 1/16 share. One free no-upload Digital Twin per account.
You'll be asked to log in first — then it's one click, no files.
🛠 Helper: build your files in ChatGPT / Gemini / Claude
Layer template
Fork L2-903
Prompt — copy into your LLM
You are helping me submit a MODIFICATION of L2-903 (Adaptive Dosing-Schedule Twin) to the PWM Protocol — a Digital Twin (L2) artifact. I will paste a Markdown template (or the current L2-903.md). 1. Rewrite the Markdown so the science is correct and clearly explained for my change. 2. Regenerate the sibling L2-903.json so EVERY field matches the Markdown. 3. Keep the schema in the "File Mapping" footer at the bottom of the MD. 4. Keep the parent reference unchanged unless I ask otherwise. Rules: the Markdown is the source of truth; use SI units; do NOT invent benchmark scores. Output each file in its own fenced code block tagged with the filename. Here is my template: [PASTE THE .md HERE]