# ⚡  L4 Solution — baseline:community

**ID:** `L3-464-001-001-T1-community-topup` · **Status:** ⊙ Testnet (genesis catalog)
**Parents:** ⬆ Benchmark [`L3-464-001-001-T1`](/artifact/l3/L3-464-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 |
|---|---|---|
| Q i bopd | — | 500 |
| B exponent | — | 1.5 |
| D i per month | — | 0.05 |
| N months history | — | 24 |
| Compression uplift events | — | 0 |
| Workovers and recompletions | — | 0 |
| Rate interference from offset wells | — | 0 |

## 4. Certificate

**Hash:** `94926ab7a75d7ff27b16df9998fb7afa64c572cafb48573ce60180159782f50a`

**Status:** `testnet`

## 5. Code

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

## 6. Reproduction Report

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

---

## File Mapping

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

| File | Role | How to regenerate |
|------|------|-------------------|
| `L3-464-001-001-T1-community-topup.md` | Source of truth — edit this | Human or LLM |
| `L3-464-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-464-001-001-T1-community-topup`._
_Edit it, regenerate the JSON, and submit at [/submit](/submit) to claim the artifact._