What's new in DMZAgent.

New name, new home: DMZAgent on dmzagent.com

The platform is now DMZAgent. The marketing site, dashboard, API, and status page moved to the dmzagent.com zone; the prior staging surface on the old zone is being retired. SDK package and repository names follow the new name (pip install dmzagent, @dmzagent/sdk, and the C# and Java equivalents).

The cookie domain moved with the rebrand, so existing sessions re-authenticate once. API base URLs in the SDKs and on this site now resolve to api.dmzagent.com.

• changed · brand → DMZAgent
• changed · hosts → dmzagent.com
• added · dmzagent SDK namespaces

Human review loop: triage, hold-and-release, live streams

Coordinate-lane dispositions now open durable review objects on a first-class triage queue, separate from notifications. An operator can hold a pending action and release it after review; the decision is recorded to the ledger and feeds back into the subject's soul through the same path as automated reasoning.

Triage updates stream to the dashboard over Server-Sent Events, so a high-risk event opens a review item in real time.

• added · review queue + triage band
• added · hold / release operator flow
• added · live triage streams

Division-scoped response and cross-workspace corroboration

Response moved from per-workspace chains into a division-level disposition chain: a fired tag resolves once per division across four lanes — record, enforce, remediate, coordinate — with a single most-restrictive circuit-breaker state. Remediation directives fire exactly once even when reasoning fans out across many workspaces.

Recognition stays independent per workspace and now corroborates — the same subject is read across workspace chains to show cross-workspace agreement and response history in the analyst workbench.

• added · division disposition chain
• changed · circuit breaker is division-scoped
• added · cross-workspace corroboration

SDKs at parity: Python, TypeScript, C#, and Java

The TypeScript, C# (NuGet), and Java (Maven) SDKs reached parity with Python, all generated against a shared JSON-Schema contract with cross-language contract tests. Each ships agent-stream capture, circuit-breaker checks, retry semantics, and webhook-signature verification.

Web Push notification delivery and an hourly email-digest sweep landed alongside the SDK release.

• added · TypeScript / C# / Java SDKs
• added · shared SDK spec + contract tests
• added · Web Push delivery

Async ingest pipeline + live job status

POST /v1/connector-instances/{id}/run now returns a 202 with a queued job id; the connector → delegate → reasoning pipeline runs in a background worker. The dashboard subscribes to a per-job Server-Sent Events stream so the run-for-real chip animates from queued to running to terminal in real time.

Recent Jobs panel updates without polling. Container restarts recover orphaned jobs at boot: in-flight rows are marked failed, queued rows are re-enqueued.

• added · async pipeline
• added · SSE job stream
• changed · /run returns 202 not 200

Owner-edited rate card

Service operators can edit free allowances, per-unit rates, and volume tier breakpoints from the dashboard at /service-admin/rates. Every publish writes to the platform ledger as a controlled record, snapshots the canonical JSON to R2 (current + versioned + history), and fires the marketing-site rebuild webhook so the pricing page reflects the new schedule within minutes.

The customer billing usage page and the rate card on dmzagent.com both read from the same R2 source — a rate change can no longer drift between the live bill and the public schedule.

• added · rate card editor
• added · controlled-record ledger
• changed · pricing reads from R2 snapshot

Containerized reasoning core cutover

The reasoning core now runs as a managed container fronted by our edge-hosted Worker, replacing the prior cloud-managed deployment. One-provider stack, no cross-internet seam between the dashboard and the reasoning core, and live tail logs surfaced in the operator console for every request and every container stdout line.

• changed · infrastructure
• added · live observability

Federal design language across the product

Every product surface — analyst dashboard, marketing site, docs — was relaid on a shared federal-records visual system: white paper background, federal navy 0a2540, treasury red c8102e for hairline accents, Public Sans for body, JetBrains Mono for identifiers. The codex is the source of truth; the surfaces present it.

• changed · design language