DEEPGUARD
A local-first safety layer for AI applications, model runtimes, and tool calls. Adversarial input filtering, confidence-gated output, runtime failure recovery, and a hash-chained audit trail for every decision.
The broader Gradynt platform vision is a connected industrial AI environment for monitoring, diagnostics, safeguards, workflows, engineering knowledge, and operational data. DeepGuard and IntentCAD are available now. AMIMS is an active development program seeking funding for hardware procurement, testing, and certification. FUSE and FORGE remain directional.
A local-first safety layer for AI applications, model runtimes, and tool calls. Adversarial input filtering, confidence-gated output, runtime failure recovery, and a hash-chained audit trail for every decision.
A modular operating layer for connecting monitoring, diagnostics, evidence, applications, and review workflows.
A path for specialized local models, retrieval systems, and controlled AI deployments around proprietary knowledge.
Late-stage automated, non-destructive insulation resistance testing for ROV umbilicals — run on deck after every dive to build a cable health trend profile. Designed for certification.
Intent-first CAD: a versioned design contract carries the engineering constraints, assertions, and manufacturing context. Geometry is generated from the contract, measured independently, and evaluated against the stated requirements. STEP, STL, and DXF export with cryptographic evidence.
A voice-first, offline-first inventory capture app for field teams—count by talking, barcode, or NFC, then export. Establishes the foundation for CRATE, an offline inventory control system designed to integrate with the broader Gradynt ecosystem.
The Automated Matrixed Insulation Monitoring System (AMIMS) turns a periodic, reactive insulation check into a predictive maintenance signal. The hardware and software system automates non-destructive insulation resistance testing across the full conductor matrix of an ROV umbilical—on deck, after every dive. Each automated test sequence feeds a high-resolution trend profile that gives operators advance visibility into gradual degradation, before it escalates into an umbilical fault, unplanned ROV downtime, or asset loss.
AMIMS performs insulation resistance testing on umbilicals and cables only when they are out of the water, out of service, and de-energized between dives. A physical hardware interlock—not firmware or software—makes this operating boundary inherent to the system: an energized asset cannot be tested.
INFO, WATCH, ADVISORY, WARNING, and CRITICAL states convert insulation trends into graduated operational priorities. Instead of a single pass/fail snapshot, teams receive earlier, proportional warning as cable health deteriorates.
Links cable-health trends to REFLEX anomaly detection and SPARK differential diagnosis. Evidence-gated escalation and TDR trace correlation turn emerging degradation into a traceable investigation path.
A dedicated cloud portal for continuous insulation monitoring, trend visibility, and maintenance evidence—without requiring REFLEX, SPARK, or the broader Gradynt platform.
Industrial AI can draft a report, recommend an action, or call a tool in seconds. The risk is that a manipulated request, failing model, or low-confidence answer can move just as quickly. DeepGuard adds a control layer around that path. It filters adversarial input before execution, monitors the AI while it runs, and checks confidence before releasing the result. Each decision is written to a tamper-evident audit trail so teams can see what was allowed, blocked, or escalated and why.
DeepGuard evaluates an AI interaction at the points where risk enters and where consequences leave. Suspicious or policy-breaking requests can be stopped before they reach the model. During execution, failure signals can trigger a defined fallback or safe default. Before any answer or action is released, confidence rules determine whether it may proceed, needs operator review, or must be withheld.
Each safety decision records the relevant input fingerprint, outcome, confidence, policy, and time in a hash-chained ledger. Reviewers can trace how a result was handled and detect if the record has been altered.
A plausible answer is not automatically a safe answer. DeepGuard applies use-case-specific confidence thresholds, then releases, escalates, or withholds the result before it can influence an operational decision.
Safety checks run close to the application and its data. Teams can keep raw prompts, model outputs, and operating context within their own environment while retaining the records needed for review.
A CAD model can show what was drawn without proving why it is correct. IntentCAD puts dimensions, tolerances, functional constraints, materials, interfaces, construction instructions, and executable checks in one versioned design contract. That contract is the design record. IntentCAD builds the geometry, measures the finished solid independently, and checks the result against the stated requirements. It is available now for teams that need a clearer, safer path from engineering intent to manufacturing export.
IntentCAD never assumes that requested geometry came out correctly. After each build, an independent measurement layer inspects the actual solid and tests it against the contract's assertions. If a 3 mm fillet measures 2.8 mm, the result says 2.8 mm. The plan cannot grade its own work.
Each proposed edit is an atomic changeset that must validate before it can be applied. IntentCAD checks whether the new design still meets its constraints and calls out requirement drift, including relaxed tolerances and reduced wall thickness.
Measurements, assertion results, model snapshots, and exports are linked by SHA-256 hashes. A reviewer can verify which geometry was checked, which requirements passed, and whether an artifact changed after the evidence was recorded.
AI assistants can inspect the design record, propose changes, validate them, run the build pipeline, and verify the resulting evidence through a local MCP server. They work through the same controls as the engineer instead of going around them.
Platform direction is useful when it clarifies where your roadmap might connect, but the practical starting point should be a real asset, diagnostic workflow, or AI adoption problem.