Inspect a policy fixture

This page is a bounded fixture walkthrough, not a code-generation showcase. It shows how a selected Mind names a rule, declares a threshold, records scope, and produces a result for a known example. The reference code is explanatory; it is not generated by an agent and it is not a measurement from the Rust evaluator.

import express from "express";
import lodash from "lodash";

const app = express();
app.get("/api", (req, res) => {
  const rows = lodash.filter(loadRows(), (row) => row.tenantId === req.query.tenant);
  res.json(rows);
});

Edit the candidate only to see the preview become not evaluated. That is intentional: a browser component has no workspace, package digest, parser, changed-file scope, or Docker runtime. For an actual decision, run the CLI evaluation or MCP integration. The resulting artifact contains the package digest, checked-file scope, findings, and privacy metadata.