Ilmu Komputer & AI editorial
NovaFabric: Tamper-Evident, Replayable Evidence for Autonomous AI Agent Runs
The core problem
Innovation
Why it matters
The results position NovaFabric as a promising but incomplete solution for audit-grade agent evidence. The strong tamper rejection and perfect redaction of credential types with preserved decoys demonstrate that the sealing and redaction mechanisms work as intended. The diff localisation of all 140 mutations further supports the integrity guarantees. However, the low declared-stream completeness of 0.652 reveals that a significant fraction of declared events are not captured, which undermines the evidentiary value of the capsule. The tool-using workload gap—only 2/10 completed—is critical because many consequential agent actions involve tools. The missing tool-response substitution means that mocked replay cannot fully re-execute tool-using runs, limiting replayability. The distributed ingest cap of 61.6 req/s due to per-worker serialisation suggests that scaling to high-throughput agent fleets will require architectural changes, such as parallelising serialisation or sharding. The blast-radius query performance is strong, with 3.3× speedup over a columnar baseline at 10M edges, but the 100M-edge latency of 167.9ms may be acceptable for interactive queries. The six defects found, with four fixed, one withdrawn, and one open, indicate active maintenance but also that the evaluation corpus itself had issues. The conditional verification on a trusted computing base means that the security guarantees are only as strong as the TCB. The contribution is integration, not new cryptography, so the novelty lies in combining existing standards into a coherent evidence pipeline. Future work should address tool-response substitution, improve declared-stream completeness, and scale ingest. The overall implication is that tamper-evident, replayable evidence for autonomous agents is feasible but requires careful attention to tool interactions and distributed performance. The replay protocol's four modes can be represented as:
This state diagram illustrates the progression from fully mocked to fully live replay, with each mode adding a live component while retaining the capsule as the source of truth for sealed components.
Who should read this
Opening member content…