ANULUM / DISCOVERY
Work you can inspect
Explore examples from ANULUM’s own research and software practice, with the source material and limitations available beside each result.
These examples describe ANULUM’s own public work. They are not customer testimonials.
Research communicationTurn a scientific relationship into an experiment
Problem: a formula is difficult to explore without seeing how its inputs affect the result.
Implementation: the compression explorer connects declared inputs to the same closed-form relationships documented by the reactor family. Published presets and source links sit beside the calculations.
Observable result: changing an input updates the quantities and plots. The lab adds comparison, settings links and data exports.
Boundary: the ideal limits do not predict yield or validate a machine.
Evidence presentationMake a comparison auditable
Problem: a result without its assumptions and source is difficult to assess.
Implementation: the reactor comparison links individual numerical anchors to device pages and references, while distinguishing reproduced, consistent and unresolved cases.
Observable result: a reader can follow a comparison row back to its stated source.
Boundary: a reproduced anchor does not by itself establish whole-device validation.
Software discoveryConnect a portfolio to its evidence
Problem: visitors need to understand which project serves their goal and where its evidence lives.
Implementation: the public portfolio records purpose, status and source links. Universal search, the project finder and the atlas reuse those public records.
Observable result: visitors can search a concept, compare project facts and follow a publication or software link.
Boundary: displayed metadata is a dated snapshot, and a relationship link does not prove integration.