AbstractIntegratedModule 0.3.0__tar.gz → 0.3.2__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.
Files changed (16) hide show
  1. abstractintegratedmodule-0.3.2/AbstractIntegratedModule.cp313-win_amd64.pyd +0 -0
  2. {abstractintegratedmodule-0.3.0 → abstractintegratedmodule-0.3.2}/AbstractIntegratedModule.cpython-310-aarch64-linux-gnu.so +0 -0
  3. {abstractintegratedmodule-0.3.0 → abstractintegratedmodule-0.3.2}/AbstractIntegratedModule.cpython-312-x86_64-linux-gnu.so +0 -0
  4. {abstractintegratedmodule-0.3.0 → abstractintegratedmodule-0.3.2}/AbstractIntegratedModule.egg-info/PKG-INFO +62 -17
  5. {abstractintegratedmodule-0.3.0 → abstractintegratedmodule-0.3.2}/AbstractIntegratedModule.py +1179 -124
  6. abstractintegratedmodule-0.3.0/README.md → abstractintegratedmodule-0.3.2/PKG-INFO +1148 -1071
  7. abstractintegratedmodule-0.3.0/PKG-INFO → abstractintegratedmodule-0.3.2/README.md +1116 -1103
  8. {abstractintegratedmodule-0.3.0 → abstractintegratedmodule-0.3.2}/setup.py +2 -2
  9. abstractintegratedmodule-0.3.0/AbstractIntegratedModule.cp313-win_amd64.pyd +0 -0
  10. {abstractintegratedmodule-0.3.0 → abstractintegratedmodule-0.3.2}/AbstractIntegratedModule.egg-info/SOURCES.txt +0 -0
  11. {abstractintegratedmodule-0.3.0 → abstractintegratedmodule-0.3.2}/AbstractIntegratedModule.egg-info/dependency_links.txt +0 -0
  12. {abstractintegratedmodule-0.3.0 → abstractintegratedmodule-0.3.2}/AbstractIntegratedModule.egg-info/requires.txt +0 -0
  13. {abstractintegratedmodule-0.3.0 → abstractintegratedmodule-0.3.2}/AbstractIntegratedModule.egg-info/top_level.txt +0 -0
  14. {abstractintegratedmodule-0.3.0 → abstractintegratedmodule-0.3.2}/MANIFEST.in +0 -0
  15. {abstractintegratedmodule-0.3.0 → abstractintegratedmodule-0.3.2}/pyproject.toml +0 -0
  16. {abstractintegratedmodule-0.3.0 → abstractintegratedmodule-0.3.2}/setup.cfg +0 -0
@@ -1,7 +1,7 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: AbstractIntegratedModule
3
- Version: 0.3.0
4
- Summary: Framework forAdvanced Integrated Non-LLM AI Module library - Backend Framework for Non-LLM AI Agent Framework
3
+ Version: 0.3.2
4
+ Summary: Framework for Advanced Integrated Non-LLM AI Module library - Backend Framework for Non-LLM AI Agent Framework
5
5
  Author: Micro-Novelty
6
6
  Author-email: hernikpuspita5@gmail.com
7
7
  License: MIT
@@ -32,7 +32,9 @@ Dynamic: summary
32
32
 
33
33
  # [=] IntegratedPipeline-Specialized-AI-Agent-library
34
34
 
35
- [~] IntegratedPipeline is a standalone Specialized AI Agent Library for Non-LLL memory Augmented Agentic Framework orchestrator, Specifically designed to provide Agentic capability for any Autonomous Agentic Framework locally and Coordinatively that runs efficiently from consumer based machine to High-end embedded systems, where the AI Can directly and continously learn, with minimal and efficient compute, built-in augmented memory, Secure Peer-To-Peer (Multi-Agent) Coordination with security layers as an option, And Explainability capability based on proof from in it's internal metrics, reducing Black-Box condition necessary for reliability. Containing specialized MLP using Its Own specialized geometric Weight shaping (AWE) and Specialized efficient Transformer for Scarce Data with Alpha-based computation, specifically designed for low-amount samples environment, or Messy environments.
35
+ [~] Introduction:
36
+ - IntegratedPipeline is a standalone Specialized AI Agent Library for Non-LLL memory - Augmented Agentic Framework orchestrator, Specifically designed to provide Agentic capability for any Autonomous Agentic Framework locally and Coordinatively that runs efficiently from consumer based machine to High-end embedded systems, where the AI Can directly and continously learn, with minimal and efficient compute, built-in augmented memory, Secure Peer-To-Peer (Multi-Agent) Coordination with security layers as an option, And Explainability capability based on proof from in it's internal metrics, reducing Black-Box condition necessary for reliability.
37
+ - AbstractIntegratedModule Contains specialized MLP using Its Own specialized geometric Weight shaping (AWE), Specialized efficient Transformer and LSTM (Long-short term memory) architecture for Scarce Data with Alpha-based computation, specifically designed for low-amount samples environment, or Messy environments.
36
38
 
37
39
  #### Github Repo (if you want to know or contribute)
38
40
  https://github.com/Micro-Novelty/IntegratedPipeline-Specialized-Non-LLM-AI-Agent-Framework
@@ -40,7 +42,7 @@ https://github.com/Micro-Novelty/IntegratedPipeline-Specialized-Non-LLM-AI-Agent
40
42
  #### Note: The README here you are reading is a direct copy from my README Repository, to download the necessary files, you can visit my Repository with the provided link above.
41
43
 
42
44
  ### Library Short Description:
43
- - Development Stage: Beta, 0.2.5.
45
+ - Development Stage: Beta, 0.3.2.
44
46
  - Maintainer: Micro-Novelty.
45
47
  - library Source-Code is Open-sourced on github.
46
48
  - Purpose: Specifically Designed for providing Non-LLM AI Agent Framework for edge Devices, Optimized for ARM64 architecture.
@@ -56,18 +58,37 @@ https://github.com/Micro-Novelty/IntegratedPipeline-Specialized-Non-LLM-AI-Agent
56
58
  - win_amd64 windows 64-bit architecture: only supports python version 3.13.
57
59
  if you don't have the necessary python, don't worry since you could use our regular pip download.
58
60
 
59
- - Proven Capabilities: Works on ARM64 Environment, Training and Prediction works efficient on Docker ARM64 environment with QEMU, good parallelizing behavior is guaranteed.
61
+ - Proven Capabilities:
62
+ - Proven Works on ARM64 Environment, Training and Prediction works efficient on Docker ARM64 environment with QEMU, good parallelizing behavior is guaranteed.
63
+ - P2P Works efficiently in ARM64 Docker + QEMU, No conflicting socket and all prediction works efficiently.
64
+ - AWE setup Proven Efficient on Hard-uncontrolled dataset such as Activity Recognition from the given Database.
65
+
60
66
  -----
61
67
 
62
68
  <img width="1280" height="600" alt="WhatsApp Image 2026-05-27 at 07 16 32" src="https://github.com/user-attachments/assets/4b58a556-45a3-419b-96fd-9c1b76cac574" />
63
69
 
64
70
 
65
71
  ## [+] MANN Intro
66
- [=] Memory augmented Neural network (MANN) is a neural network architecture coupled with an external, dynamic memory module, allowing it to store, retrieve, and update information similarly to a computer's RAM. Unlike traditional networks that store knowledge only in weight parameters, MANNs excel at fast learning, long-term dependency handling, and episodic recall, In IntegratedPipeline, Its memory is stored in a custom database inside your local machine, then later used for memory retrieval, transfered to the AI Dictionary where it can finnaly recall its memory when input condition matched with memory.
72
+ [=] Memory augmented Neural network (MANN) is a neural network architecture coupled with an external, dynamic memory module, allowing it to store, retrieve, and update information similarly to a computer's RAM. Unlike traditional networks that store knowledge only in weight parameters, MANNs excel at fast learning, long-term dependency handling, and episodic recall, In IntegratedPipeline, Its memory is stored in a custom database inside your local machine, then later used for memory retrieval, transfered to the AI Dictionary where it can finnaly recall its memory when input condition matched with memory.
67
73
 
68
74
  ## [+] Abstract Weight Encoder (AWE) Intro
69
75
  [=] AWE is a specialized custom weight shaping or encoding method Specifically designed for MLP Architecture, using eigenvalue and spectral methods as base equations to calculate covariance inside a given input data, and shape the correct Weight from the given eigenvalue, AWE Works by processing input and then captures the necessary eigenvalue to shape a properly initialized Weight that aligns with input data complexity, With this approach, MLP training will be much more consistent and robust against noise.
70
76
 
77
+ ## [+] LSTM And Transformer Intro:
78
+ A. LSTMs (Long Short-Term Memory) and Transformers are foundational deep learning architectures built to process sequential data (like text or time series). While both handle the flow of time and context, they do so using completely different mechanisms.
79
+ - LSTM (Long Short-Term Memory):
80
+ - LSTMs are an advanced class of Recurrent Neural Networks (RNNs) introduced to solve the problem of traditional RNNs forgetting earlier data.
81
+ - How it works: LSTMs process data sequentially—one word or time-step at a time. They regulate information using "gates" (forget, input, and output) that determine what information from the sequence to keep or discard.
82
+ - Use Cases: Ideal for tasks with strictly continuous chronological data like time-series forecasting (e.g., stock market or weather prediction) or speech recognition.
83
+ - Limitations: Because they process data in a strict chain, it is difficult to parallelize training, making them slow and prone to forgetting long contexts.
84
+
85
+ B. Transformer:
86
+ Transformers are the modern standard for AI, introduced in 2017 with the famous "Attention Is All You Need" paper.
87
+ - How it works: Instead of reading sequences linearly, Transformers read the entire sequence all at once. They utilize a self-attention mechanism, which calculates how much "attention" or weight every part of the sequence should give to every other part, understanding the global context instantly.
88
+ - Use Cases: The backbone of Large Language Models (LLMs) like ChatGPT or BERT, making them perfect for machine translation, text generation, and summarization.
89
+ - Limitations: Transformers require massive amounts of training data and computing power to work effectively.
90
+
91
+
71
92
  [~] For a much In-Depth Explanation You can visit This repository to learn more about AWE and its performance results:
72
93
  - Link: https://github.com/Micro-Novelty/Specialized-MLP-for-noise-robustness
73
94
 
@@ -81,12 +102,14 @@ https://github.com/Micro-Novelty/IntegratedPipeline-Specialized-Non-LLM-AI-Agent
81
102
  2. Continously Learning behavior for an Agent:
82
103
  - different from LLM that is static and cannot improve beyond its given training condition, AI Agent using IntegratedPipeline has a dynamic, flexible continously learning behavior with conditional training algorithms included in the library that has both supervised and unsupervised learning present, The learned input and predicted Output will be stored in the database, allowing it to recall its memory during processing and find matching known prediction given if input matched with the stored input inside the database. this Continous learning behavior is efficient because its not relying on weights for memory, allowing flexible and predictable behavior inside a given environment.
83
104
 
84
- 3. Robust Specialized MLP and Transformer Architecture with ensemble weighting:
85
- - IntegratedPipeline has 2 Different type's of AI Architecture stacked together, and one architecture to weight their confidence and probability fairly to get the final prediction, Specialized MLP for Noise robustness And Specialized Transformer that used Alpha-based Computing algorithm for contextual reasoning, The reason why those Models complement and used together :
105
+ 3. Robust Specialized MLP, Transformer and LSTM Architecture with ensemble weighting architecture:
106
+ - IntegratedPipeline has 2 Different type's of AI Architecture stacked together, and one architecture to weight their confidence and probability fairly to get the final prediction, Specialized MLP for Noise robustness And Specialized Transformer that used Alpha-based Computing algorithm for contextual reasoning, LSTM architecture to provides proof-of-credibility over a certain output, acting as a support mechanism rather than Main orchestrator like MLP and Transformer. The reason why those Models complement and used together:
86
107
  - Specialized MLP Provides synchronous robust classification Against noise with its specialized Weight Encoder (AWE) to handle noise using eigenvalue based computing that is lightweight and efficient. This Method can't be replicated Inside Transformer FFN (Feed-forward-network) because of Transformer dynamic brute force computing where AWE-Based generated weight's get diluted over time by Transformer dynamic projection embedding, making AWE Generated weight causes inefficient inside Transformer dynamic FFN/QKV projection.
87
108
  - Specialized Transformer provides robust synchronous advanced contextual relationships, efficient data processing using Alpha based computing, The Transformer is tuned towards to be as flexible as possible to provide dynamic projection or fixed FFN projection training with minimal head's and dimension's to reduce computational power.
109
+ - LSTM doesn't act as a Main orchestrator, instead it Provides coherent Short-term memory for the Ensemble architecture, acting as a support mechanism to provides proof-of-credibility of a given answer from past previous context input, this allows flexible and achievable Aggreement between Transformer and MLP over a short period of time.
88
110
  - Ensemble weighting provides the model a much more robust classification best from both worlds perspective, weighting both MLP and Transformer confidence and probability, combined with Attention quality from the transformer to get the final prediction of an input if transformer is allowed and permitted to be in use.
89
111
 
112
+
90
113
  4. flexible and secure Peer-to-Peer Coordination (Multi-Agent):
91
114
  - IntegratedPipeline offers Peer to Peer communication capabilities asynchronously, Where IntegratedPipeline directly checks for other Peer presence directly to the local database present in the local computer or system (Synchronous prediction from peer previous data in the database), or externally, by using asynchronous request for initiating prediction, P2P is secured Using:
92
115
  - secure socket using user provided SSL CERT. on both client and server,
@@ -115,7 +138,8 @@ https://github.com/Micro-Novelty/IntegratedPipeline-Specialized-Non-LLM-AI-Agent
115
138
  [3.] Non-Representative data (Undersampled) : IntegratedPipeline Support's ambiguous data that come's from file with format such as CSV Format to extract title's and label's necessary to create automatic Dataset for Later use in Training, making it optimized for specific task's and easier dataset creation with lower overfitting rate for reliability.
116
139
 
117
140
  [=] Architectural-Overview
118
- <img width="1600" height="860" alt="WhatsApp Image 2026-05-09 at 16 13 41" src="https://github.com/user-attachments/assets/580722aa-bbd8-4148-a425-4bff01c06c47" />
141
+ <img width="1280" height="600" alt="WhatsApp Image 2026-05-27 at 07 16 32" src="https://github.com/user-attachments/assets/4b58a556-45a3-419b-96fd-9c1b76cac574" />
142
+ ---
119
143
  [=] Contextual meaning:
120
144
  1. - Sequence encoding is a machine learning technique that transforms a sequential input (like text, time-series data, or audio) into a compact, fixed-length numerical vector, often called a context vector
121
145
  2. - TF-IDF (Term Frequency-Inverse Document Frequency) is a numerical statistic used in machine learning and NLP to evaluate how important a word is to a document within a collection (corpus). It boosts rare words and penalizes common words (like "the", "and") by multiplying two metrics: how often a word appears in a document (TF) and the inverse frequency of the word across all documents (IDF).
@@ -313,7 +337,7 @@ A. [=] Computational performance results with Transformer included during Advanc
313
337
  - Repeated 269 MiB suggests allocator settled, ndarray pools stabilized, workload reached steady state
314
338
  - gradual, safe and steady batch accumulation, reduced possibility of leak explosion.
315
339
 
316
- B. [=] Advanced Prediction without Transformer, Only Specialized MLP using AWE.
340
+ B. [=] Advanced Prediction without Transformer, Only Specialized MLP + LSTM using AWE.
317
341
  ```txt
318
342
  == TIME == | CPU % | RAM \ RAM LIMIT |
319
343
  10:01:37.456 100.44% 269.8MiB / 3.71GiB # initial round 1 training started
@@ -495,11 +519,13 @@ B. [=] Advanced Prediction without Transformer, Only Specialized MLP using AWE.
495
519
  import numpy as np
496
520
 
497
521
  memory_name = 'agent_memory'
522
+ cert_file = <your_cert_file_dir> # your .crt file
523
+ key_file = <your_key_file_dir> # your .key file
524
+
498
525
  main_model = IntegratedPipeline(
499
526
  memory_name=memory_name, # memory name for the AI you already initialized
500
527
  use_async=True, # local asynchronous prediction is permitted, if not PipelineAsyncManager wont start asynchronous prediction.
501
528
  agent_port=5001, # this port is used to set AgentDistributedInference server (optional)
502
- singleton_permitted=False, # set IntegratedPipeline to singleton if you don't use it for P2P, False if you use P2P.
503
529
  ssl_cert_file=cert_file, ssl_key_file=key_file) # provide your cert_file path or key_file path (optional)
504
530
 
505
531
  main_prediction = PipelinePredictionManager(
@@ -653,6 +679,12 @@ import traceback
653
679
 
654
680
  prediction_manager = PipelinePredictionManager(main_model, label_csv=<your_training_labels.txt>, target_title=<target_title>, label=<target_label>)
655
681
 
682
+ secondary_model = IntegratedPipeline(memory_name=memory_name,
683
+ use_async=True, agent_port=8080,
684
+ ssl_cert_file=cert_file, ssl_key_file=key_file) # provide cert_file path or key_file path (optional)
685
+ # secondary model of integrated pipeline is critical for ARM64 environment to prevent socket conflict during P2P with the first Integrated pipeline instance.
686
+ # make sure that the agent_port in secondary_model must be different from agent_port in first IntegratedPipeline instance you initialized.
687
+
656
688
  print("=== SECURE PEER-TO-PEER CLUSTER ===")
657
689
 
658
690
  # CohesiveAgentDeployment is deeply tied and coupled with AgentDistributedInference,
@@ -660,6 +692,7 @@ print("=== SECURE PEER-TO-PEER CLUSTER ===")
660
692
  # allowing secure socket to be used directly by CohesiveAgentDeployment
661
693
 
662
694
  main_model.distribution.enable_ssl = False # set to false if you dont have SSL key and CERT, this code would instruct AgentDistributedInference that you don't have SSL, and provide you a regular unsecured socket (Not necessary for production)
695
+ secondary_model.distribution.enable_ssl = False
663
696
 
664
697
  # Agent 1 - Primary (Port 5555)
665
698
  agent1 = CohesiveAgentDeployment(
@@ -681,7 +714,7 @@ agent1 = CohesiveAgentDeployment(
681
714
 
682
715
  # Agent 2 - Secondary (Port 5556)
683
716
  agent2 = CohesiveAgentDeployment(
684
- pipeline=main_model,
717
+ pipeline=secondary_model,
685
718
  memory_name="agent_secondary",
686
719
  filename=<filename>,
687
720
  target_title=<title_name>,
@@ -705,11 +738,12 @@ agent2 = CohesiveAgentDeployment(
705
738
  # you must put "known_peers" in the config so python can identify the list of IPs and Ports
706
739
  # "known_peers": [
707
740
  # ["127.0.0.1", 5555], can be modified using real IP or local IP.
708
- # ["127.0.0.1", 5556]
741
+ # ["127.0.0.1", 5556],
742
+ # more ip and port lists...
709
743
  # ]
710
744
  # }
711
745
 
712
-
746
+
713
747
  try:
714
748
  # Start both agents
715
749
  print("\n🚀 Starting Agent 1...")
@@ -731,7 +765,9 @@ try:
731
765
 
732
766
  # texts dictionary must contain test_titles, label_map, and rules that you can assign,
733
767
  # agent ID can be strings, int, or floats, recommendded to make it long for better security.
734
-
768
+ agent1.pipeline.use_transformer = False # set agent1 pipeline to not use transformer for efficient processing in ARM64 env.
769
+ agent2.pipeline.use_transformer = False
770
+
735
771
  # Make prediction with peer ensemble
736
772
  # Connection will be guaranteed successfull during discovery.
737
773
  result = await agent1.multi_modal_peer_ensemble_prediction(
@@ -1007,7 +1043,7 @@ When gradients flow backward:
1007
1043
  [=] 1. - Consider checking and run: [IntegratedPipeline_Flow.html](IntegratedPipeline_Flow.html) regarding each function of the whole components and deep-dive mechanism.
1008
1044
  2. - consider checking [ARCHITECTURE.md](ARCHITECTURE.md) for more explanation about the main components.
1009
1045
 
1010
- [=] With 20 total architectures working together as a standalone library that is efficient and robust, Main components include:
1046
+ [=] With 23 total architectures working together as a standalone library that is efficient and robust, Main components include:
1011
1047
 
1012
1048
  1. GeometricWeightShaping
1013
1049
  Purpose: Analyzes the geometric structure of data (anisotropy, spectral properties, complexity) and generates optimal weight matrices based on that geometry. Essentially teaches the model how to "understand" the shape of data before processing it, Highly robust to noise, making it an excellent fit for messy environment.
@@ -1068,12 +1104,21 @@ purpose: Handles both synchronous prediction, and P2P Asynchronous prediction re
1068
1104
  ---
1069
1105
  20. ConsecutivePeerAgent
1070
1106
  purpose: handles ensemble weighting from received output from peer, managed server and acts as a listener simultaneously.
1071
-
1107
+ ---
1108
+ 21. LSTMCell
1109
+ purpose: handles LSTM Core equations In Numpy.
1110
+ ---
1111
+ 22. LSTMNetwork
1112
+ purpose: handling LSTM Feed-forward layer, Training and Samples handling.
1113
+ ---
1114
+ 23. LSTMEngine
1115
+ purpose: handles Proper LSTM Confidence and calibration layer.
1072
1116
 
1073
1117
  ## Full Documentation Features
1074
1118
  - [Go to IntegratedPipeline-Specialized-AI-Agent-library](#IntegratedPipeline-Specialized-AI-Agent-library)
1075
1119
  - [Go to MANN Intro](#MANN-Intro)
1076
1120
  - [Go to Abstract Weight Encoder (AWE) Intro](#Abstract-Weight-Encoder-(AWE)-Intro)
1121
+ - [Go to LSTM And Transformer Into](#-lstm-and-transformer-intro)
1077
1122
  - [Go to Why IntegratedPipeline?](#Why-IntegratedPipeline?)
1078
1123
  - [Go to Requirements](#Requirements)
1079
1124
  - [Go to System-Specific-Notes](#System-Specific-Notes)