System Documentation

Comprehensive technical specifications, operational guidelines, and execution protocols for navigating the Nuviac Intelligence Grid.

1. Architectural Overview

The Nuviac Grid is an advanced Open Source Intelligence (OSINT) aggregator. It operates as a stateless proxy vault. It does not host or store target data natively; instead, it utilizes high-speed encrypted routing to fetch, parse, and sanitize data from third-party networks in real-time.

  • Zero-Storage Engine: Target outputs are processed in volatile memory (RAM) and immediately discarded post-delivery.
  • Header Stripping: All requests routed through the vault are scrubbed of the operator's digital signature, origin IP, and user-agent.
  • Packet Normalization: Disparate data formats (HTML, XML, raw text) from external endpoints are aggressively formatted into strictly typed JSON structures.

2. Cryptographic Security

Data in Transit

Secured via TLS 1.3 encryption. Interception between the client and the proxy vault is mathematically infeasible.

Data at Rest

Ephemeral processing. Nuviac utilizes Upstash Redis for quotas, bypassing permanent database storage for payloads.

Bot Mitigation

Layer 7 defense enforced by Cloudflare Turnstile. Cryptographic tokens are required for every execution.

3. Node Operation Protocol

Executing a successful query requires precise input formatting. Each module is uniquely calibrated to accept specific data strings. Dirty data will trigger an automatic rejection.

Reading the Action Guideline

Before querying, consult the Required Format block on the execution page. This specifies exactly what data type is expected (e.g., a 10-digit numeric array, an alphanumeric string, or a raw URL).

Obeying Strict Constraints

The Strict Constraints block lists prohibited characters. Identity nodes frequently require operators to omit country codes (e.g., +91), spaces, and hyphens.

4. System Diagnostics

If a query fails to resolve, the UI will intercept the backend response and display a standard HTTP error code. Refer to the table below for diagnostic resolution.

HTTP 400BAD_REQUEST

Invalid Module Signature. The requested node does not exist or the parameter is malformed.

HTTP 401UNAUTHORIZED

Authentication failure. Your session has expired or the active token is invalid.

HTTP 403FORBIDDEN

Access denied. The target is on the admin blocklist, or your Turnstile security token is stale.

HTTP 429TOO_MANY_REQUESTS

Rate limit breached. You have exceeded 10 requests within a rolling 60-second window.

HTTP 502BAD_GATEWAY

Target API unreachable. The external endpoint is down or returned non-JSON data.

5. Clearance Levels & Limits

Daily payload volume is strictly regulated by dynamic clearance tiers. Quotas automatically reset at 00:00 UTC via the Redis auto-cleaning tracker.

Standard

11 req/day

Lite

100 req/day

Premium X

1,000 req/day

Elite

10,000 req/day

6. Operational Security (OPSEC)

While Nuviac ensures the connection between our proxy vault and external networks is fully encrypted, your local Operational Security remains your primary responsibility.

  • Never utilize system nodes for unauthorized data extraction, harassment, or illegal intelligence gathering.
  • We highly recommend operating Nuviac through a secured VPN tunnel to mask your origin ISP from your local network traffic monitoring.
  • When you execute a search, it is temporarily cached in your device's localStorage to render your Profile history. You can manually wipe this cache via the "Clear Cache" button on your Profile to maintain zero local footprints.

Terms & Conditions / Legal Framework

Full legal framework drafting in progress. To be formally appended shortly.