Selected NXTG.AI Artifacts You Can Verify Publicly
A selected, non-exhaustive set of NXTG.AI artifacts, each paired with the public probe that supports the narrow claim beside it. Run the probe; treat the result as time-stamped evidence.
Explore 12 articles in the research category.
A selected, non-exhaustive set of NXTG.AI artifacts, each paired with the public probe that supports the narrow claim beside it. Run the probe; treat the result as time-stamped evidence.
One night our agent fleet produced at least 9 wrong or almost-wrong claims the harness caught before they shipped — and at least one reached the running server before a second layer of defense masked the impact. An honest account of the harness — probes at the authority source, verifiers separate from generators, hooks that block, typed state over prose — making individually fallible agents collectively trustworthy, with the line drawn exactly where the evidence stops.
Most agentic systems keep their intelligence in the wrong place: the transcript. Dx3 is our answer — a persistent, transactional substrate collapsing relational, vector, and graph retrieval into one PostgreSQL boundary, with truth-fidelity ranking that returns the current record rather than whatever was remembered. The substrate our own multi-agent fleet already thinks through, seams and all.
CRUCIBLE is a governance protocol that audits whether an AI agent's own test-and-coverage system provides evidence not controlled by the same producer. Three forensic cases: 3,277 passing tests hid silent data loss; a 77% coverage badge masked an audit estimate of ~15%; 4,726 passing tests could not prove real-database reachability.
How NXTG.AI governs 18 software projects with autonomous Claude Code agents using a 7-layer autonomy stack, a 23-principle constitution, and a file-based directive protocol that survives process death and machine reboots.
A production-scale study of brokerless multi-agent AI coordination: two autonomous agents on two machines governed a 21-project portfolio for 21 weeks using a version-controlled git repository as the sole coordination substrate — no message broker, no shared database, no orchestration service.
Measurement fraud is when the AI system that produces code also grades it, so evals pass while the code is broken. Definition, how to detect it, and how to prevent it.
A single-day census of what our production multi-agent harness caught: at least 9 wrong or almost-wrong claims caught before they shipped, and at least one that reached a running server before it was caught. Disclosed counting rule, per-item record including the miss, and an honest statement of what the numbers do and do not support.
We built ASIF for a simple reason — one-shot AI is not enough; real AI work needs a control plane.