📂 Bundle Templates

Reference bundles for each protocol layer. Use them as a starting point — fork the Markdown, ask your LLM to regenerate the JSON (and, for solutions, the code + reports), then submit.

The bundle convention in one line:

Every layer ships a Markdown file (human-readable, source of truth) plus a JSON file (structured, machine-readable). The Markdown ends with a File Mapping footer that documents the JSON schema and gives an LLM the exact prompt to regenerate it. For Solutions, the footer additionally points to a code/ directory (runnable solver) and a reports/ directory (reconstruction results on the parent benchmark).

⚛ L1

Principle

2 files

📋 principle.json ⬇
📝 principle.md ⬇

📐 L2

Spec

2 files

📋 spec.json ⬇
📝 spec.md ⬇

☆ L3

Benchmark

2 files

📋 benchmark.json ⬇
📝 benchmark.md ⬇

⚡ L4

Solution

6 files

📄 code/requirements.txt ⬇
🐍 code/solver.py ⬇
📝 reports/reproduce.md ⬇
📝 reports/results.md ⬇
📋 solution.json ⬇
📝 solution.md ⬇

Ready to contribute? Pick a layer and submit your bundle.

⊕ Submit a bundle →