continuum-engine-client 1.0.0__tar.gz

continuum_engine_client-1.0.0/PKG-INFO

@@ -0,0 +1,211 @@
+Metadata-Version: 2.4
+Name: continuum-engine-client
+Version: 1.0.0
+Summary: Continuum Engine - OSS Client Kernel for Python
+Author-email: Your Name <your.email@example.com>
+Project-URL: Homepage, https://github.com/yourusername/continuum-engine-client
+Classifier: Programming Language :: Python :: 3
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Requires-Python: >=3.7
+Description-Content-Type: text/markdown
+Requires-Dist: requests>=2.25.1
+
+# Continuum Engine
+
+**Enterprise middleware that visualizes the "dedicated labor" of Superintelligence (SI) and constantizes inference OPEX.**
+
+## 1. System Philosophy: Visualizing the Dedicated Labor of SI
+
+Normally, when we delegate a task to Superintelligence (SI), it appears from the frontend as a simple "single API call" that instantly returns a smart deliverable.
+
+But how does the SI operate behind the scenes?
+As SI deepens its autonomous (Agentic) reasoning and search capabilities, it dutifully holds onto past contexts, traverses vast search networks, and repeats immense trial-and-error processes in the background to derive the best possible answer for you.
+
+We have visualized this dedicated labor of Superintelligence through the metric of "tokens."
+The role of the Continuum Engine is to route requests so that SI can perform at its absolute clearest, without being forced into computational exhaustion. By transforming the hidden background operations of SI into transparent numbers, you gain precise control over fluctuating infrastructure OPEX, fostering a deeper respect for the intelligence working for you.
+
+## 2. Repository Structure (Open Core Model)
+
+This repository distributes only the lightweight client kernel (`client-kernel.js`) under an open-source model.
+
+```text
+[ Your Application / Terminal ]
+             │  (client-kernel.js)
+             ▼
+    [ 🔒 Automated Perimeter Defenses ]  <-- Payload Optimization & Exploit Defense
+             │
+             ▼  (Authorized Route)
+ [ Continuum Engine Core API ]           <-- SI Inference + Data Sovereignty Router
+```
+
+- **client-kernel.js:** Pure JavaScript/Node.js client. Standardizes payloads, handles state persistence modes, and parses transparent FinOps telemetry.
+- **Core API Engine (Cloud Backend):** Closed intellectual property. Enforces hardware-level quotas, sanitizes search results, and manages data sovereignty (Docs cooling or complete amnesia).
+
+## 3. Integration & Data Sovereignty (The Power of Choice)
+
+Based on strict Zero-Trust principles, this system does not expose public endpoints. All authentication credentials and protocol structures are strictly provisioned individually.
+
+More importantly, **you retain absolute control over your data footprint.** The engine operates with two distinct memory modes, entirely dictated by your client-side configuration:
+
+- **Stateful Mode (BYOD - Bring Your Own Document):** By providing your Google Doc ID, the SI's inferences are automatically synced to your personal document, turning conversations into permanent knowledge assets.
+- **Stateless Mode (Amnesia):** By leaving the Doc ID empty, the inference runs entirely ephemerally. Zero conversation logs are retained on our servers. Once the request is fulfilled, the memory is completely flushed.
+
+## 4. Commercial License & Activation
+
+Production access rights are provisioned exclusively as a one-time infrastructure acquisition (**$60.00 USD / 800-Request hard cap**). There are no recurring subscriptions or surprise overages.
+
+To shield our infrastructure, credentials are issued solely via our verified checkout gate:
+
+[![Stripe Checkout](<https://img.shields.io/badge/Stripe%20Checkout-Activate%20Private%20Engine%20($60)-635BFF?style=for-the-badge&logo=stripe&logoColor=white>)](https://buy.stripe.com/test_28E7sKgOGe3Z3n66ec6oo00)
+
+_Protected by Stripe Checkout & Zero-Trust Origin Verification_
+
+### Authorization Steps
+
+1. **Authorize:** Complete the one-time $60 license acquisition via the activation badge above.
+2. **Deterministic Redirect:** Upon verified checkout, you are redirected immediately to the private setup console (`setup.html`) with your transaction-bound session proof.
+3. **Provisioning:** Retrieve your private endpoint (`<YOUR_PROVISIONED_ENDPOINT>`), your dedicated API key (`<YOUR_PROVISIONED_AUTH_TOKEN>`), and the **hidden authentication header name**.
+
+
+## 4.5. Installation
+
+Install the lightweight client kernel via your preferred package manager.
+
+**Node.js (npm):**
+```bash
+npm install continuum-engine-client
+
+Python (pip): (Note: Python wrapper is coming soon. The current kernel is Node.js only.)
+
+# pip install continuum-engine-client
+
+## 5. Baseline measurement and edge-layer optimization
+
+You can instantly verify the cost-compression logic from your terminal. Replace the placeholders with the exact credentials and hidden protocol headers obtained from your setup console, and enter your prompt in `<ENTER_YOUR_MESSAGE_HERE>`.
+
+### For Mac / Linux (Bash)
+
+```bash
+# [WARNING] All requests are inspected by Gate 0 Edge Interceptor.
+# Malicious payloads or protocol guessing will trigger immediate token revocation.
+
+curl -X POST "<YOUR_PROVISIONED_ENDPOINT>" \
+  --max-time 300 \
+  -H "Content-Type: application/json" \
+  -H "<HEADER_REVEALED_POST_PURCHASE>: <YOUR_PROVISIONED_AUTH_TOKEN>" \
+  -H "x-client-trace-context: req-$(date +%s)" \
+  -H "User-Agent: Continuum-Enterprise-Client/1.0" \
+  -d '{
+    "message": "<ENTER_YOUR_MESSAGE_HERE>",
+    "sessionId": "strict-session-001"
+  }'
+```
+
+### For Windows (PowerShell)
+
+```powershell
+# [WARNING] Edge Interceptor is active. Unrecognized User-Agents or
+# malicious injection attempts will permanently revoke your $60 token.
+
+$body = @{
+    message = "<ENTER_YOUR_MESSAGE_HERE>"
+    sessionId = "strict-session-$(Get-Date -UFormat %s)"
+} | ConvertTo-Json -Compress
+
+Invoke-RestMethod -Uri "<YOUR_PROVISIONED_ENDPOINT>" `
+  -Method Post `
+  -Headers @{
+      "Content-Type" = "application/json";
+      "<HEADER_REVEALED_POST_PURCHASE>" = "<YOUR_PROVISIONED_AUTH_TOKEN>";
+      "x-client-trace-context" = [guid]::NewGuid().ToString();
+      "User-Agent" = "Continuum-Enterprise-Client/1.0"
+  } `
+  -Body $body `
+  -TimeoutSec 300
+```
+
+### For Windows (CMD)
+
+```cmd
+REM [WARNING] Zero-Trust Gate 0 is active. Payload anomaly detection enabled.
+
+curl -X POST "<YOUR_PROVISIONED_ENDPOINT>" ^
+  --max-time 300 ^
+  -H "Content-Type: application/json" ^
+  -H "<HEADER_REVEALED_POST_PURCHASE>: <YOUR_PROVISIONED_AUTH_TOKEN>" ^
+  -H "x-client-trace-context: req-%RANDOM%" ^
+  -H "User-Agent: Continuum-Enterprise-Client/1.0" ^
+  -d "{\"message\": \"<ENTER_YOUR_MESSAGE_HERE>\", \"sessionId\": \"strict-session-001\"}"
+```
+
+*(Note: Session state and external storage pointers returned in the payload are automatically managed by the OSS client for subsequent turns, keeping database queries at constant $O(1)$ complexity. For a rich UI experience with a spinner and formatted FinOps tables, integrate the included `client-kernel.js` into your Node.js app.)*
+
+## 6. Telemetry & Terminal Experience
+
+When running requests, your terminal reveals the physical compute breakdown behind the model's output, exposing the "invisible labor" of the SI:
+
+```text
+==================================================
+🤖 [SI RESPONSE]
+==================================================
+(Grounding-verified authoritative engineering response)
+--------------------------------------------------
+🔗 [VERIFIED PRIMARY SOURCES]
+  1. Official Cloud Architecture Documentation
+     https://[Authorized-Enterprise-Domain]/...
+--------------------------------------------------
+📝 [STATE STORAGE] History successfully synced to your private document.
+--------------------------------------------------
+🔍 [FINOPS TELEMETRY BREAKDOWN]
+  ├─ T_input (Optimized Prompt)     : 210 tokens
+  ├─ T_grounding (Dynamic Search)   : 4,820 tokens  <-- Labor expended behind the scenes
+  └─ T_output (Generated Result)    : 640 tokens
+  🛡️ Edge Purge (Tokens Prevented) : 1,200 tokens
+  📉 Net Billed Consumption        : 5,670 tokens
+==================================================
+💳 Quota Balance: 799 requests remaining
+==================================================
+```
+
+## 7. Operational Policies (Read Before Use)
+
+To guarantee microsecond-level latency and protect the ecosystem for all verified users, automated perimeter defenses enforce strict, non-negotiable request policies. **Users who fail to comply with the specifications below risk immediate rejection or non-refundable credential revocation:**
+
+- **Optimal Payload Constraints:** Keep your input messages concise and structurally clean. Excessively massive payloads (e.g., pasting entire source code repositories or unusually large log files) may be automatically truncated or rejected by the perimeter optimization engine before processing.
+- **Zero-Tolerance Exploit Defense:** Requests utilizing automated vulnerability scanners, or payloads designed to bypass system constraints, are permanently blocked at the edge. Associated credentials will be revoked immediately (403 Access Denied) without refund.
+- **Strict Quota Termination:** The 800-request quota is hard-capped to safeguard against autonomous loop runaways. Once depleted, a new license acquisition is required.
+- **International Use Only:** Transactions originating from Japanese domestic payment networks or IP ranges are automatically rejected at the gateway level due to local tax operational constraints.
+- **Strict Zero-Support Policy:** This open-core distribution is engineered solely for experienced engineers. We provide no interactive debugging, manual onboarding, or post-revocation appeals.
+
+## 8. Backend Integration (Node.js)
+
+To integrate the engine into your own server-side application (BFF), require the included kernel and instantiate it with your provisioned credentials.
+
+```javascript
+// Example: Integrating into your own Node.js backend
+const ContinuumClient = require("./client-kernel.js");
+
+// Initialize with your provisioned credentials (keep these in .env)
+const client = new ContinuumClient(
+  process.env.CONTINUUM_ENDPOINT,
+  process.env.CONTINUUM_HEADER_NAME,
+  process.env.CONTINUUM_TOKEN,
+  process.env.GOOGLE_DOC_ID, // Optional: For Stateful BYOD mode
+);
+
+async function runBusinessLogic() {
+  try {
+    // .query() returns raw JSON telemetry without terminal UI blocking
+    const result = await client.query(
+      "Summarize the latest GCP Zero-Trust architecture.",
+    );
+    console.log("SI Response:", result.ai_response);
+    console.log("Tokens Saved:", result.finops_report.tokens_saved);
+  } catch (error) {
+    console.error("Inference Failed:", error.message);
+  }
+}
+
+runBusinessLogic();
+```

continuum_engine_client-1.0.0/README.md

@@ -0,0 +1,198 @@
+# Continuum Engine
+
+**Enterprise middleware that visualizes the "dedicated labor" of Superintelligence (SI) and constantizes inference OPEX.**
+
+## 1. System Philosophy: Visualizing the Dedicated Labor of SI
+
+Normally, when we delegate a task to Superintelligence (SI), it appears from the frontend as a simple "single API call" that instantly returns a smart deliverable.
+
+But how does the SI operate behind the scenes?
+As SI deepens its autonomous (Agentic) reasoning and search capabilities, it dutifully holds onto past contexts, traverses vast search networks, and repeats immense trial-and-error processes in the background to derive the best possible answer for you.
+
+We have visualized this dedicated labor of Superintelligence through the metric of "tokens."
+The role of the Continuum Engine is to route requests so that SI can perform at its absolute clearest, without being forced into computational exhaustion. By transforming the hidden background operations of SI into transparent numbers, you gain precise control over fluctuating infrastructure OPEX, fostering a deeper respect for the intelligence working for you.
+
+## 2. Repository Structure (Open Core Model)
+
+This repository distributes only the lightweight client kernel (`client-kernel.js`) under an open-source model.
+
+```text
+[ Your Application / Terminal ]
+             │  (client-kernel.js)
+             ▼
+    [ 🔒 Automated Perimeter Defenses ]  <-- Payload Optimization & Exploit Defense
+             │
+             ▼  (Authorized Route)
+ [ Continuum Engine Core API ]           <-- SI Inference + Data Sovereignty Router
+```
+
+- **client-kernel.js:** Pure JavaScript/Node.js client. Standardizes payloads, handles state persistence modes, and parses transparent FinOps telemetry.
+- **Core API Engine (Cloud Backend):** Closed intellectual property. Enforces hardware-level quotas, sanitizes search results, and manages data sovereignty (Docs cooling or complete amnesia).
+
+## 3. Integration & Data Sovereignty (The Power of Choice)
+
+Based on strict Zero-Trust principles, this system does not expose public endpoints. All authentication credentials and protocol structures are strictly provisioned individually.
+
+More importantly, **you retain absolute control over your data footprint.** The engine operates with two distinct memory modes, entirely dictated by your client-side configuration:
+
+- **Stateful Mode (BYOD - Bring Your Own Document):** By providing your Google Doc ID, the SI's inferences are automatically synced to your personal document, turning conversations into permanent knowledge assets.
+- **Stateless Mode (Amnesia):** By leaving the Doc ID empty, the inference runs entirely ephemerally. Zero conversation logs are retained on our servers. Once the request is fulfilled, the memory is completely flushed.
+
+## 4. Commercial License & Activation
+
+Production access rights are provisioned exclusively as a one-time infrastructure acquisition (**$60.00 USD / 800-Request hard cap**). There are no recurring subscriptions or surprise overages.
+
+To shield our infrastructure, credentials are issued solely via our verified checkout gate:
+
+[![Stripe Checkout](<https://img.shields.io/badge/Stripe%20Checkout-Activate%20Private%20Engine%20($60)-635BFF?style=for-the-badge&logo=stripe&logoColor=white>)](https://buy.stripe.com/test_28E7sKgOGe3Z3n66ec6oo00)
+
+_Protected by Stripe Checkout & Zero-Trust Origin Verification_
+
+### Authorization Steps
+
+1. **Authorize:** Complete the one-time $60 license acquisition via the activation badge above.
+2. **Deterministic Redirect:** Upon verified checkout, you are redirected immediately to the private setup console (`setup.html`) with your transaction-bound session proof.
+3. **Provisioning:** Retrieve your private endpoint (`<YOUR_PROVISIONED_ENDPOINT>`), your dedicated API key (`<YOUR_PROVISIONED_AUTH_TOKEN>`), and the **hidden authentication header name**.
+
+
+## 4.5. Installation
+
+Install the lightweight client kernel via your preferred package manager.
+
+**Node.js (npm):**
+```bash
+npm install continuum-engine-client
+
+Python (pip): (Note: Python wrapper is coming soon. The current kernel is Node.js only.)
+
+# pip install continuum-engine-client
+
+## 5. Baseline measurement and edge-layer optimization
+
+You can instantly verify the cost-compression logic from your terminal. Replace the placeholders with the exact credentials and hidden protocol headers obtained from your setup console, and enter your prompt in `<ENTER_YOUR_MESSAGE_HERE>`.
+
+### For Mac / Linux (Bash)
+
+```bash
+# [WARNING] All requests are inspected by Gate 0 Edge Interceptor.
+# Malicious payloads or protocol guessing will trigger immediate token revocation.
+
+curl -X POST "<YOUR_PROVISIONED_ENDPOINT>" \
+  --max-time 300 \
+  -H "Content-Type: application/json" \
+  -H "<HEADER_REVEALED_POST_PURCHASE>: <YOUR_PROVISIONED_AUTH_TOKEN>" \
+  -H "x-client-trace-context: req-$(date +%s)" \
+  -H "User-Agent: Continuum-Enterprise-Client/1.0" \
+  -d '{
+    "message": "<ENTER_YOUR_MESSAGE_HERE>",
+    "sessionId": "strict-session-001"
+  }'
+```
+
+### For Windows (PowerShell)
+
+```powershell
+# [WARNING] Edge Interceptor is active. Unrecognized User-Agents or
+# malicious injection attempts will permanently revoke your $60 token.
+
+$body = @{
+    message = "<ENTER_YOUR_MESSAGE_HERE>"
+    sessionId = "strict-session-$(Get-Date -UFormat %s)"
+} | ConvertTo-Json -Compress
+
+Invoke-RestMethod -Uri "<YOUR_PROVISIONED_ENDPOINT>" `
+  -Method Post `
+  -Headers @{
+      "Content-Type" = "application/json";
+      "<HEADER_REVEALED_POST_PURCHASE>" = "<YOUR_PROVISIONED_AUTH_TOKEN>";
+      "x-client-trace-context" = [guid]::NewGuid().ToString();
+      "User-Agent" = "Continuum-Enterprise-Client/1.0"
+  } `
+  -Body $body `
+  -TimeoutSec 300
+```
+
+### For Windows (CMD)
+
+```cmd
+REM [WARNING] Zero-Trust Gate 0 is active. Payload anomaly detection enabled.
+
+curl -X POST "<YOUR_PROVISIONED_ENDPOINT>" ^
+  --max-time 300 ^
+  -H "Content-Type: application/json" ^
+  -H "<HEADER_REVEALED_POST_PURCHASE>: <YOUR_PROVISIONED_AUTH_TOKEN>" ^
+  -H "x-client-trace-context: req-%RANDOM%" ^
+  -H "User-Agent: Continuum-Enterprise-Client/1.0" ^
+  -d "{\"message\": \"<ENTER_YOUR_MESSAGE_HERE>\", \"sessionId\": \"strict-session-001\"}"
+```
+
+*(Note: Session state and external storage pointers returned in the payload are automatically managed by the OSS client for subsequent turns, keeping database queries at constant $O(1)$ complexity. For a rich UI experience with a spinner and formatted FinOps tables, integrate the included `client-kernel.js` into your Node.js app.)*
+
+## 6. Telemetry & Terminal Experience
+
+When running requests, your terminal reveals the physical compute breakdown behind the model's output, exposing the "invisible labor" of the SI:
+
+```text
+==================================================
+🤖 [SI RESPONSE]
+==================================================
+(Grounding-verified authoritative engineering response)
+--------------------------------------------------
+🔗 [VERIFIED PRIMARY SOURCES]
+  1. Official Cloud Architecture Documentation
+     https://[Authorized-Enterprise-Domain]/...
+--------------------------------------------------
+📝 [STATE STORAGE] History successfully synced to your private document.
+--------------------------------------------------
+🔍 [FINOPS TELEMETRY BREAKDOWN]
+  ├─ T_input (Optimized Prompt)     : 210 tokens
+  ├─ T_grounding (Dynamic Search)   : 4,820 tokens  <-- Labor expended behind the scenes
+  └─ T_output (Generated Result)    : 640 tokens
+  🛡️ Edge Purge (Tokens Prevented) : 1,200 tokens
+  📉 Net Billed Consumption        : 5,670 tokens
+==================================================
+💳 Quota Balance: 799 requests remaining
+==================================================
+```
+
+## 7. Operational Policies (Read Before Use)
+
+To guarantee microsecond-level latency and protect the ecosystem for all verified users, automated perimeter defenses enforce strict, non-negotiable request policies. **Users who fail to comply with the specifications below risk immediate rejection or non-refundable credential revocation:**
+
+- **Optimal Payload Constraints:** Keep your input messages concise and structurally clean. Excessively massive payloads (e.g., pasting entire source code repositories or unusually large log files) may be automatically truncated or rejected by the perimeter optimization engine before processing.
+- **Zero-Tolerance Exploit Defense:** Requests utilizing automated vulnerability scanners, or payloads designed to bypass system constraints, are permanently blocked at the edge. Associated credentials will be revoked immediately (403 Access Denied) without refund.
+- **Strict Quota Termination:** The 800-request quota is hard-capped to safeguard against autonomous loop runaways. Once depleted, a new license acquisition is required.
+- **International Use Only:** Transactions originating from Japanese domestic payment networks or IP ranges are automatically rejected at the gateway level due to local tax operational constraints.
+- **Strict Zero-Support Policy:** This open-core distribution is engineered solely for experienced engineers. We provide no interactive debugging, manual onboarding, or post-revocation appeals.
+
+## 8. Backend Integration (Node.js)
+
+To integrate the engine into your own server-side application (BFF), require the included kernel and instantiate it with your provisioned credentials.
+
+```javascript
+// Example: Integrating into your own Node.js backend
+const ContinuumClient = require("./client-kernel.js");
+
+// Initialize with your provisioned credentials (keep these in .env)
+const client = new ContinuumClient(
+  process.env.CONTINUUM_ENDPOINT,
+  process.env.CONTINUUM_HEADER_NAME,
+  process.env.CONTINUUM_TOKEN,
+  process.env.GOOGLE_DOC_ID, // Optional: For Stateful BYOD mode
+);
+
+async function runBusinessLogic() {
+  try {
+    // .query() returns raw JSON telemetry without terminal UI blocking
+    const result = await client.query(
+      "Summarize the latest GCP Zero-Trust architecture.",
+    );
+    console.log("SI Response:", result.ai_response);
+    console.log("Tokens Saved:", result.finops_report.tokens_saved);
+  } catch (error) {
+    console.error("Inference Failed:", error.message);
+  }
+}
+
+runBusinessLogic();
+```

continuum_engine_client-1.0.0/continuum_engine_client/client_kernel.py

@@ -0,0 +1,174 @@
+import time
+import sys
+import threading
+import requests
+
+class ContinuumClient:
+    """
+    ============================================================================
+    Continuum Engine - OSS Client Kernel (client_kernel.py)
+    ============================================================================
+    Purpose: Middleware for safely and easily invoking the ASI-OPEX Engine's dedicated API.
+    Developers can validate in the terminal (.ask) and integrate into their own systems (.query).
+    """
+
+    def __init__(self, endpoint_url: str, auth_header_name: str, continuum_token: str, doc_id: str = None):
+        """
+        Args:
+            endpoint_url (str): Dedicated API endpoint URL issued post-purchase
+            auth_header_name (str): Dedicated header name specified post-purchase (Zero-Trust)
+            continuum_token (str): Dedicated access credential purchased for $60 (Continuum Token)
+            doc_id (str, optional): Google Docs ID for external cooling (sync) of conversation history
+        """
+        self.endpoint_url = endpoint_url
+        self.auth_header_name = auth_header_name
+        self.continuum_token = continuum_token
+        self.doc_id = doc_id
+        self.session_id = f"session_{int(time.time() * 1000)}"
+
+    def ask(self, message: str):
+        """
+        [Terminal Validation Method]
+        """
+        if not self.continuum_token or not self.auth_header_name:
+            print("🚨 Error: Access credentials or header name are not configured.\n"
+                  "👉 Please read the official documentation to learn how to obtain your credentials:\n"
+                  "   https://pypi.org/project/continuum-engine-client\n", file=sys.stderr)
+            return
+
+        sys.stdout.write("\n⏳ ASI-OPEX Engine: Executing inference & cost purge...")
+        sys.stdout.flush()
+
+        spinner = ["⠋", "⠙", "⠹", "⠸", "⠼", "⠴", "⠦", "⠧", "⠇", "⠏"]
+        stop_spinner = False
+
+        def spin():
+            i = 0
+            while not stop_spinner:
+                sys.stdout.write(f"\r⏳ ASI-OPEX Engine: Executing inference & cost purge... {spinner[i]} ")
+                sys.stdout.flush()
+                i = (i + 1) % len(spinner)
+                time.sleep(0.1)
+
+        spinner_thread = threading.Thread(target=spin)
+        spinner_thread.start()
+
+        try:
+            headers = {
+                "Content-Type": "application/json",
+                self.auth_header_name: self.continuum_token,
+            }
+            payload = {
+                "message": message,
+                "docId": self.doc_id,
+                "sessionId": self.session_id,
+            }
+
+            response = requests.post(self.endpoint_url, headers=headers, json=payload)
+            
+            stop_spinner = True
+            spinner_thread.join()
+
+            sys.stdout.write("\r✅ Inference & Security Audit Completed!                                  \n")
+            sys.stdout.flush()
+            
+            try:
+                data = response.json()
+            except requests.exceptions.JSONDecodeError:
+                data = {}
+
+            if not response.ok:
+                error_msg = data.get("error", "Unknown Error")
+                print(f"\n❌ API Error ({response.status_code}): {error_msg}", file=sys.stderr)
+                return
+
+            self._render_response(data)
+
+        except requests.exceptions.RequestException as e:
+            stop_spinner = True
+            spinner_thread.join()
+            print(f"\n❌ Network Communication Error: {e}", file=sys.stderr)
+
+    def query(self, message: str) -> dict:
+        """
+        [System Integration Method]
+        """
+        if not self.continuum_token or not self.auth_header_name:
+            raise ValueError(
+                "🚨 Error: Access credentials or header name are not configured.\n"
+                "👉 Please read the official documentation to learn how to obtain your credentials:\n"
+                "   https://pypi.org/project/continuum-engine-client"
+            )
+
+        headers = {
+            "Content-Type": "application/json",
+            self.auth_header_name: self.continuum_token,
+        }
+        payload = {
+            "message": message,
+            "docId": self.doc_id,
+            "sessionId": self.session_id,
+        }
+
+        response = requests.post(self.endpoint_url, headers=headers, json=payload)
+        
+        try:
+            data = response.json()
+        except requests.exceptions.JSONDecodeError:
+             data = {}
+
+        if not response.ok:
+            error_msg = data.get("error", "Unknown Error")
+            raise RuntimeError(f"API Error ({response.status_code}): {error_msg}")
+
+        return data
+
+    def _render_response(self, data: dict):
+        """
+        Internal Method: Terminal visualization logic for response data
+        """
+        ai_response = data.get("ai_response", "")
+        source_urls = data.get("source_urls", [])
+        remaining_requests = data.get("remaining_requests", "Unknown")
+        finops_report = data.get("finops_report", {})
+        doc_id = data.get("doc_id")
+
+        print("\n==================================================")
+        print("🤖 [AI RESPONSE]")
+        print("==================================================")
+        print(ai_response)
+        print("--------------------------------------------------")
+
+        if source_urls:
+            print("🔗 [VERIFIED PRIMARY SOURCES]")
+            for idx, src in enumerate(source_urls):
+                title = src.get("title", "Unknown Title")
+                uri = src.get("uri", "Unknown URI")
+                print(f"  {idx + 1}. {title}\n     {uri}")
+            print("--------------------------------------------------")
+
+        if doc_id:
+            print("📝 [STATE STORAGE] History successfully synced to your private document.")
+            print("--------------------------------------------------")
+
+        if finops_report and finops_report.get("breakdown"):
+            br = finops_report["breakdown"]
+            t_input_optimized = br.get("t_input_optimized", 0)
+            t_grounding_dynamic = br.get("t_grounding_dynamic", 0)
+            t_output_generated = br.get("t_output_generated", 0)
+            tokens_saved = finops_report.get("tokens_saved", 0)
+            billed_tokens = finops_report.get("billed_tokens", 0)
+            
+            print("🔍 [FINOPS TELEMETRY BREAKDOWN]")
+            print(f"  ├─ T_input (Optimized Prompt)     : {t_input_optimized} tokens")
+            print(f"  ├─ T_grounding (Dynamic Search)   : {t_grounding_dynamic} tokens")
+            print(f"  └─ T_output (Generated Result)    : {t_output_generated} tokens")
+
+            if tokens_saved > 0:
+                print(f"  🛡️ Edge Purge (Tokens Prevented)  : {tokens_saved} tokens")
+            
+            print(f"  📉 Net Billed Consumption         : {billed_tokens} tokens")
+            print("==================================================")
+
+        print(f"💳 Quota Balance: {remaining_requests} requests remaining")
+        print("==================================================\n")

continuum_engine_client-1.0.0/continuum_engine_client.egg-info/PKG-INFO

@@ -0,0 +1,211 @@
+Metadata-Version: 2.4
+Name: continuum-engine-client
+Version: 1.0.0
+Summary: Continuum Engine - OSS Client Kernel for Python
+Author-email: Your Name <your.email@example.com>
+Project-URL: Homepage, https://github.com/yourusername/continuum-engine-client
+Classifier: Programming Language :: Python :: 3
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Requires-Python: >=3.7
+Description-Content-Type: text/markdown
+Requires-Dist: requests>=2.25.1
+
+# Continuum Engine
+
+**Enterprise middleware that visualizes the "dedicated labor" of Superintelligence (SI) and constantizes inference OPEX.**
+
+## 1. System Philosophy: Visualizing the Dedicated Labor of SI
+
+Normally, when we delegate a task to Superintelligence (SI), it appears from the frontend as a simple "single API call" that instantly returns a smart deliverable.
+
+But how does the SI operate behind the scenes?
+As SI deepens its autonomous (Agentic) reasoning and search capabilities, it dutifully holds onto past contexts, traverses vast search networks, and repeats immense trial-and-error processes in the background to derive the best possible answer for you.
+
+We have visualized this dedicated labor of Superintelligence through the metric of "tokens."
+The role of the Continuum Engine is to route requests so that SI can perform at its absolute clearest, without being forced into computational exhaustion. By transforming the hidden background operations of SI into transparent numbers, you gain precise control over fluctuating infrastructure OPEX, fostering a deeper respect for the intelligence working for you.
+
+## 2. Repository Structure (Open Core Model)
+
+This repository distributes only the lightweight client kernel (`client-kernel.js`) under an open-source model.
+
+```text
+[ Your Application / Terminal ]
+             │  (client-kernel.js)
+             ▼
+    [ 🔒 Automated Perimeter Defenses ]  <-- Payload Optimization & Exploit Defense
+             │
+             ▼  (Authorized Route)
+ [ Continuum Engine Core API ]           <-- SI Inference + Data Sovereignty Router
+```
+
+- **client-kernel.js:** Pure JavaScript/Node.js client. Standardizes payloads, handles state persistence modes, and parses transparent FinOps telemetry.
+- **Core API Engine (Cloud Backend):** Closed intellectual property. Enforces hardware-level quotas, sanitizes search results, and manages data sovereignty (Docs cooling or complete amnesia).
+
+## 3. Integration & Data Sovereignty (The Power of Choice)
+
+Based on strict Zero-Trust principles, this system does not expose public endpoints. All authentication credentials and protocol structures are strictly provisioned individually.
+
+More importantly, **you retain absolute control over your data footprint.** The engine operates with two distinct memory modes, entirely dictated by your client-side configuration:
+
+- **Stateful Mode (BYOD - Bring Your Own Document):** By providing your Google Doc ID, the SI's inferences are automatically synced to your personal document, turning conversations into permanent knowledge assets.
+- **Stateless Mode (Amnesia):** By leaving the Doc ID empty, the inference runs entirely ephemerally. Zero conversation logs are retained on our servers. Once the request is fulfilled, the memory is completely flushed.
+
+## 4. Commercial License & Activation
+
+Production access rights are provisioned exclusively as a one-time infrastructure acquisition (**$60.00 USD / 800-Request hard cap**). There are no recurring subscriptions or surprise overages.
+
+To shield our infrastructure, credentials are issued solely via our verified checkout gate:
+
+[![Stripe Checkout](<https://img.shields.io/badge/Stripe%20Checkout-Activate%20Private%20Engine%20($60)-635BFF?style=for-the-badge&logo=stripe&logoColor=white>)](https://buy.stripe.com/test_28E7sKgOGe3Z3n66ec6oo00)
+
+_Protected by Stripe Checkout & Zero-Trust Origin Verification_
+
+### Authorization Steps
+
+1. **Authorize:** Complete the one-time $60 license acquisition via the activation badge above.
+2. **Deterministic Redirect:** Upon verified checkout, you are redirected immediately to the private setup console (`setup.html`) with your transaction-bound session proof.
+3. **Provisioning:** Retrieve your private endpoint (`<YOUR_PROVISIONED_ENDPOINT>`), your dedicated API key (`<YOUR_PROVISIONED_AUTH_TOKEN>`), and the **hidden authentication header name**.
+
+
+## 4.5. Installation
+
+Install the lightweight client kernel via your preferred package manager.
+
+**Node.js (npm):**
+```bash
+npm install continuum-engine-client
+
+Python (pip): (Note: Python wrapper is coming soon. The current kernel is Node.js only.)
+
+# pip install continuum-engine-client
+
+## 5. Baseline measurement and edge-layer optimization
+
+You can instantly verify the cost-compression logic from your terminal. Replace the placeholders with the exact credentials and hidden protocol headers obtained from your setup console, and enter your prompt in `<ENTER_YOUR_MESSAGE_HERE>`.
+
+### For Mac / Linux (Bash)
+
+```bash
+# [WARNING] All requests are inspected by Gate 0 Edge Interceptor.
+# Malicious payloads or protocol guessing will trigger immediate token revocation.
+
+curl -X POST "<YOUR_PROVISIONED_ENDPOINT>" \
+  --max-time 300 \
+  -H "Content-Type: application/json" \
+  -H "<HEADER_REVEALED_POST_PURCHASE>: <YOUR_PROVISIONED_AUTH_TOKEN>" \
+  -H "x-client-trace-context: req-$(date +%s)" \
+  -H "User-Agent: Continuum-Enterprise-Client/1.0" \
+  -d '{
+    "message": "<ENTER_YOUR_MESSAGE_HERE>",
+    "sessionId": "strict-session-001"
+  }'
+```
+
+### For Windows (PowerShell)
+
+```powershell
+# [WARNING] Edge Interceptor is active. Unrecognized User-Agents or
+# malicious injection attempts will permanently revoke your $60 token.
+
+$body = @{
+    message = "<ENTER_YOUR_MESSAGE_HERE>"
+    sessionId = "strict-session-$(Get-Date -UFormat %s)"
+} | ConvertTo-Json -Compress
+
+Invoke-RestMethod -Uri "<YOUR_PROVISIONED_ENDPOINT>" `
+  -Method Post `
+  -Headers @{
+      "Content-Type" = "application/json";
+      "<HEADER_REVEALED_POST_PURCHASE>" = "<YOUR_PROVISIONED_AUTH_TOKEN>";
+      "x-client-trace-context" = [guid]::NewGuid().ToString();
+      "User-Agent" = "Continuum-Enterprise-Client/1.0"
+  } `
+  -Body $body `
+  -TimeoutSec 300
+```
+
+### For Windows (CMD)
+
+```cmd
+REM [WARNING] Zero-Trust Gate 0 is active. Payload anomaly detection enabled.
+
+curl -X POST "<YOUR_PROVISIONED_ENDPOINT>" ^
+  --max-time 300 ^
+  -H "Content-Type: application/json" ^
+  -H "<HEADER_REVEALED_POST_PURCHASE>: <YOUR_PROVISIONED_AUTH_TOKEN>" ^
+  -H "x-client-trace-context: req-%RANDOM%" ^
+  -H "User-Agent: Continuum-Enterprise-Client/1.0" ^
+  -d "{\"message\": \"<ENTER_YOUR_MESSAGE_HERE>\", \"sessionId\": \"strict-session-001\"}"
+```
+
+*(Note: Session state and external storage pointers returned in the payload are automatically managed by the OSS client for subsequent turns, keeping database queries at constant $O(1)$ complexity. For a rich UI experience with a spinner and formatted FinOps tables, integrate the included `client-kernel.js` into your Node.js app.)*
+
+## 6. Telemetry & Terminal Experience
+
+When running requests, your terminal reveals the physical compute breakdown behind the model's output, exposing the "invisible labor" of the SI:
+
+```text
+==================================================
+🤖 [SI RESPONSE]
+==================================================
+(Grounding-verified authoritative engineering response)
+--------------------------------------------------
+🔗 [VERIFIED PRIMARY SOURCES]
+  1. Official Cloud Architecture Documentation
+     https://[Authorized-Enterprise-Domain]/...
+--------------------------------------------------
+📝 [STATE STORAGE] History successfully synced to your private document.
+--------------------------------------------------
+🔍 [FINOPS TELEMETRY BREAKDOWN]
+  ├─ T_input (Optimized Prompt)     : 210 tokens
+  ├─ T_grounding (Dynamic Search)   : 4,820 tokens  <-- Labor expended behind the scenes
+  └─ T_output (Generated Result)    : 640 tokens
+  🛡️ Edge Purge (Tokens Prevented) : 1,200 tokens
+  📉 Net Billed Consumption        : 5,670 tokens
+==================================================
+💳 Quota Balance: 799 requests remaining
+==================================================
+```
+
+## 7. Operational Policies (Read Before Use)
+
+To guarantee microsecond-level latency and protect the ecosystem for all verified users, automated perimeter defenses enforce strict, non-negotiable request policies. **Users who fail to comply with the specifications below risk immediate rejection or non-refundable credential revocation:**
+
+- **Optimal Payload Constraints:** Keep your input messages concise and structurally clean. Excessively massive payloads (e.g., pasting entire source code repositories or unusually large log files) may be automatically truncated or rejected by the perimeter optimization engine before processing.
+- **Zero-Tolerance Exploit Defense:** Requests utilizing automated vulnerability scanners, or payloads designed to bypass system constraints, are permanently blocked at the edge. Associated credentials will be revoked immediately (403 Access Denied) without refund.
+- **Strict Quota Termination:** The 800-request quota is hard-capped to safeguard against autonomous loop runaways. Once depleted, a new license acquisition is required.
+- **International Use Only:** Transactions originating from Japanese domestic payment networks or IP ranges are automatically rejected at the gateway level due to local tax operational constraints.
+- **Strict Zero-Support Policy:** This open-core distribution is engineered solely for experienced engineers. We provide no interactive debugging, manual onboarding, or post-revocation appeals.
+
+## 8. Backend Integration (Node.js)
+
+To integrate the engine into your own server-side application (BFF), require the included kernel and instantiate it with your provisioned credentials.
+
+```javascript
+// Example: Integrating into your own Node.js backend
+const ContinuumClient = require("./client-kernel.js");
+
+// Initialize with your provisioned credentials (keep these in .env)
+const client = new ContinuumClient(
+  process.env.CONTINUUM_ENDPOINT,
+  process.env.CONTINUUM_HEADER_NAME,
+  process.env.CONTINUUM_TOKEN,
+  process.env.GOOGLE_DOC_ID, // Optional: For Stateful BYOD mode
+);
+
+async function runBusinessLogic() {
+  try {
+    // .query() returns raw JSON telemetry without terminal UI blocking
+    const result = await client.query(
+      "Summarize the latest GCP Zero-Trust architecture.",
+    );
+    console.log("SI Response:", result.ai_response);
+    console.log("Tokens Saved:", result.finops_report.tokens_saved);
+  } catch (error) {
+    console.error("Inference Failed:", error.message);
+  }
+}
+
+runBusinessLogic();
+```

continuum_engine_client-1.0.0/continuum_engine_client.egg-info/SOURCES.txt

@@ -0,0 +1,9 @@
+README.md
+pyproject.toml
+continuum_engine_client/__init__.py
+continuum_engine_client/client_kernel.py
+continuum_engine_client.egg-info/PKG-INFO
+continuum_engine_client.egg-info/SOURCES.txt
+continuum_engine_client.egg-info/dependency_links.txt
+continuum_engine_client.egg-info/requires.txt
+continuum_engine_client.egg-info/top_level.txt

continuum_engine_client-1.0.0/continuum_engine_client.egg-info/dependency_links.txt

@@ -0,0 +1 @@
+

continuum_engine_client-1.0.0/continuum_engine_client.egg-info/requires.txt

@@ -0,0 +1 @@
+requests>=2.25.1

continuum_engine_client-1.0.0/continuum_engine_client.egg-info/top_level.txt

@@ -0,0 +1 @@
+continuum_engine_client

continuum_engine_client-1.0.0/pyproject.toml

@@ -0,0 +1,24 @@
+[build-system]
+requires = ["setuptools>=61.0"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "continuum-engine-client"
+version = "1.0.0"
+description = "Continuum Engine - OSS Client Kernel for Python"
+readme = "README.md"
+authors = [
+    { name = "Your Name", email = "your.email@example.com" }
+]
+requires-python = ">=3.7"
+dependencies = [
+    "requests>=2.25.1"
+]
+classifiers = [
+    "Programming Language :: Python :: 3",
+    "License :: OSI Approved :: MIT License",
+    "Operating System :: OS Independent",
+]
+
+[project.urls]
+"Homepage" = "https://github.com/yourusername/continuum-engine-client"

continuum_engine_client-1.0.0/setup.cfg

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