Skip to content

visado: observability, UI, launch research (2026-11-18)

Observability: no OTel semconv for identity/authz exists yet. visado can reuse gen_ai.agent.*, gen_ai.tool.name and mcp.* (all Development, now in the separate semantic-conventions-genai repo), put the chain under a visado.* namespace, and track GenAI PR #291 (agent authz attributes). enduser.id was deprecated in core v1.45 and moved to the client-side repo.

Rust: opentelemetry 0.33.1 (2026-10-08). Logs and metrics are stable, traces are still beta. Pin opentelemetry* and pair it with tracing-opentelemetry 0.34.

Audit: OCSF API Activity (6003) with actor.authorizations and actor.invoked_by. CAEP 1.0/SSF 1.0 are Final (Sept 2025) and fit revocation signals. AIMS needs tamper-evident audit records. PR #176 keeps the transcription mapping for audit.

UI: a static SPA embedded in the binary, using React Flow with a left-to-right dagre/ELK layout, one hop per node, and allow/deny coloring. The target screenshot is one request with the denied hop lit up red.

Launch: agent-identity Show HNs score low (Zalando AIB 25 pts, Nov 2026). Projects that took off had a hook: a threat model (Agent Vault 156), a story (Cloudflare “Claude wrote it”), research first (mcp-scan), or a foundation donation at a conference (agentgateway). Proposed window: IETF 128 hackathon (Mar 6-7, 2027, inferred), then KubeCon EU, then AGNTCon NA.

How to emit a chain (my recommendation; not in any spec)

Section titled “How to emit a chain (my recommendation; not in any spec)”
  • AIMS (draft-ietf-wimse-aims-01, 2026-11-02): audit, delegation and authz depend on a stable WIMSE identifier, and audit records MUST be tamper-evident. https://datatracker.ietf.org/doc/draft-ietf-wimse-aims/
  • PR #176 (nik-kale) adds privacy text. Where stable IDs are not acceptable, the AS uses claims transcription (OAUTH-ID-CHAIN section 2.5) and keeps the mapping for audit. During review the text was softened to defer to deployment policy. Merge status is not visible. https://github.com/ietf-wg-wimse/draft-ietf-wimse-aims/pull/176
    • Implication: visado’s audit record should store both pre- and post-transcription subject IDs, gated by policy.
  • CAEP 1.0 / SSF 1.0 / RISC 1.0 are Final (vote Sept 2025). An interop profile is in progress. Use them as an output, for example emitting session-revoked/token-claims-change SETs when a chain is revoked. https://openid.net/three-shared-signals-final-specifications-approved/
  • OCSF:
    • API Activity (6003) is the best fit per request. actor.authorizations[] carries decision and policy, and actor.invoked_by is a natural slot for the delegator. https://schema.ocsf.io/1.3.0/objects/actor
    • Authorize Session (3003) is session-level only.
    • Open issue #1736 debates mapping agent behavior to OCSF, so there is no settled agent mapping yet. https://github.com/ocsf/ocsf-schema/issues/1736
    • Inference: put the full chain in unmapped or a profile until OCSF settles.

What makes a screenshot compelling (synthesis)

Section titled “What makes a screenshot compelling (synthesis)”
  • One request, a linear left-to-right chain, and each edge labeled with the token step (ID token, then ID-JAG/OBO, then Txn-Token) plus the scope narrowing (repo:* to repo:foo:read).
  • The deny hop highlighted red, with the AuthZEN reason inline.
  • A side panel with the decoded Txn-Token and the AuthZEN request/response.
  • A “copy as TraceQL / open in Grafana” link.
  • Serve a static SPA from the gateway, embedded with rust-embed/include_dir at /ui. It reads a JSON /api/requests/{id}/chain endpoint and an SSE live tail.
  • Use React Flow (@xyflow/react) with a dagre/ELK LR layout. Chains are small DAGs, so Cytoscape’s large-graph strengths are not needed.
  • Add a share-by-URL mode (chain JSON in the fragment, as fga-playground does) so people can paste chains into issues.
  • Add a visado explain <req-id> TUI/CLI twin, similar to Teleport’s tsh access-graph and openfga-tui.
  • Inference: a bare “agent identity gateway” Show HN will probably land at 10 to 30 pts.
  • A hook works better:
    • (a) a research post, such as “we replayed N agent delegation chains and found scope widening”, mcp-scan style; or
    • (b) a visual: an HN-native title showing the chain, for example “Show HN: Visado – see every hop of an AI agent’s delegation chain (Rust)”.
  • Title format: “Show HN: Name – plain-language what it does”, with no buzzword stack.
  • README order:
    1. A GIF/asciinema of the chain UI above the fold
    2. docker compose up / cargo install with a one-command demo that runs human, agent, agent and tool locally, and ends on a deny
    3. “Why” (threat model, 3 bullets)
    4. Specs implemented (Txn-Token, AuthZEN, WIMSE, AIMS) with versions
    5. Compare table (agentgateway, AIB, Aembit)
    6. Status/limits
  • Interop with agentgateway and AIB adds credibility, since AIB already pairs with agentgateway.

CNCF sandbox day-1 hygiene (CLOMonitor checks)

Section titled “CNCF sandbox day-1 hygiene (CLOMonitor checks)”
  • An ADOPTERS* file
  • DCO: enable the DCO app on all repos
  • OpenSSF Best Practices badge in README
  • Scorecard badge in README (api.scorecard.dev URL)
  • Scorecard-derived checks: binary artifacts, code review, dangerous workflow, dependency update tool, maintained, signed releases, token permissions
  • A recent release
  • An approved license (Apache-2.0 is OK) and license scanning
  • A CNCF Slack reference in README
  • An OpenSSF Security Insights manifest
  • SECURITY.md, CODE_OF_CONDUCT, GOVERNANCE, MAINTAINERS, CONTRIBUTING
  • Sources: https://clomonitor.io/docs/topics/checks/ , https://github.com/cncf/clomonitor/blob/main/docs/checks.md
  • The sandbox onboarding asks for the Best Practices badge, while the security guidelines push Scorecard, so both are needed.
  • For a Rust project, also: cargo-deny/cargo-audit in CI, signed releases (cosign/sigstore), SLSA provenance, and pinned action SHAs (helps the Scorecard token-permissions and pinned-deps checks).
  • The 889 pts figure for workers-oauth-provider is not verified.
  • Hubble UI’s graph library is unknown.
  • The IETF 128 hackathon exact days are inferred.
  • AGNTCon NA CFP deadline was not checked.
  • The otel-rust 0.33.1 stability claim needs a check against the release notes.
  • Everything in the GenAI/MCP semconv is Development and still churning.