p2predict 0.9.0__tar.gz

p2predict-0.9.0/LICENSE

@@ -0,0 +1,121 @@
+PolyForm Noncommercial License 1.0.0
+
+Copyright (c) 2023 Ahmed K. Hafsi
+
+https://polyformproject.org/licenses/noncommercial/1.0.0
+
+## Acceptance
+
+In order to get any license under these terms, you must agree to them as
+both strict obligations and conditions to all your licenses.
+
+## Copyright License
+
+The licensor grants you a copyright license for the software to do
+everything you might do with the software that would otherwise infringe
+the licensor's copyright in it for any permitted purpose. However, you
+may only distribute the software according to Distribution License and
+make changes or new works based on the software according to Changes and
+New Works License.
+
+## Distribution License
+
+The licensor grants you an additional copyright license to distribute
+copies of the software. Your license to distribute covers distributing
+the software with changes and new works permitted by Changes and New
+Works License.
+
+## Notices
+
+You must ensure that anyone who gets a copy of any part of the software
+from you also gets a copy of these terms or the URL for them above, as
+well as copies of any plain-text lines beginning with "Required Notice:"
+that the licensor provided with the software. For example:
+
+  Required Notice: Copyright 2023 Ahmed K. Hafsi
+
+## Changes and New Works License
+
+The licensor grants you an additional copyright license to make changes
+and new works based on the software for any permitted purpose.
+
+## Patent License
+
+The licensor grants you a patent license for the software that covers
+patent claims the licensor can license, or becomes able to license, that
+you would infringe by using the software.
+
+## Noncommercial Purposes
+
+Any noncommercial purpose is a permitted purpose.
+
+## Personal Uses
+
+Personal use for research, experiment, and testing for the benefit of
+public knowledge, personal study, private entertainment, hobby projects,
+amateur pursuits, or religious observance, without any anticipated
+commercial application, is use for a noncommercial purpose.
+
+## Noncommercial Organizations
+
+Use by any charitable organization, educational institution, public
+research organization, public safety or health organization,
+environmental protection organization, or government institution is use
+for a noncommercial purpose regardless of the source of funding or
+obligations resulting from the funding.
+
+## Fair Use
+
+You may have "fair use" rights for the software under the law. These
+terms do not limit them.
+
+## No Other Rights
+
+These terms do not allow you to sublicense or transfer any of your
+licenses to anyone else, or prevent the licensor from granting licenses
+to anyone else. These terms do not imply any other licenses.
+
+## Patent Defense
+
+If you make any written claim that the software infringes or contributes
+to infringement of any patent, your patent license for the software
+granted under these terms ends immediately. If your employer makes such a
+claim, your patent license ends immediately for work on behalf of your
+employer.
+
+## Violations
+
+The first time you are notified in writing that you have violated any of
+these terms, or done anything with the software not covered by your
+licenses, the violation is automatically cured if you come into
+compliance within 32 days after receiving notice.
+
+## No Liability
+
+As far as the law allows, the software comes as is, without any warranty
+or condition, and the licensor will not be liable to you for any damages
+arising out of these terms or the use or nature of the software, under
+any kind of legal claim.
+
+## Definitions
+
+The "licensor" is the individual or entity offering these terms, and the
+"software" is the software the licensor makes available under these
+terms.
+
+"You" refers to the individual or entity agreeing to these terms.
+
+"Your company" is any legal entity, sole proprietorship, or other kind
+of organization that you work for, plus all organizations that have
+control over, are under the control of, or are under common control with
+that organization. "Control" means ownership of substantially all the
+assets of an entity, or the power to direct its management and legal
+affairs.
+
+"Your licenses" are all the licenses granted to you for the software
+under these terms.
+
+"Use" means anything you do with the software requiring one of your
+licenses.
+
+"Trademark" means trademarks, service marks, and similar rights.

p2predict-0.9.0/PKG-INFO

@@ -0,0 +1,216 @@
+Metadata-Version: 2.4
+Name: p2predict
+Version: 0.9.0
+Summary: Parametric price benchmarking for procurement and engineering — exact SHAP attribution, conformal likely-range intervals, what-if comparisons, all CLI- and agent-callable.
+Author: Ahmed Khalil Hafsi
+License-Expression: PolyForm-Noncommercial-1.0.0
+Project-URL: Homepage, https://github.com/ahmed-khalil-hafsi/P2Predict
+Project-URL: Repository, https://github.com/ahmed-khalil-hafsi/P2Predict
+Project-URL: Issues, https://github.com/ahmed-khalil-hafsi/P2Predict/issues
+Project-URL: Changelog, https://github.com/ahmed-khalil-hafsi/P2Predict/blob/main/CHANGELOG.md
+Project-URL: Roadmap, https://github.com/ahmed-khalil-hafsi/P2Predict/blob/main/ROADMAP.md
+Keywords: procurement,price-prediction,parametric-estimating,should-cost,shap,conformal-prediction,machine-learning,scikit-learn,xgboost,mcp
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Financial and Insurance Industry
+Classifier: Intended Audience :: Science/Research
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Scientific/Engineering
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: click>=8.1
+Requires-Dist: joblib>=1.2
+Requires-Dist: matplotlib>=3.7
+Requires-Dist: mpld3>=0.5
+Requires-Dist: numpy>=1.24
+Requires-Dist: pandas<3.0,>=2.0
+Requires-Dist: rich>=13.3
+Requires-Dist: scikit-learn>=1.5
+Requires-Dist: scipy>=1.10
+Requires-Dist: seaborn>=0.12
+Requires-Dist: xgboost>=1.7
+Requires-Dist: halo>=0.0.31
+Requires-Dist: questionary>=1.10
+Requires-Dist: shap<0.50,>=0.44
+Provides-Extra: mcp
+Requires-Dist: mcp>=1.0; extra == "mcp"
+Provides-Extra: dev
+Requires-Dist: pytest>=7; extra == "dev"
+Dynamic: license-file
+
+<div align="center">
+
+# P2Predict
+
+### The right price is already in your data.
+
+**P2Predict turns your purchasing history into a price model your team can talk to. Ask what a part should cost, why, and how sure the answer is, in plain language, through the AI agent you already use.**
+
+![Works with any AI agent](https://img.shields.io/badge/works%20with-any%20AI%20agent-6E56CF) &nbsp;
+![Local first](https://img.shields.io/badge/local--first-your%20data%20never%20leaves-1F8A4C) &nbsp;
+![Built for procurement](https://img.shields.io/badge/built%20for-procurement-0B6BCB) &nbsp;
+![License](https://img.shields.io/badge/license-PolyForm%20Noncommercial-555)
+
+![P2Predict MCP Demo](./documentation/p2predict_mcp_demo.gif)
+
+</div>
+
+## The problem
+
+Most of what a part costs is decided upstream, in a design review procurement never sees. An engineer tightens a tolerance beyond what the application needs, or locks the part to a single supplier, and the cost rides downstream with no number attached. By the time the BOM reaches procurement, the expensive decisions are frozen and all that is left to negotiate is the rounding.
+
+Then the quote arrives. The supplier knows their cost to the cent; you have last year's PO and a few days to respond. Multiply that across every line you buy and the leaks look the same everywhere: premiums no one benchmarked, specs no one costed, a number you cannot defend when finance asks where the savings went.
+
+The answers are already in your purchase history. Nobody has had the time to dig them out.
+
+## What P2Predict does
+
+P2Predict learns from your own purchasing data what drives the price of a part: supplier, material, size, spec, region. Then it gives your team a defensible target for any new or proposed part. Your category managers ask in plain English. The answer comes back grounded in what you have actually paid.
+
+It runs on your machine, on your data, through any AI agent your team already uses. Nothing is uploaded. No vendor catalog, no cloud, no per-seat data-sharing.
+
+## What it is, and what it isn't
+
+P2Predict is **parametric price prediction**. It learns the fundamental pricing structure in your historical buying data and benchmarks any part against it, the ones you are about to buy and the ones you already do. Being precise about that is the whole point, so here is the honest scope.
+
+**What it does**
+
+- Learns from the prices you have actually paid and predicts what a similar part should cost.
+- Attributes that predicted price to each spec and to the supplier, so you can see what is moving the number.
+- Puts a calibrated likely-range on every estimate and flags where the data is too thin to trust.
+- Improves as you give it more of your own purchase history.
+
+**What it does not do**
+
+- **It is not a should-cost tool.** It does not build a part up from raw material, labor, and machine time, and it cannot tell you a supplier's true cost or margin.
+- It only knows what your data has shown it. Ask about a part unlike anything in your history and it will widen the range or tell you to get a quote rather than guess.
+- The per-spec breakdown shows what is *associated* with price in your data. It is a read on your market, not a causal or engineering model of why a part costs what it does.
+- It does not invent data. No relevant history, no model.
+
+## The conversations it changes
+
+This is where P2Predict earns its keep. Every one of these is a real question your team can now answer in seconds, with a number and the confidence behind it.
+
+### "Is this quote fair?"
+
+Your category manager drops the quote on the agent.
+
+> **Category manager:** *"Supplier quotes $14.20 for this part. What should it cost?"*
+>
+> **P2Predict:** *"$12.40. Nine times in ten the real price lands between $10.80 and $13.90. This quote is running about 15% high."*
+
+Your category manager now knows exactly where they can push back, with real data behind it.
+
+### When the supplier pushes back: "Are you sure that's the right price?"
+
+This is where most negotiations stall. Now you have an answer. Ask for the breakdown.
+
+> **Category manager:** *"Why $12.40? Break it down."*
+>
+> **P2Predict:** *"Supplier choice +$0.85, rush delivery +$1.20, tighter tolerance +$0.42, size +$0.40."*
+
+Now you argue the components line by line: *"We agreed standard lead time. Take the $1.20 rush charge off and we're aligned."* A line item is hard to wave away.
+
+### "What if we switch supplier?"
+
+Hold the spec fixed, swap the supplier, read the delta.
+
+> **Category manager:** *"What happens if we move this 16-cell pack monitor from Supplier A to Supplier B?"*
+>
+> **P2Predict:** *"Down 37.7%, about $2.07 a unit, with the per-feature breakdown to back it up."*
+
+More targeted RFQs, and a faster sourcing decision. That number is your lever in the room.
+
+### In the design review: "Is this feature worth it?"
+
+Engineering proposes a tighter tolerance. Before it gets locked in, price it.
+
+> **Engineer:** *"We want to go from ±0.1mm to ±0.05mm."*
+>
+> **Category manager to the agent:** *"What does that do to cost?"*
+>
+> **P2Predict:** *"+$0.42 a unit, +18%, likely range $0.30 to $0.55."*
+
+Now the conversation is *"is 18% worth this requirement?"*, a priced trade-off the room can settle on numbers.
+
+### In the cost-down workshop: "What is the design paying for that it doesn't need?"
+
+Walk in with every spec priced. Which features carry real cost, which premiums are negotiable, where the design is paying for something the application never uses. Backed by your own data, with a confidence level on every finding.
+
+### RFQ triage: "Which of these 200 lines deserve a call?"
+
+Drop the whole RFQ on the agent. Every line gets a target and a range. The eight to fifteen lines that fall outside their range are the ones worth a phone call. The rest are routine. Your team spends the afternoon on what actually moves the number.
+
+## It tells you how much to trust the number
+
+Most tools hand you a number and walk away. P2Predict hands you the number **and tells you how confident to be in it**, per part, in dollars. That honesty is the whole point: a confident-but-wrong benchmark loses you credibility the moment a supplier checks it.
+
+![Honest confidence ranges, per part](./case-studies/battery-management-ics/assets/intervals_comparison.png)
+
+Three real parts, three different confidence ranges. The model is tight on the part it knows well and openly uncertain on the ones it doesn't. A narrow range means negotiate hard. A wide one means get a quote first. Your category manager always knows which.
+
+- **A confidence range on every estimate.** "$12.40, and nine times in ten the real price lands between $10.80 and $13.90."
+- **An honest map of where the model is strong and where it is thin.** P2Predict flags which parts of your category it can benchmark with confidence and which need a real quote, so nobody negotiates off a number the data can't support.
+- **A reason for every number.** Every estimate breaks down into what each spec and the supplier contribute, so you argue the components line by line.
+
+## See what actually drives the price
+
+Point P2Predict at a category and it shows you the levers. These charts come straight out of the [Battery Management ICs case study](case-studies/battery-management-ics/), built on public catalog data anyone can reproduce.
+
+**Supplier choice is the biggest lever on the board.** Same single-cell chip, identical spec, sorted by who makes it:
+
+![Supplier premium on an identical part](./case-studies/battery-management-ics/assets/manufacturer_premium.png)
+
+The premium supplier is priced at roughly four times the value option for the same part. That is a number you take into a negotiation, backed by your own data.
+
+**Every estimate breaks down spec by spec.** Ask why a part is priced the way it is and you get the full breakdown:
+
+![Per-feature dollar breakdown for one part](./case-studies/battery-management-ics/assets/ev_bms_attribution.png)
+
+Package size, supplier premium, multi-cell architecture: each one in dollars, each one adding up exactly to the predicted price. This is what lets your category manager say *"I know what I'm paying for, and here's the line I want to cut."*
+
+## How it fits your stack
+
+**You don't use P2Predict; your agent does.** It speaks to **any AI agent** through a standard connector — Claude, GPT, or a local model — so your category managers never learn a new tool. They ask the assistant they already use, and it runs the analysis for them. This is agentic-first: there is no dashboard and no app, the interface is the agent you already have.
+
+Everything runs **on your own machine**. Your purchasing data is your most sensitive commercial asset, so P2Predict never uploads it and no third party trains on it. Pair it with a local model to keep the whole loop offline, or with a cloud agent if you prefer; either way your raw spend stays put, with no data-residency conversation to have with legal.
+
+It complements should-cost tools, it does not replace them. Bottom-up should-costing builds a part up from material, labor, and machine time to estimate what it *should cost to make*. P2Predict does not do that and is not trying to. It answers the other question every category manager actually asks: *what has the market charged us for parts like this, and what should we expect to pay for the next one?*
+
+## Proof on public data
+
+Three worked case studies, each reproducible end to end on data anyone can download:
+
+- **[Battery Management ICs](case-studies/battery-management-ics/):** the closest thing to a real procurement job. A small, realistic parts slice, a supplier-premium lever you can quote, and an honest read on where the model is strong and where it needs a real quote.
+- **[Used vehicles](case-studies/used-cars/):** the easy-to-follow walkthrough on prices that span orders of magnitude.
+- **[Aerospace fasteners](case-studies/aerospace-fasteners/):** the honesty story. How P2Predict shows you when the data itself sets the limit, so you stop chasing accuracy the data can't give.
+
+Each one leads with results, shows where to trust them, and points to exactly where every number comes from.
+
+## Who built it
+
+P2Predict is built and maintained by **[Ahmed K. Hafsi](https://ahmedhafsi.com)**, Senior Manager of Negotiation Excellence at Infineon, where he leads negotiation strategy across automotive, semiconductor, consumer, and chemicals categories in Asia-Pacific. He built and led Dyson's global Negotiation Excellence capability and advised on negotiation and applied game theory at TWS Partners in Munich and London. He trained as an engineer at the Karlsruhe Institute of Technology and works across three continents in four languages.
+
+P2Predict comes out of that work: the tools a procurement team actually needs to walk into a negotiation knowing its number and its leverage. More on his approach to negotiation, pricing, and game theory at **[ahmedhafsi.com](https://ahmedhafsi.com)**.
+
+## Try it / set it up
+
+- **Set it up with your agent:** see **[INSTALL.md](INSTALL.md)** to install, connect your AI assistant, and point it at your data.
+- **How it works under the hood:** the models, the math, the full reference live in **[TECHNICAL.md](TECHNICAL.md)**.
+
+## Licensing
+
+Source-available under the [PolyForm Noncommercial License 1.0.0](LICENSE).
+
+- **Free for internal use:** use P2Predict inside your own organization at no cost.
+- **Commercial use requires a license:** deploying for clients, embedding it in a paid service, or consulting engagements.
+
+For a commercial license, a partnership, or to share a procurement dataset, reach out: **[ahmedhafsi.com/contact](https://ahmedhafsi.com/contact/)**.
+
+© Ahmed K. Hafsi. P2Predict is a copyrighted work; all rights reserved except as granted under the license above.

p2predict-0.9.0/README.md

@@ -0,0 +1,170 @@
+<div align="center">
+
+# P2Predict
+
+### The right price is already in your data.
+
+**P2Predict turns your purchasing history into a price model your team can talk to. Ask what a part should cost, why, and how sure the answer is, in plain language, through the AI agent you already use.**
+
+![Works with any AI agent](https://img.shields.io/badge/works%20with-any%20AI%20agent-6E56CF) &nbsp;
+![Local first](https://img.shields.io/badge/local--first-your%20data%20never%20leaves-1F8A4C) &nbsp;
+![Built for procurement](https://img.shields.io/badge/built%20for-procurement-0B6BCB) &nbsp;
+![License](https://img.shields.io/badge/license-PolyForm%20Noncommercial-555)
+
+![P2Predict MCP Demo](./documentation/p2predict_mcp_demo.gif)
+
+</div>
+
+## The problem
+
+Most of what a part costs is decided upstream, in a design review procurement never sees. An engineer tightens a tolerance beyond what the application needs, or locks the part to a single supplier, and the cost rides downstream with no number attached. By the time the BOM reaches procurement, the expensive decisions are frozen and all that is left to negotiate is the rounding.
+
+Then the quote arrives. The supplier knows their cost to the cent; you have last year's PO and a few days to respond. Multiply that across every line you buy and the leaks look the same everywhere: premiums no one benchmarked, specs no one costed, a number you cannot defend when finance asks where the savings went.
+
+The answers are already in your purchase history. Nobody has had the time to dig them out.
+
+## What P2Predict does
+
+P2Predict learns from your own purchasing data what drives the price of a part: supplier, material, size, spec, region. Then it gives your team a defensible target for any new or proposed part. Your category managers ask in plain English. The answer comes back grounded in what you have actually paid.
+
+It runs on your machine, on your data, through any AI agent your team already uses. Nothing is uploaded. No vendor catalog, no cloud, no per-seat data-sharing.
+
+## What it is, and what it isn't
+
+P2Predict is **parametric price prediction**. It learns the fundamental pricing structure in your historical buying data and benchmarks any part against it, the ones you are about to buy and the ones you already do. Being precise about that is the whole point, so here is the honest scope.
+
+**What it does**
+
+- Learns from the prices you have actually paid and predicts what a similar part should cost.
+- Attributes that predicted price to each spec and to the supplier, so you can see what is moving the number.
+- Puts a calibrated likely-range on every estimate and flags where the data is too thin to trust.
+- Improves as you give it more of your own purchase history.
+
+**What it does not do**
+
+- **It is not a should-cost tool.** It does not build a part up from raw material, labor, and machine time, and it cannot tell you a supplier's true cost or margin.
+- It only knows what your data has shown it. Ask about a part unlike anything in your history and it will widen the range or tell you to get a quote rather than guess.
+- The per-spec breakdown shows what is *associated* with price in your data. It is a read on your market, not a causal or engineering model of why a part costs what it does.
+- It does not invent data. No relevant history, no model.
+
+## The conversations it changes
+
+This is where P2Predict earns its keep. Every one of these is a real question your team can now answer in seconds, with a number and the confidence behind it.
+
+### "Is this quote fair?"
+
+Your category manager drops the quote on the agent.
+
+> **Category manager:** *"Supplier quotes $14.20 for this part. What should it cost?"*
+>
+> **P2Predict:** *"$12.40. Nine times in ten the real price lands between $10.80 and $13.90. This quote is running about 15% high."*
+
+Your category manager now knows exactly where they can push back, with real data behind it.
+
+### When the supplier pushes back: "Are you sure that's the right price?"
+
+This is where most negotiations stall. Now you have an answer. Ask for the breakdown.
+
+> **Category manager:** *"Why $12.40? Break it down."*
+>
+> **P2Predict:** *"Supplier choice +$0.85, rush delivery +$1.20, tighter tolerance +$0.42, size +$0.40."*
+
+Now you argue the components line by line: *"We agreed standard lead time. Take the $1.20 rush charge off and we're aligned."* A line item is hard to wave away.
+
+### "What if we switch supplier?"
+
+Hold the spec fixed, swap the supplier, read the delta.
+
+> **Category manager:** *"What happens if we move this 16-cell pack monitor from Supplier A to Supplier B?"*
+>
+> **P2Predict:** *"Down 37.7%, about $2.07 a unit, with the per-feature breakdown to back it up."*
+
+More targeted RFQs, and a faster sourcing decision. That number is your lever in the room.
+
+### In the design review: "Is this feature worth it?"
+
+Engineering proposes a tighter tolerance. Before it gets locked in, price it.
+
+> **Engineer:** *"We want to go from ±0.1mm to ±0.05mm."*
+>
+> **Category manager to the agent:** *"What does that do to cost?"*
+>
+> **P2Predict:** *"+$0.42 a unit, +18%, likely range $0.30 to $0.55."*
+
+Now the conversation is *"is 18% worth this requirement?"*, a priced trade-off the room can settle on numbers.
+
+### In the cost-down workshop: "What is the design paying for that it doesn't need?"
+
+Walk in with every spec priced. Which features carry real cost, which premiums are negotiable, where the design is paying for something the application never uses. Backed by your own data, with a confidence level on every finding.
+
+### RFQ triage: "Which of these 200 lines deserve a call?"
+
+Drop the whole RFQ on the agent. Every line gets a target and a range. The eight to fifteen lines that fall outside their range are the ones worth a phone call. The rest are routine. Your team spends the afternoon on what actually moves the number.
+
+## It tells you how much to trust the number
+
+Most tools hand you a number and walk away. P2Predict hands you the number **and tells you how confident to be in it**, per part, in dollars. That honesty is the whole point: a confident-but-wrong benchmark loses you credibility the moment a supplier checks it.
+
+![Honest confidence ranges, per part](./case-studies/battery-management-ics/assets/intervals_comparison.png)
+
+Three real parts, three different confidence ranges. The model is tight on the part it knows well and openly uncertain on the ones it doesn't. A narrow range means negotiate hard. A wide one means get a quote first. Your category manager always knows which.
+
+- **A confidence range on every estimate.** "$12.40, and nine times in ten the real price lands between $10.80 and $13.90."
+- **An honest map of where the model is strong and where it is thin.** P2Predict flags which parts of your category it can benchmark with confidence and which need a real quote, so nobody negotiates off a number the data can't support.
+- **A reason for every number.** Every estimate breaks down into what each spec and the supplier contribute, so you argue the components line by line.
+
+## See what actually drives the price
+
+Point P2Predict at a category and it shows you the levers. These charts come straight out of the [Battery Management ICs case study](case-studies/battery-management-ics/), built on public catalog data anyone can reproduce.
+
+**Supplier choice is the biggest lever on the board.** Same single-cell chip, identical spec, sorted by who makes it:
+
+![Supplier premium on an identical part](./case-studies/battery-management-ics/assets/manufacturer_premium.png)
+
+The premium supplier is priced at roughly four times the value option for the same part. That is a number you take into a negotiation, backed by your own data.
+
+**Every estimate breaks down spec by spec.** Ask why a part is priced the way it is and you get the full breakdown:
+
+![Per-feature dollar breakdown for one part](./case-studies/battery-management-ics/assets/ev_bms_attribution.png)
+
+Package size, supplier premium, multi-cell architecture: each one in dollars, each one adding up exactly to the predicted price. This is what lets your category manager say *"I know what I'm paying for, and here's the line I want to cut."*
+
+## How it fits your stack
+
+**You don't use P2Predict; your agent does.** It speaks to **any AI agent** through a standard connector — Claude, GPT, or a local model — so your category managers never learn a new tool. They ask the assistant they already use, and it runs the analysis for them. This is agentic-first: there is no dashboard and no app, the interface is the agent you already have.
+
+Everything runs **on your own machine**. Your purchasing data is your most sensitive commercial asset, so P2Predict never uploads it and no third party trains on it. Pair it with a local model to keep the whole loop offline, or with a cloud agent if you prefer; either way your raw spend stays put, with no data-residency conversation to have with legal.
+
+It complements should-cost tools, it does not replace them. Bottom-up should-costing builds a part up from material, labor, and machine time to estimate what it *should cost to make*. P2Predict does not do that and is not trying to. It answers the other question every category manager actually asks: *what has the market charged us for parts like this, and what should we expect to pay for the next one?*
+
+## Proof on public data
+
+Three worked case studies, each reproducible end to end on data anyone can download:
+
+- **[Battery Management ICs](case-studies/battery-management-ics/):** the closest thing to a real procurement job. A small, realistic parts slice, a supplier-premium lever you can quote, and an honest read on where the model is strong and where it needs a real quote.
+- **[Used vehicles](case-studies/used-cars/):** the easy-to-follow walkthrough on prices that span orders of magnitude.
+- **[Aerospace fasteners](case-studies/aerospace-fasteners/):** the honesty story. How P2Predict shows you when the data itself sets the limit, so you stop chasing accuracy the data can't give.
+
+Each one leads with results, shows where to trust them, and points to exactly where every number comes from.
+
+## Who built it
+
+P2Predict is built and maintained by **[Ahmed K. Hafsi](https://ahmedhafsi.com)**, Senior Manager of Negotiation Excellence at Infineon, where he leads negotiation strategy across automotive, semiconductor, consumer, and chemicals categories in Asia-Pacific. He built and led Dyson's global Negotiation Excellence capability and advised on negotiation and applied game theory at TWS Partners in Munich and London. He trained as an engineer at the Karlsruhe Institute of Technology and works across three continents in four languages.
+
+P2Predict comes out of that work: the tools a procurement team actually needs to walk into a negotiation knowing its number and its leverage. More on his approach to negotiation, pricing, and game theory at **[ahmedhafsi.com](https://ahmedhafsi.com)**.
+
+## Try it / set it up
+
+- **Set it up with your agent:** see **[INSTALL.md](INSTALL.md)** to install, connect your AI assistant, and point it at your data.
+- **How it works under the hood:** the models, the math, the full reference live in **[TECHNICAL.md](TECHNICAL.md)**.
+
+## Licensing
+
+Source-available under the [PolyForm Noncommercial License 1.0.0](LICENSE).
+
+- **Free for internal use:** use P2Predict inside your own organization at no cost.
+- **Commercial use requires a license:** deploying for clients, embedding it in a paid service, or consulting engagements.
+
+For a commercial license, a partnership, or to share a procurement dataset, reach out: **[ahmedhafsi.com/contact](https://ahmedhafsi.com/contact/)**.
+
+© Ahmed K. Hafsi. P2Predict is a copyrighted work; all rights reserved except as granted under the license above.

p2predict-0.9.0/pyproject.toml

@@ -0,0 +1,81 @@
+[build-system]
+requires = ["setuptools>=68", "wheel"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "p2predict"
+version = "0.9.0"
+description = "Parametric price benchmarking for procurement and engineering — exact SHAP attribution, conformal likely-range intervals, what-if comparisons, all CLI- and agent-callable."
+readme = "README.md"
+license = "PolyForm-Noncommercial-1.0.0"
+license-files = ["LICENSE"]
+authors = [{name = "Ahmed Khalil Hafsi"}]
+requires-python = ">=3.10"
+keywords = [
+    "procurement",
+    "price-prediction",
+    "parametric-estimating",
+    "should-cost",
+    "shap",
+    "conformal-prediction",
+    "machine-learning",
+    "scikit-learn",
+    "xgboost",
+    "mcp",
+]
+classifiers = [
+    "Development Status :: 4 - Beta",
+    "Intended Audience :: Developers",
+    "Intended Audience :: Financial and Insurance Industry",
+    "Intended Audience :: Science/Research",
+    "Operating System :: OS Independent",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.10",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Topic :: Scientific/Engineering",
+    "Topic :: Scientific/Engineering :: Artificial Intelligence",
+]
+dependencies = [
+    "click>=8.1",
+    "joblib>=1.2",
+    "matplotlib>=3.7",
+    "mpld3>=0.5",
+    "numpy>=1.24",
+    "pandas>=2.0,<3.0",
+    "rich>=13.3",
+    "scikit-learn>=1.5",
+    "scipy>=1.10",
+    "seaborn>=0.12",
+    "xgboost>=1.7",
+    "halo>=0.0.31",
+    "questionary>=1.10",
+    "shap>=0.44,<0.50",
+]
+
+[project.optional-dependencies]
+mcp = [
+    "mcp>=1.0",
+]
+dev = [
+    "pytest>=7",
+]
+
+[project.urls]
+Homepage = "https://github.com/ahmed-khalil-hafsi/P2Predict"
+Repository = "https://github.com/ahmed-khalil-hafsi/P2Predict"
+Issues = "https://github.com/ahmed-khalil-hafsi/P2Predict/issues"
+Changelog = "https://github.com/ahmed-khalil-hafsi/P2Predict/blob/main/CHANGELOG.md"
+Roadmap = "https://github.com/ahmed-khalil-hafsi/P2Predict/blob/main/ROADMAP.md"
+
+[project.scripts]
+p2predict = "p2predict.cli.predict:main"
+p2predict-train = "p2predict.cli.train:train"
+p2predict-mcp = "p2predict.mcp.server:main"
+
+[tool.setuptools.packages.find]
+where = ["src"]
+include = ["p2predict*"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]

p2predict-0.9.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+