Explore a fictional project graph through eight repeatable queries. Change the graph or query, then inspect the included items, relationships and reasons. Export the result with a record of the rules and source data used.
Rules inspect the graph you supply. They do not establish that risks are real, controls work, evidence is sufficient, or a decision is approved. “Approved” and “Verified” are input labels. Relationship direction follows the supplied starter schema. Its legacy depends_on label points from predecessor work to a successor, despite the label: check direction when importing. Standard edge types must match their declared endpoint types. Properties support text, finite numbers, booleans and null; structured data belongs in a separately linked source.
The JSON and CSV files are generic mapping formats intended for adapting to tools such as SharpCloud. No vendor import or live connection has been verified. The FNV-1a checksum is a repeatable change indicator, not a cryptographic signature or authentication.
Exports use the most recent successful query; changed controls must be run again. Download CSVs prefix formula-leading text with an apostrophe for spreadsheet use; JSON retains exact values. The receipt records both the chosen parameters and truncation. Tables of query findings and lineage describe the full query before the card limit; lineage can contain context items outside the exported view. Download Graph JSON separately if you need the full input graph for a rerun.