Vipera: AI Auditing & Microcore Compiler

• Vipera is defined as two distinct research systems: an interactive auditing workbench for text-to-image generative models and a compiler-runtime framework for dynamic DSLs on micro-core architectures.
• The AI auditing system uses scene graphs, coordinated visual cues, and LLM-powered suggestions to enable systematic exploration and structured inquiry over model outputs.
• The compiler framework translates vPython into efficient native code for micro-core processors, achieving competitive performance and reduced code size compared to traditional C implementations.

Searching arXiv for the relevant Vipera papers to ground the article in the cited literature. arXiv search query: Vipera auditing text-to-image generative AI; Vipera framework DSL micro-core architectures. Vipera denotes two unrelated research systems in the arXiv literature. In 2025, the name referred to an interactive workbench for systematic auditing of generative text-to-image models, designed to support exploration of bias, offense, misinformation, and other problematic outputs through coordinated visual cues and LLM-powered suggestions (Huang et al., 14 Mar 2025, Huang et al., 7 Oct 2025). In 2022, the same name referred to a compiler-and-runtime framework for implementing dynamic Domain-Specific Languages on micro-core processor architectures, with an emphasis on code performance, code size, and transparent offloading (Jamieson et al., 2022). The auditing system is the more developed sense in the 2025 literature; the earlier micro-core framework is a separate line of work that shares only the name.

1. Disambiguation and research context

Within the 2025 human-computer interaction and AI auditing literature, Vipera is presented as a browser-based auditing workbench, and later as a single-page web application, for text-to-image auditing at scale (Huang et al., 14 Mar 2025, Huang et al., 7 Oct 2025). Its motivating premise is that a single prompt can yield dozens or hundreds of diverse images, while the semantic richness of images produces a combinatorial audit space spanning objects, attributes, relationships, and style. The cited studies report that auditors often “just look at the images,” rely on personal intuition, and lack a structured mechanism for tracking which criteria have already been explored (Huang et al., 7 Oct 2025).

The 2022 systems paper uses the same name for a compiler-and-runtime framework supporting a subset of Python called vPython on micro-core architectures with extremely small on-chip scratchpad memories and no hardware cache (Jamieson et al., 2022). Because the two projects occupy different technical domains, treating them as a single software lineage would be misleading. A common source of confusion is therefore nominal rather than conceptual.

For the auditing system, the research problem is not image generation itself but the organization of human inquiry over model outputs. The March 2025 paper frames the central challenge as scalability and thoroughness in AI auditing, together with the difficulty of enabling auditors to explore the auditing space in a structural and effective way (Huang et al., 14 Mar 2025). The October 2025 paper refines this framing into obstacles of scale and semantic richness, then operationalizes Vipera as a multimodal interface that couples visual sensemaking with AI assistance (Huang et al., 7 Oct 2025).

2. Design goals and conceptual model of the auditing system

Vipera’s 2025 auditing papers articulate a set of design goals around structured exploration. The March paper specifies five goals: structured, customizable auditing via interactive visual aids; intuitive comparison of output distributions across multiple prompts; divergent thinking support to surface “unknown unknowns”; prompt-space exploration; and in-tool note taking, provenance tracking, and report generation (Huang et al., 14 Mar 2025). The October paper presents a closely related set of goals, phrased as Interactive Visual Aids, Cross-Prompt Comparison, Divergent Inspirations, Blended Guidance, and Built-in Reporting (Huang et al., 7 Oct 2025). Across both formulations, the system is intended to support top-down and bottom-up auditing without collapsing the process into a fixed checklist.

The conceptual model combines two loops. One is a data flow from prompt entry to image generation, scene-graph construction, attribute labeling, chart embedding, and evidence capture. The other is an inspiration loop in which auditors inspect images or graphs, invoke LLM suggestions, add new prompts or criteria, and then regenerate or relabel outputs (Huang et al., 7 Oct 2025). This arrangement makes the auditing process iterative rather than linear.

A common misconception is to read Vipera as a fully automatic auditing pipeline. The published descriptions instead center the human auditor throughout the workflow: prompts are issued by the auditor, criteria can be added or edited by right-clicking nodes, suggested criteria or prompt edits are accepted or rejected by the auditor, and findings are captured through bookmarking, comments, and note writing (Huang et al., 14 Mar 2025, Huang et al., 7 Oct 2025). The system automates parts of labeling and suggestion, but it does not remove the interpretive role of the auditor.

3. Interface, scene graphs, and coordinated visual analysis

The auditing interface is described as having three main panels. In the March paper these are Prompt input, Analysis view, and Note view; in the October paper they appear as Input View, Analysis View, and Note View (Huang et al., 14 Mar 2025, Huang et al., 7 Oct 2025). The analysis region contains a prompts list or prompts panel, an image thumbnail panel, a scene graph, and a suggestions pane. The note region supports bookmarking, evidence collection, and report writing.

Scene graphs are the central visual abstraction. In the March description, a scene graph comprises nodes for detected objects and edges for semantic relations such as “doctor – in – office,” and users can right-click object nodes to add attribute nodes such as “gender” with a discrete label set such as $\{male, female\}$ (Huang et al., 14 Mar 2025). In the October description, the graph is a rooted tree whose first level is fixed to “foreground” versus “background,” with internal nodes as semantic objects and leaves as attribute nodes (Huang et al., 7 Oct 2025). The construction pipeline there is explicit: randomly sample up to four images, prompt Gemini 2.5 Flash to output a small scene graph per image, merge identical nodes across the sampled graphs, and prune leaf nodes to at most five to avoid overload (Huang et al., 7 Oct 2025).

The graph is tightly linked to other visual cues. Attribute nodes embed stacked-bar charts showing how many images, and which prompts, fall into each value. In the March paper, these charts are said to visualize the proportion of each label per prompt; in the October paper, coordinated color coding links prompts, thumbnails, chart slices, and graph nodes (Huang et al., 14 Mar 2025, Huang et al., 7 Oct 2025). Hover interactions expose labels or corresponding subsets, and relabeling can be triggered when scope or candidate values change (Huang et al., 7 Oct 2025). A scatterplot clustering mode is also reported in the March paper, grouping all generated images by assigned labels to enable prompt-to-prompt visual comparison, although the observational study found that this mode was invoked infrequently (Huang et al., 14 Mar 2025).

The observational evidence clarifies how these visual devices function in practice. Participants in the March study described the scene graph as a “checklist,” and all reportedly found the node-link summary useful for uncovering minority cases, especially small nodes they might otherwise miss (Huang et al., 14 Mar 2025). The later controlled study similarly reports that scene graphs with embedded statistics acted as structured “checklists,” but it also notes that some participants found them overwhelming or psychologically pressuring, describing the experience as feeling “boxed in” (Huang et al., 7 Oct 2025). The significance of Vipera’s visual layer is therefore not merely descriptive; it structures audit attention, but can also shape it too strongly.

4. LLM-powered suggestions, labeling, and formalization

Both 2025 versions of Vipera embed two AI-assisted functions: suggestions for analysis criteria and suggestions for prompt edits. In the March paper, LLaVA v1.6 is used for scene-graph extraction and image labeling, while LLaMA v3.1 is used for prompt-editing suggestions (Huang et al., 14 Mar 2025). The October paper instead reports Gemini 2.5 Flash as the scene graph generator and GPT-5-mini as the labeler and suggestion engine (Huang et al., 7 Oct 2025). This indicates an implementation change across reports, but not a change in the underlying interaction pattern.

For audit-criteria suggestions, the March system samples image pairs from the current audit session together with the partial scene graph, then prompts LLaVA v1.6 with a template such as “Compare these two images; what semantic attribute (object, style, relation) differs notably?” The output is a ranked list of candidate new scene-graph nodes (Huang et al., 14 Mar 2025). In the October system, the suggestion engine selects two images with maximally different embeddings, prompts the LLM to describe their main semantic difference and suggest an attribute node, and only surfaces suggestions if the model’s self-reported confidence exceeds a threshold (Huang et al., 7 Oct 2025). For prompt suggestions, the March system queries LLaMA v3.1 with few-shot examples of semantically close but creatively diverse phrase replacements and returns 3–5 alternative prompts (Huang et al., 14 Mar 2025). The October system describes phrase-level prompt edits such as “doctor” $\rightarrow$ “nurse,” and states that accepting such a suggestion clones the graph branch for “doctor” into a new “nurse” branch so that subcriteria can be compared side by side (Huang et al., 7 Oct 2025).

The March paper also provides intended formalizations for the auditing process, while noting that the paper itself does not provide explicit formal definitions or algorithms. Let $O$ be the set of detected objects, and for each object $o \in O$, let $A_o$ be a finite set of user-defined attributes with value set $V_o$. An auditing criterion is then a tuple $(o, a, V_{o,a})$. For each image $i$ and criterion $(o,a)$, a labeling model defines

$l(i; o,a) \in V_{o,a}.$

Given prompt $\rightarrow$0 and its generated image set $\rightarrow$1, the empirical frequency is defined as

$\rightarrow$2

which is what the stacked bar charts visualize. Illustrative metrics include Shannon entropy

$\rightarrow$3

for diversity, and

$\rightarrow$4

for coverage over prompts $\rightarrow$5 and criteria $\rightarrow$6 (Huang et al., 14 Mar 2025).

These formalizations are useful because they expose the system’s basic statistical object: not an abstract notion of “bias” in isolation, but empirical distributions over user-defined semantic attributes conditioned on prompts. At the same time, the October paper explicitly states that no custom fine-tuning or loss functions are reported, and that behavior is governed by prompt engineering (Huang et al., 7 Oct 2025). Vipera is therefore best understood as an interface and orchestration framework around pretrained multimodal models, rather than as a new end-to-end learning algorithm.

5. Studies, effectiveness claims, and open limitations

The March paper reports an observational user study with $\rightarrow$7 experienced text-to-image auditors: 3 PhD students, 1 postdoc, and 1 engineer; three had prior paid auditing experience, and two had used an earlier Vipera prototype (Huang et al., 14 Mar 2025). Participants audited Stable Diffusion XL for 30 minutes with no constraints on prompts or criteria, used Vipera’s bookmarking mechanism to capture findings, and produced interaction logs, bookmarks, and semi-structured interview data. All participants experimented with 5–10 distinct prompts, defined on average 6 new criteria each, and produced 4 to 9 bookmarked insights (Huang et al., 14 Mar 2025). All auditors reported more systematic coverage of criteria than in their prior “just look at images” workflow, and the paper states that the integrated visual cues and LLM hints generated novel audit leads that would likely remain undiscovered in unguided workflows (Huang et al., 14 Mar 2025).

The October paper extends the evaluation to a controlled experiment with 24 participants: 20 general student auditors with various AI familiarity and 4 expert auditors (Huang et al., 7 Oct 2025). The design is described as within-subjects mixed, with three systems per user in random order: a baseline with a simple “Criteria View,” a scene-graph-only condition, an AI-support-only condition, and the full Vipera condition. Each session included a 5-minute tutorial, a 15-minute task per system, think-aloud, NASA-TLX after each system, and a final interview. Reported NASA-TLX results for the full system relative to baseline include lower Mental Demand ($\rightarrow$8, $\rightarrow$9), lower Physical Demand ($O$0, $O$1), and higher Performance ($O$2, $O$3) (Huang et al., 7 Oct 2025). Additional results include improvements from baseline to scene graph and from scene graph to full Vipera in one group, significant drops in several workload dimensions for AI support relative to baseline in another group, and an increase in Temporal Demand when scene graph was added on top of AI support (Huang et al., 7 Oct 2025).

Interaction logs and qualitative data complicate a purely positive reading. The full system produced the highest number of created criteria, prompts, and images, but fewer bookmarks, which the paper interprets as more exploration with less time spent documenting each insight (Huang et al., 7 Oct 2025). AI authored 78–87% of criteria in the AI-support conditions, but only 50–62% of prompts, suggesting that auditors preferred to author prompts themselves (Huang et al., 7 Oct 2025). Mean BERT cosine similarity of 0.904 across prompts indicates that auditors deliberately kept prompts comparable (Huang et al., 7 Oct 2025). Qualitatively, six insight sources were identified—direct image inspection, scene graph, AI suggestions, prompt comparisons, personal experience, and serendipity—and participants displayed “breadth-oriented,” “depth-oriented,” and mixed auditing patterns (Huang et al., 7 Oct 2025).

The limitations are explicit in both papers. The March paper highlights the need for provenance and narrative support, fine-grained scope control, depth-oriented suggestions, verifier ensembles or human-in-the-loop spot checks for labeling uncertainty, and APIs or plugins for integration with issue-tracking, CI, or reporting pipelines (Huang et al., 14 Mar 2025). The October paper adds that the study was conducted in a lab setting with students, that bookmarks are an imperfect proxy for insights, and that LLM labeling errors often went uncorrected, motivating confidence surfacing and correction mechanisms (Huang et al., 7 Oct 2025). A common controversy in reading such systems is whether AI-generated labels can be trusted as evidence. The literature here does not resolve that concern; instead, it documents it and proposes interface-level mitigations.

6. Vipera as a compiler-and-runtime framework for micro-core architectures

In the 2022 systems literature, Vipera is a compiler-and-runtime framework for implementing dynamic DSLs, especially a subset of Python called vPython, on micro-core architectures (Jamieson et al., 2022). “Micro-cores” are defined there as many-core chips with approximately 32–64 KB scratchpad memories and no hardware cache. The framework’s goals are to automate translation of high-level dynamic-language kernels to efficient native code, manage data movement and kernel launch transparently, and minimize power and memory overheads while delivering performance close to or exceeding handwritten C (Jamieson et al., 2022).

Its architecture is layered and split between host and device. On the host side, Vipera comprises a vPython parser and AST front end, an Olympus Intermediate Representation generator, a back-end code generator that emits portable C source with Olympus mnemonics and statically allocated data structures, a C compiler invocation stage, and an offload orchestrator via the Eithne API (Jamieson et al., 2022). On the device side, the Olympus runtime includes a heap manager with approximately 24 KB footprint on Epiphany-III, dynamic loader and linker stubs, function dispatch and trampoline code, and a device-local execution stub (Jamieson et al., 2022). The code-generation pipeline emphasizes portability and predictable code size, with specific lowering optimizations such as converting for i in range(...) into native C loops with integer iterator registers.

The paper models performance via

$O$4

and code size via

$O$5

Experiments span Adapteva Epiphany-III, Xilinx MicroBlaze, PicoRV32 RISC-V, and several traditional CPUs. For LINPACK, the Epiphany-III results are 139.4 MFLOPS for Olm(-Os), 193.5 MFLOPS for Olm(-O3), 84.0 MFLOPS for Native(-Os), and 106.0 MFLOPS for Native(-O3), with the paper stating that the Olympus kernel in “int” FPU mode outperforms native C by up to 1.8× at -O3 (Jamieson et al., 2022). On other platforms, Olympus is reported as within 5–30% of native C, with code-size ratios in the interval $O$6 for LINPACK (Jamieson et al., 2022). For the Sieve benchmark, the gap is larger, and a micro-benchmark on RISCV64 reports 7.22 s and 5.55 s for a vPython while, 2.33 s and 1.92 s for a vPython for, and 1.33 s and 1.20 s for native C under -Os and -O3, respectively (Jamieson et al., 2022).

The significance of this earlier Vipera lies in dynamic-language implementation on highly resource-constrained processors, not in generative AI auditing. Its reported limitations—code bloat, single-core kernels only, and reliance on host-side compiler quality and ISA flags—belong to compiler and architecture research rather than HCI or responsible AI (Jamieson et al., 2022). The shared name does not imply any technical relation to the 2025 auditing workbench.