Bluefly Technology Reduction

Stop maintaining what you no longer need.

A commercial offer, not a platform product. Registered in products/AUTHORITY-MATRIX.md under Commercial offer authority.

File	Is the single authority for
Product-Definition.md	The offer: names, promise, buyer, trigger, measures, scope, pricing basis, classification, kill criteria
Delivery-Method.md	How Maintenance Review, Safe Removal and Maintenance Watch are delivered
Sales-Package.md	Customer-facing copy: one-pager, landing page, 8-slide deck, talk track
Delivery-Kit.md	The 12 reusable artifacts, each a projection of the data model
data-model.yaml	Every field used anywhere in the engagement
Demonstration.md	One worked example, end to end. Illustrative — not customer evidence

Three stages of one offer

MAINTENANCE REVIEW   ->  Deletion Plan        what can go?
SAFE REMOVAL         ->  verified removals    prove it, then remove it
MAINTENANCE WATCH    ->  2 lists per quarter  stop it growing back

The rules that keep this from drifting

1. No artifact invents a field. Add it to data-model.yaml first. 92 field references across these documents currently resolve to the model; zero orphans.
2. No number without provenance. source, assumption, customer_confirmed — or it is not shown to a customer.
3. No removal without a named approver and a tested rollback path.
4. No NOW rank on vendor documentation alone. That shortcut turns this offer into an outage generator.
5. Success is WHAT_THE_CUSTOMER_NO_LONGER_HAS_TO_OWN — never code produced, hours consumed or agents deployed.

What this offer does not require

No new software platform, app, portal or dashboard is built to sell or deliver it. ContextControl may later carry delivery evidence or customer visibility; it is not a dependency.