A useful Avaritia wiki should answer two layers of questions at once: what the progression concept is, and which implementation of that concept your modpack actually uses.
Project identity
Document the exact Avaritia project, Minecraft version, loader, and mod version at the top of your notes. This prevents recipe information from one branch being mistaken for another branch with the same item names.
Progression map
Organize the mod by systems instead of individual items: early infrastructure, neutron-related production, resource compression or singularities, Extreme Crafting components, catalysts, and Infinity-tier outputs. The exact names vary by branch, but the dependency graph matters more than the catalog.
Recipe research
Use your installed recipe viewer as the source of truth for the current pack, because scripts and datapacks can alter recipes. A website can explain concepts, but the running instance reveals the exact recipe graph used by that world.
Singularity research
For modern data-driven implementations, inspect how singularity definitions specify resource type, quantity, timing, display properties, and whether recipes are enabled. Pack authors can use these values to align Avaritia costs with the rest of the economy.
Integration research
Check which other mods contribute materials or special recipes. Avaritia is often most interesting when the final craft requires outputs from several established systems rather than only vanilla resources.
Keep notes versioned
When the mod or pack changes, update the notes with the release date and version. A wiki without version context can become actively misleading in a mod ecosystem where APIs and recipes move quickly.
Related guides
Continue with another focused guide from the Avaritia resource library.