aidflow 3.0.0__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- aidflow-3.0.0/PKG-INFO +24 -0
- aidflow-3.0.0/README.md +16 -0
- aidflow-3.0.0/aidflow/__init__.py +0 -0
- aidflow-3.0.0/pyproject.toml +11 -0
aidflow-3.0.0/PKG-INFO
ADDED
|
@@ -0,0 +1,24 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: aidflow
|
|
3
|
+
Version: 3.0.0
|
|
4
|
+
Summary: Pipeline execution framework
|
|
5
|
+
Author-email: AIGENSYS <info@aigensys.com>
|
|
6
|
+
Requires-Python: >=3.13
|
|
7
|
+
Description-Content-Type: text/markdown
|
|
8
|
+
|
|
9
|
+
# AIDflow
|
|
10
|
+
|
|
11
|
+
Most ML tools are simple wrappers around Scikit-Learn—they automate the process but hide the logic, creating a "black box" that regulators reject. AIDflow is different.
|
|
12
|
+
|
|
13
|
+
AIDflow is designed specifically for high-stakes environments (Fintech, Banking, Insurance) where a model isn't just a file—it's a legal document.
|
|
14
|
+
We provide a full ecosystem for scorecard development that prioritizes *Human-in-the-Loop Governance*:
|
|
15
|
+
|
|
16
|
+
*Absolute Micromanagement*: While the pipeline is automated, every single step is transparent and open. Users can pause, intervene, and fine-tune any parameter at any layer—from raw ingestion to final champion selection.
|
|
17
|
+
*Audit-Ready Reporting*: Every phase generates comprehensive, industry-standard reports. We don't just give you an accuracy score; we provide the evidence required for internal risk committees and external regulators.
|
|
18
|
+
*Production Scorecard Readiness*: The output is not just a .pkl file—it is a fully validated production scorecard, complete with stability metrics and explainability vectors that meet the strictest global financial standards.
|
|
19
|
+
*The Governance Gap*: AIDflow fills the void between "fast prototyping" and "compliant deployment," ensuring your models are as robust in the eyes of a regulator as they are in a Jupyter notebook.
|
|
20
|
+
|
|
21
|
+
## Why this is a winning strategy:
|
|
22
|
+
It solves the "Fear of Automation": By using words like "Micromanagement" and "Human-in-the-Loop," you tell the bank's risk officer that they are still in control.
|
|
23
|
+
It targets high-value niches: Mentioning "Regulators," "Scorecards," and "Financial Industry" immediately moves your product from a "hobbyist tool" to a "mission-critical enterprise asset."
|
|
24
|
+
It defines the category: You aren't competing with Scikit-Learn; you are creating a new category: Regulatory Scorecard Orchestration.
|
aidflow-3.0.0/README.md
ADDED
|
@@ -0,0 +1,16 @@
|
|
|
1
|
+
# AIDflow
|
|
2
|
+
|
|
3
|
+
Most ML tools are simple wrappers around Scikit-Learn—they automate the process but hide the logic, creating a "black box" that regulators reject. AIDflow is different.
|
|
4
|
+
|
|
5
|
+
AIDflow is designed specifically for high-stakes environments (Fintech, Banking, Insurance) where a model isn't just a file—it's a legal document.
|
|
6
|
+
We provide a full ecosystem for scorecard development that prioritizes *Human-in-the-Loop Governance*:
|
|
7
|
+
|
|
8
|
+
*Absolute Micromanagement*: While the pipeline is automated, every single step is transparent and open. Users can pause, intervene, and fine-tune any parameter at any layer—from raw ingestion to final champion selection.
|
|
9
|
+
*Audit-Ready Reporting*: Every phase generates comprehensive, industry-standard reports. We don't just give you an accuracy score; we provide the evidence required for internal risk committees and external regulators.
|
|
10
|
+
*Production Scorecard Readiness*: The output is not just a .pkl file—it is a fully validated production scorecard, complete with stability metrics and explainability vectors that meet the strictest global financial standards.
|
|
11
|
+
*The Governance Gap*: AIDflow fills the void between "fast prototyping" and "compliant deployment," ensuring your models are as robust in the eyes of a regulator as they are in a Jupyter notebook.
|
|
12
|
+
|
|
13
|
+
## Why this is a winning strategy:
|
|
14
|
+
It solves the "Fear of Automation": By using words like "Micromanagement" and "Human-in-the-Loop," you tell the bank's risk officer that they are still in control.
|
|
15
|
+
It targets high-value niches: Mentioning "Regulators," "Scorecards," and "Financial Industry" immediately moves your product from a "hobbyist tool" to a "mission-critical enterprise asset."
|
|
16
|
+
It defines the category: You aren't competing with Scikit-Learn; you are creating a new category: Regulatory Scorecard Orchestration.
|
|
File without changes
|
|
@@ -0,0 +1,11 @@
|
|
|
1
|
+
[build-system]
|
|
2
|
+
requires = ["hatchling"]
|
|
3
|
+
build-backend = "hatchling.build"
|
|
4
|
+
|
|
5
|
+
[project]
|
|
6
|
+
name = "aidflow"
|
|
7
|
+
version = "3.0.0"
|
|
8
|
+
description = "Pipeline execution framework"
|
|
9
|
+
readme = "README.md"
|
|
10
|
+
authors = [{ name = "AIGENSYS", email = "info@aigensys.com" }]
|
|
11
|
+
requires-python = ">=3.13"
|