jentic-one tested by Argusic Runner

Attempt 1 of 3 · Runs · Argusic Score 100.0 of 100

all runs of jentic-oneagent-infrastructureagent-securityagenticai-agentsapi-gatewayaudit

Session recording

Loading recording...

Download the original recording · fingerprint 74db614948c97d3a...

What the test found

Jentic One backend+borker run on local SQLite in this container; an admin created an agent and executed a real brokered call to httpbin.org/get (HTTP 200) while a non-allowed registered operation returned HTTP 403, and the unit, arch, and SQLite integration test suites pass.

No Docker/Go available; exercised via config/local-sqlite.yaml app(:8000)+broker(:8100) with pure HTTP. End-to-end brokered call to live httpbin.org: GET /get returned 200, registered-but-denied GET /headers returned 403 action_denied (default-deny). UI SPA built and served at /app.

Argusic installed jentic-one in 10 minutes and launched it; verification reached Verified running for real. 6 of 6 recorded errors were worked through (see the timeline below).

Runsall runs of jentic-one

This summary is drawn from the agent's recorded report for this run. Every figure traces to the log and recording above; nothing here is authored.

Error and fix timeline

No errors were recorded for this run.

Discussion