---
id: ADAPTIVE-WP-0006
type: workplan
title: "Customer-tuning solver prototype"
domain: financials
repo: adaptive-pricing
status: finished
owner: codex
topic_slug: helix-forge
created: "2026-07-02"
updated: "2026-07-02"
state_hub_workstream_id: "4083f345-1bd3-462f-aa70-50f299729d7c"
---

# Customer-tuning solver prototype

Implement the first seller-safe customer-tuning flow described in `INTENT.md`.

## Define Tuning Interface

```task
id: ADAPTIVE-WP-0006-T01
status: done
priority: high
state_hub_task_id: "ad2df753-ae93-4813-bd35-fb8ee78149cc"
```

Define which pricing parameters may be customer-tunable, how preferences are
expressed, and which parts remain seller-controlled or calculated.

## Implement Solver Core

```task
id: ADAPTIVE-WP-0006-T02
status: done
priority: high
state_hub_task_id: "9146f1dc-2e86-4617-8e3e-0b5e4799daa3"
```

Implement a solver that accepts selected tunable inputs and computes a valid
configuration or rejection based on constraints and comparable-customer LTV
requirements.

## Explain Solver Outcomes

```task
id: ADAPTIVE-WP-0006-T03
status: done
priority: high
state_hub_task_id: "57d6066d-088b-413c-817b-9e374f60f83a"
```

Return structured explanations for accepted and rejected tuned configurations,
including which constraints bound the result and which trade-offs were chosen.

## Pilot Against Coulomb Hybrid Models

```task
id: ADAPTIVE-WP-0006-T04
status: done
priority: medium
state_hub_task_id: "86423454-71e4-4f8e-afe0-61ceb70314c2"
```

Use the Coulomb candidate hybrid models as the first pilot surface for solver
behavior, without exposing customer-visible billing changes before validation is
trusted.

## Exit Criteria

```task
id: ADAPTIVE-WP-0006-T05
status: done
priority: medium
state_hub_task_id: "72f7d7b4-6ad2-4b63-b9de-acb7a7b81832"
```

Exit when the repo can produce and explain seller-safe tuned configurations for
at least one hybrid pricing model family.

Dependencies: `ADAPTIVE-WP-0004`, `ADAPTIVE-WP-0005`.