Audit and Signature
EmakiForge writes audit data to forged result items after successful forging. This data helps trace the source recipe and validate whether material contribution data was tampered with.
Audit data
ForgeAuditBuilder writes data such as:
| Field | Description |
|---|---|
recipe_id | Recipe id used for forging. |
quality | Quality tier name. |
multiplier | Quality multiplier. |
forged_at | Forge timestamp. |
materials_signature | Stable hash signature of material contribution data. |
output_item | Output item source shorthand. Written only when the recipe configures an output item source. |
materials | Material contribution list. |
Material signature
materials_signature is computed only from material contributions whose consumed amount is greater than zero. The same set of material contributions always yields the same signature, so it can be used to compare an item's forging material data against an expected value.
Relationship with refresh
The Forge item refresh service reads recipe_id and quality from the audit data to rebuild the forge layer presentation. Items whose audit data is missing, or whose recipe has been deleted, cannot have their forge layer rebuilt.
Use cases
- Trading or recycling systems can read audit data to determine an item's source recipe and quality.
- External analytics can aggregate forge output by
recipe_id,quality, andforged_at.
Forge does not ship a built-in command for viewing audit data. Use an external tool that can read item PDC when manual inspection is needed.