v1.6.0: Operational Intelligence for AI Agents

Proxus 1.6.0 strengthens the context available to connected AI agents while preserving the platform's offline-first edge runtime.

Operational Graph Intelligence

• The new graph_paths MCP tool returns bounded, cycle-safe causal paths with relationship evidence and confidence.
• graph_context_pack now ranks context for the agent's stated goal instead of returning relationships in storage order.
• Runtime mismatches and pending last-known evidence receive appropriate priority without turning missing edge confirmation into a failure.
• Authenticated graph calls now reuse a bounded, security-scoped topology snapshot across different root queries instead of rebuilding the same dependency model for every call.
• Graph tools now return recoverable, classified guidance for missing or invalid arguments instead of terminating with a generic invocation error.
• Graph edge evidence is self-describing through confidence/source-kind names and stable, versioned extractor identifiers while preserving existing numeric fields.
• Every graph response includes snapshot freshness metadata. Agents can distinguish current, stale, last-complete, and temporarily unavailable context without receiving security-scope identifiers.
• Dashboard lineage now connects datasource, query, field, widget, and dashboard bindings through the dashboard object model while keeping raw SQL redacted.
• ClickHouse telemetry queries add conservative key-level or exact device-and-key series lineage. Ambiguous device scope stays key-level, and unsupported syntax never creates guessed relationships.
• Rule lineage now interprets supported criteria semantics, including telemetry keys, device scope, logical branches, and event context. Dynamic or unsupported criteria remain explicitly partial or opaque instead of creating guessed dependencies.
• Function lineage now identifies statically proven telemetry inputs and outputs, device effects, and notification dependencies from the same compiled API contracts used by the platform. Renamed or refactored APIs remain compiler-checked instead of relying on method-name matching.
• Semantic results include coverage, confidence, evidence, and freshness so agents can separate proven relationships from incomplete analysis.
• Raw rule criteria, function source code, unresolved literals, credentials, and notification secrets remain excluded from graph and MCP responses.

MCP Compatibility

• Prompt and resource-template parameters provide standards-based allowed-value completions to compatible MCP clients.
• Tool parameter choices continue to use JSON Schema enums.
• The MCP C# SDK was updated to the latest stable servicing release for transport reliability and memory-management fixes.
• MCP telemetry access is now one administrator-only, guarded read-only ClickHouse query tool, with schema-led query guidance and bounded resource controls.
• Telemetry schema discovery now provides machine-readable planning for point evidence, freshness, trends, and portfolio anomaly triage. Agents define the criterion, aggregate before raw drill-down, report scope coverage, and re-plan rather than repeat an unchanged resource-limited query.
• The authenticated device_status tool now reports live, permission-scoped device health from Hub runtime and freshness evidence. Persisted device fields, gateway connectivity, telemetry observations, and graph apply confirmation remain separate facts.
• MCP initialization now requests a tool-catalog refresh through the standard list-changed notification. Schema discovery identifies stale catalogs, and calls from clients that still retain removed telemetry tools receive a controlled recovery diagnostic instead of an unknown-tool failure.
• Anonymous MCP bootstrap now reports authentication as a blocking workflow state. Login requires both human-supplied fields, empty login calls return a controlled recovery action, and protected task routing becomes actionable only after the current protocol session is authenticated.
• MCP authorization now keeps platform permission checks and downstream entity requests on one authenticated session identity. Exact-origin controls, configurable anonymous discovery, and protocol-compliant security errors strengthen multi-user deployments.

All operational graph calls remain authenticated and read-only. Reused topology snapshots still receive current in-memory runtime evidence when a result is produced. Graph calls do not create periodic edge traffic or change device and rule runtime behavior.