aidflow 3.0.0__tar.gz → 3.0.1__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.1/PKG-INFO ADDED
@@ -0,0 +1,162 @@
1
+ Metadata-Version: 2.4
2
+ Name: aidflow
3
+ Version: 3.0.1
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
+ **Human-in-the-Loop Scorecard Orchestration for Regulated ML**
12
+
13
+ [![PyPI version](https://img.shields.io/pypi/v/aidflow.svg?color=blue)](https://pypi.org/project/aidflow/)
14
+ [![Python Version](https://img.shields.io/pypi/pyversions/aidflow.svg)](https://pypi.org/project/aidflow/)
15
+ [![License](https://img.shields.io/badge/License-Custom-informational.svg)](LICENSE)
16
+ [![Code Style](https://img.shields.io/badge/code%20style-black-000000.svg)](https://github.com/psf/black)
17
+
18
+ ---
19
+
20
+ Most automated machine learning tools act as black-box wrappers—they optimize metrics in isolation while hiding the underlying logic, producing models that risk failure during regulatory scrutiny. **AIDflow is built differently.**
21
+
22
+ Designed specifically for high-stakes, highly regulated industries (**Fintech, Banking, Insurance**), AIDflow treats machine learning models not as opaque binary artifacts, but as **auditable, legal assets**. It provides a comprehensive ecosystem for scorecard development built around **Human-in-the-Loop Governance**.
23
+
24
+ ---
25
+
26
+ ## 🏛️ Core Pillars
27
+
28
+ ### 🎯 Absolute Micromanagement
29
+ Automation should never mean a loss of control. While AIDflow automates repetitive pipeline mechanics, every layer remains fully transparent and configurable.
30
+ Practitioners can pause execution, inspect intermediate states, and fine-tune parameters—from raw feature ingestion and binning to final champion model selection.
31
+
32
+ ### 📋 Audit-Ready Reporting
33
+ Every execution phase generates comprehensive, standardized documentation out of the box.
34
+ AIDflow goes beyond traditional accuracy metrics ($AUC$, $Gini$) to produce full validation artifacts required by internal risk committees and external financial regulators.
35
+
36
+ ### 🛡️ Production Scorecard Readiness
37
+ Outputs extend far beyond standard estimator binaries (`.pkl` / `.joblib`). AIDflow generates fully engineered production scorecards complete with Population Stability Index ($PSI$),
38
+ Characteristic Stability Index ($CSI$), score transformations, and feature explainability vectors that satisfy international credit risk standards (e.g., Basel II/III, IFRS 9).
39
+
40
+ ### ⚡ Bridging the Governance Gap
41
+ AIDflow eliminates the friction between rapid experimental prototyping and enterprise compliance—ensuring models that perform in a Jupyter notebook transition seamlessly into compliant production environments.
42
+
43
+ ---
44
+
45
+ ## 🚀 Quick Start
46
+
47
+ ### Installation
48
+
49
+ ```bash
50
+ pip install aidflow
51
+ ```
52
+
53
+ ### Basic Usage
54
+
55
+ Defining the Project Context (Control Plane) & Project Scope:
56
+
57
+ ```python
58
+ import aidflow as aid
59
+
60
+ ctx = aid.ProjectContext()
61
+
62
+ ctx.genesis(
63
+ project = 'test',
64
+ input_data = 'test.csv',
65
+ target = 'target',
66
+ yy_mm = 'decision_date',
67
+ yy_mm_format = '%d%b%y'
68
+ )
69
+ ctx.params()
70
+ ```
71
+
72
+ **Worker → Model**
73
+
74
+ Accessing worker's inputs schema → parameters & types:
75
+
76
+ ```python
77
+ ctx.workers.data_loader.inputs
78
+ ```
79
+
80
+ Accessing worker's fitter options and schema → parameters & types:
81
+
82
+ ```python
83
+ ctx.workers.data_loader.fitters
84
+ ```
85
+
86
+ Executing worker with defaults → auto provided by the context:
87
+
88
+ ```python
89
+ ctx.workers.data_loader()
90
+ ```
91
+
92
+ Once worker has been executed, thus its main model has been built,\
93
+ we have access to all populated attributes.
94
+
95
+ ```python
96
+ ctx.workers.data_loader.inputs.inputs
97
+ ctx.workers.data_loader.result
98
+ ctx.workers.data_loader.state
99
+ ctx.workers.data_loader.features
100
+ ctx.workers.data_loader.stats
101
+ ctx.workers.data_loader.params
102
+ ctx.workers.data_loader.fitter # jump to chosen internal fitter
103
+ ...
104
+ ```
105
+
106
+ View to model report of executed worker:
107
+
108
+ ```python
109
+ ctx.workers.data_loader.report.show()
110
+ ```
111
+
112
+ **Model → Fitter**
113
+
114
+ Once worker has been executed, we obtain internal fitter state\
115
+ and its parametrization:
116
+
117
+ ```python
118
+ ctx.workers.data_loader.fitter
119
+ ```
120
+
121
+ The fitted fitter provides all populated attributes.
122
+
123
+ ```python
124
+ ctx.workers.data_loader.fitter.stats
125
+ ctx.workers.data_loader.fitter.params
126
+ ```
127
+
128
+ Direct choice and parametrization of internal fitter:
129
+
130
+ ```python
131
+ fx = ctx.registry.data_loader[0]
132
+ prm = dict(
133
+ flow_vars = ['target1', 'target2'],
134
+ columns_subset = ['fe1', 'fe2']
135
+ )
136
+ loader = ctx.workers.data_loader(fx_choice = fx, fx_params = prm)
137
+ ```
138
+
139
+ In the experimenting phase when various targets might be under testing\
140
+ (*note that target2 must be present in the data*):
141
+
142
+ ```python
143
+ cfg = dict(
144
+ target = 'target2',
145
+ )
146
+ woe = ctx.workers.data_loader(fx_config = cfg)
147
+ ```
148
+
149
+ ### Pipeline Architecture
150
+ [ Raw Data Ingestion ]
151
+ │
152
+ ▼
153
+ [ Feature Binning & WOE Transformation ] ──► (Human-in-the-Loop Adjustments)
154
+ │
155
+ ▼
156
+ [ Multi-Constraint Feature Selection ] ──► (PSI / Monotonicity Filtering)
157
+ │
158
+ ▼
159
+ [ Scorecard Scaling & Alignment ] ──► (Points to Double Odds Setup)
160
+ │
161
+ ▼
162
+ [ Audit Report & Model Artifacts ] ──► (Compliance PDF & Production Rules)
@@ -0,0 +1,154 @@
1
+ # AIDflow
2
+
3
+ **Human-in-the-Loop Scorecard Orchestration for Regulated ML**
4
+
5
+ [![PyPI version](https://img.shields.io/pypi/v/aidflow.svg?color=blue)](https://pypi.org/project/aidflow/)
6
+ [![Python Version](https://img.shields.io/pypi/pyversions/aidflow.svg)](https://pypi.org/project/aidflow/)
7
+ [![License](https://img.shields.io/badge/License-Custom-informational.svg)](LICENSE)
8
+ [![Code Style](https://img.shields.io/badge/code%20style-black-000000.svg)](https://github.com/psf/black)
9
+
10
+ ---
11
+
12
+ Most automated machine learning tools act as black-box wrappers—they optimize metrics in isolation while hiding the underlying logic, producing models that risk failure during regulatory scrutiny. **AIDflow is built differently.**
13
+
14
+ Designed specifically for high-stakes, highly regulated industries (**Fintech, Banking, Insurance**), AIDflow treats machine learning models not as opaque binary artifacts, but as **auditable, legal assets**. It provides a comprehensive ecosystem for scorecard development built around **Human-in-the-Loop Governance**.
15
+
16
+ ---
17
+
18
+ ## 🏛️ Core Pillars
19
+
20
+ ### 🎯 Absolute Micromanagement
21
+ Automation should never mean a loss of control. While AIDflow automates repetitive pipeline mechanics, every layer remains fully transparent and configurable.
22
+ Practitioners can pause execution, inspect intermediate states, and fine-tune parameters—from raw feature ingestion and binning to final champion model selection.
23
+
24
+ ### 📋 Audit-Ready Reporting
25
+ Every execution phase generates comprehensive, standardized documentation out of the box.
26
+ AIDflow goes beyond traditional accuracy metrics ($AUC$, $Gini$) to produce full validation artifacts required by internal risk committees and external financial regulators.
27
+
28
+ ### 🛡️ Production Scorecard Readiness
29
+ Outputs extend far beyond standard estimator binaries (`.pkl` / `.joblib`). AIDflow generates fully engineered production scorecards complete with Population Stability Index ($PSI$),
30
+ Characteristic Stability Index ($CSI$), score transformations, and feature explainability vectors that satisfy international credit risk standards (e.g., Basel II/III, IFRS 9).
31
+
32
+ ### ⚡ Bridging the Governance Gap
33
+ AIDflow eliminates the friction between rapid experimental prototyping and enterprise compliance—ensuring models that perform in a Jupyter notebook transition seamlessly into compliant production environments.
34
+
35
+ ---
36
+
37
+ ## 🚀 Quick Start
38
+
39
+ ### Installation
40
+
41
+ ```bash
42
+ pip install aidflow
43
+ ```
44
+
45
+ ### Basic Usage
46
+
47
+ Defining the Project Context (Control Plane) & Project Scope:
48
+
49
+ ```python
50
+ import aidflow as aid
51
+
52
+ ctx = aid.ProjectContext()
53
+
54
+ ctx.genesis(
55
+ project = 'test',
56
+ input_data = 'test.csv',
57
+ target = 'target',
58
+ yy_mm = 'decision_date',
59
+ yy_mm_format = '%d%b%y'
60
+ )
61
+ ctx.params()
62
+ ```
63
+
64
+ **Worker → Model**
65
+
66
+ Accessing worker's inputs schema → parameters & types:
67
+
68
+ ```python
69
+ ctx.workers.data_loader.inputs
70
+ ```
71
+
72
+ Accessing worker's fitter options and schema → parameters & types:
73
+
74
+ ```python
75
+ ctx.workers.data_loader.fitters
76
+ ```
77
+
78
+ Executing worker with defaults → auto provided by the context:
79
+
80
+ ```python
81
+ ctx.workers.data_loader()
82
+ ```
83
+
84
+ Once worker has been executed, thus its main model has been built,\
85
+ we have access to all populated attributes.
86
+
87
+ ```python
88
+ ctx.workers.data_loader.inputs.inputs
89
+ ctx.workers.data_loader.result
90
+ ctx.workers.data_loader.state
91
+ ctx.workers.data_loader.features
92
+ ctx.workers.data_loader.stats
93
+ ctx.workers.data_loader.params
94
+ ctx.workers.data_loader.fitter # jump to chosen internal fitter
95
+ ...
96
+ ```
97
+
98
+ View to model report of executed worker:
99
+
100
+ ```python
101
+ ctx.workers.data_loader.report.show()
102
+ ```
103
+
104
+ **Model → Fitter**
105
+
106
+ Once worker has been executed, we obtain internal fitter state\
107
+ and its parametrization:
108
+
109
+ ```python
110
+ ctx.workers.data_loader.fitter
111
+ ```
112
+
113
+ The fitted fitter provides all populated attributes.
114
+
115
+ ```python
116
+ ctx.workers.data_loader.fitter.stats
117
+ ctx.workers.data_loader.fitter.params
118
+ ```
119
+
120
+ Direct choice and parametrization of internal fitter:
121
+
122
+ ```python
123
+ fx = ctx.registry.data_loader[0]
124
+ prm = dict(
125
+ flow_vars = ['target1', 'target2'],
126
+ columns_subset = ['fe1', 'fe2']
127
+ )
128
+ loader = ctx.workers.data_loader(fx_choice = fx, fx_params = prm)
129
+ ```
130
+
131
+ In the experimenting phase when various targets might be under testing\
132
+ (*note that target2 must be present in the data*):
133
+
134
+ ```python
135
+ cfg = dict(
136
+ target = 'target2',
137
+ )
138
+ woe = ctx.workers.data_loader(fx_config = cfg)
139
+ ```
140
+
141
+ ### Pipeline Architecture
142
+ [ Raw Data Ingestion ]
143
+ │
144
+ ▼
145
+ [ Feature Binning & WOE Transformation ] ──► (Human-in-the-Loop Adjustments)
146
+ │
147
+ ▼
148
+ [ Multi-Constraint Feature Selection ] ──► (PSI / Monotonicity Filtering)
149
+ │
150
+ ▼
151
+ [ Scorecard Scaling & Alignment ] ──► (Points to Double Odds Setup)
152
+ │
153
+ ▼
154
+ [ Audit Report & Model Artifacts ] ──► (Compliance PDF & Production Rules)
@@ -0,0 +1,4 @@
1
+ python -m build
2
+ twine upload dist/*
3
+ username: __token__
4
+ password: api token
@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
4
4
 
5
5
  [project]
6
6
  name = "aidflow"
7
- version = "3.0.0"
7
+ version = "3.0.1"
8
8
  description = "Pipeline execution framework"
9
9
  readme = "README.md"
10
10
  authors = [{ name = "AIGENSYS", email = "info@aigensys.com" }]
aidflow-3.0.0/PKG-INFO DELETED
@@ -1,24 +0,0 @@
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 DELETED
@@ -1,16 +0,0 @@
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