# ⚡  L4 Solution — baseline:community

**ID:** `L3-516-001-001-T1-community-topup` · **Status:** ⊙ Testnet (genesis catalog)
**Parents:** ⬆ Benchmark [`L3-516-001-001-T1`](/artifact/l3/L3-516-001-001-T1)

> **🛠 Solver:** `baseline:community`
> **📊 Performance:** **Q = `0.8`** · difficulty `0.15`
> **🔖 Status:** `testnet`

---

## 1. Solver

**`baseline:community`**

## 2. Performance

| Property | Value |
|---|---|
| Difficulty score | 0.15 |
| Quality ratio | 0.8 |
| Reward pwm | 0 |

## 3. Operating Point (Ω_s)

| Parameter | Unit | Value |
|---|---|---|
| Te ms | ms | 35 |
| Tr ms | ms | 2000 |
| Snr db | dB | 20 |
| H voxels | — | 16 |
| W voxels | — | 16 |
| Z voxels | — | 8 |
| B0 field t | — | 3 |
| Voxel size mm | mm | 8 |
| Spectral points | — | 1024 |
| B0 inhomogeneity | — | 0 |
| Partial volume csf | — | 0 |
| Voxel lipid contamination | — | 0 |
| Water suppression residual | — | 0 |
| Threshold calibration age effect | — | 0 |

## 4. Certificate

**Hash:** `284f6f7668582260ac682333464b2a13d6d1dfe7a4c3af0e78dd68c14dd9247b`

**Status:** `testnet`

## 5. Code

Reference implementation — see [`code/`](/artifact/l4/L3-516-001-001-T1-community-topup/raw/code/) when present.

## 6. Reproduction Report

Reconstruction results on the parent benchmark — see [`reports/`](/artifact/l4/L3-516-001-001-T1-community-topup/raw/reports/) when present.

---

## File Mapping

This bundle consists of: `L3-516-001-001-T1-community-topup.md`, `L3-516-001-001-T1-community-topup.json`, `code/`, `reports/`.

| File | Role | How to regenerate |
|------|------|-------------------|
| `L3-516-001-001-T1-community-topup.md` | Source of truth — edit this | Human or LLM |
| `L3-516-001-001-T1-community-topup.json` | Structured metadata for the registry | LLM regenerates from the sections above |
| `code/solver.*` | Reference implementation | LLM regenerates from §1 Solver and §2 Operating point |
| `reports/results.md` | Reconstruction results | **Generated by running the solver** — do not fabricate |
| `reports/reproduce.md` | Step-by-step verification recipe | LLM regenerates as a recipe matching what was actually run |

**Prompt for your LLM after editing this Markdown:**

> Read the attached Markdown. Regenerate the sibling `.json` so every field matches.
> Also regenerate `code/solver.*` and `reports/reproduce.md` per the schema.
> Output each file in its own fenced code block tagged with the filename.
> Do NOT fabricate `reports/results.md` — it must come from actually running the solver.

_This Markdown was auto-synthesized from the catalog row for `L3-516-001-001-T1-community-topup`._
_Edit it, regenerate the JSON, and submit at [/submit](/submit) to claim the artifact._