Modules
Analysis-only Mix compiler for BEAM projects: incremental argus analyses via roux, reported as rich compiler diagnostics.
Incremental argus analysis as a roux query graph.
The analysis-relevant view of a .beam file.
The scry: project configuration, validated loudly.
Resolved findings → pentiment frames → Mix.Task.Compiler.Diagnostic.
The disk-beam roux frontend: Scry.Analysis's frontend contract,
satisfied from the .beam files the stock compilers just produced.
Output formats for the standalone mix scry task.
The shared driver core for mix compile.scry and mix scry: database
lifecycle, manifest warm start, input sync, the souffle gate, and
analysis demand.
The outcome of one driver run.
Beam discovery and change detection for the compiler driver.
The Argus.Symbols table scry interns fact rows against: an
Argus.Symbols.Store over one of the database's Roux.Intern tables,
so the ids memoized rows carry are persisted in the manifest with them
and mean the same thing on the next run.
Mix Tasks
An analysis-only Mix.Task.Compiler: append it after the stock
compilers and it reads the .beam files they just produced, runs the
configured argus analyses incrementally, and reports findings as
compiler diagnostics with pentiment-rendered frames.
The credo-style one-shot entry point. Compiles the project first, then
drives the same incremental core as mix compile.scry against the
same manifest — a checkout that already ran mix compile costs a
validation walk, not a re-analysis.