Running a Business with Holdings and Forge
A business can have two connected records. Property Holdings records the place you own. Forge runs the supported operation inside it.
Establish the place through play
Earn, inherit, build, claim, or knowingly accept the business in the story. Once the acquisition is completed and verified, it can appear under Operations > Holdings.
A possibility is not ownership. An opportunity does not put the place in your holdings. Complete and accept the acquisition first, then check the record.
Open the linked Forge
Choose the holding and use Open Forge. Forge owns the operational details it can verify, including:
- workers;
- resources;
- recipes;
- active production;
- completed output;
- stock;
- coffers.
Use the controls that appear in Forge for the selected operation. Property Holdings does not independently copy, advance, or settle these mechanics.
Read the holding separately
Return to Holdings for ownership, control, lifecycle, location, and the readable record of the place. A Committed · Forge label means the displayed value came from the linked Forge rather than from the holding itself.
Collect ready coffers
When the linked Forge has coffers ready to collect, Collect Coffers can appear on the holding record. Use that control and check the result before collecting again.
Use the business in the story
Ask the Narrator to frame a scene at the business, speak with its people, investigate a problem, pursue an opportunity, or react to a verified condition. Check the holding and Forge records for ownership, stock, workers, production, and coffers. A scene description alone is not confirmation that one of those values changed.
Costs
Direct Holdings and Forge management costs 0 Spark. An ordinary Narrator turn keeps its normal Spark cost.
For the full record workflow, source labels, lifecycle states, existing-world behavior, and troubleshooting, read Property Holdings.