---
title: Proofs we already have
---

# Proofs we already have

> _Several Nexus design elements already exist in working or audited form._

## Aletheia proves

- Native Gemini through the LiteLLM gateway root is a working path in the reviewed implementation.
- A hard `asyncio.wait_for(...)` bound around `agent.arun(...)` is necessary.
- Structured output works as a first-class runtime pattern.
- Trusted source URLs should be computed in code from stable source paths.

## openc-xfleet proves

- YAML frontmatter plus Markdown body can define agents cleanly.
- Fleet-style comparison against one typed output shape is practical.
- Deny hooks in the reviewed implementation inspect every string argument field.
- Shell tools should be disabled by default and explicitly allowlisted.

## The auth and architecture docs prove

- N1 already has a real auth direction: Oathkeeper, Hydra, Kratos, and a `Principal` plus `Policy` posture in `api-backend`.
- Nexus documentation uses that existing auth direction.

## The tech-debt audit proves

- The current CHR and pipeline path has real seams around PHI telemetry, status safety, runtime state, retry visibility, and credential handling.
- Nexus runtime and trust-rail documents address those seams.

## The AG-UI showcase proves

- The local showcase at `/home/arun/n1-agui-showcase/` proves that a backend can expose live AG-UI interfaces over SSE.
- Backend code can stream typed custom events that the browser maps to widgets.
- One frontend can render vitals panels, biomarker charts, clinical record panels, eval verdicts, traces, and generated layouts from event names.
- The browser should own rendering; the backend should emit typed payloads.

## The current AG-UI docs prove

- `https://docs.ag-ui.com/concepts/events` defines AG-UI as an event protocol, not a runtime architecture.
- `https://docs.ag-ui.com/concepts/serialization` defines official stream serialization, reconnect, branching, and compaction concepts.
- `https://docs.ag-ui.com/sdk/js/core/events` defines current `REASONING_*` events and deprecates older `THINKING_*` names.
- N1 durable replay metadata should live in an N1 persistence wrapper around AG-UI events, because AG-UI base events do not require N1-style `event_id` and `sequence` fields.