A World Engine Manual is Created
Phase 2 is about taking Nubimancy from working extensions to a fully realized business ecosystem – thousands of realistic, interconnected records that demonstrate how these systems work together in practice.
This past week we completed the knowledge planning foundation. It’s not a giant leap forward, but it’s the critical groundwork that will allow us to generate consistent, believable demo data at scale in the next phase. With the worldbuilding files complete and the CSV schema mapped out, we have a clear blueprint for how to populate the BC environment with data that reflects the rich lore and economic systems we’ve created.
The Problem with Demo Data
Anyone who has built a BC demo environment knows the pain. You need customers, vendors, items, locations, posting groups, resources, routes, contracts — and you need them to make sense together. A vendor who ships widgets should logically appear as a source on item cards. A customer in one city should have delivery routes that pass through plausible waypoints. The chart of accounts should reflect a real business, not a patchwork of test codes.
For Nubimancy, this problem is multiplied by five – five distinct hero companies, all running different industries, all interacting with each other and with a shared world economy. Bran’s caravan routes need to intersect with Thorin’s ale delivery schedules. Delyra’s enchantment services need pricing that’s calibrated against the same wage baseline that governs Weltina’s creature care staff.
Manually crafting thousands of records that maintain this level of internal consistency would take months. We needed a better approach.
The Plan: Knowledge First, Data Second
The insight driving Phase 2 is that the worldbuilding files are the source of truth for data generation. If the economic rules, geographic constraints, cultural naming patterns, and trade relationships are all documented in a consistent, structured way, AI agents can use those rules to generate thousands of authentic records – rather than inventing them one at a time.
This is the “Smart Template Multiplication” approach:
Base Templates (10–50 business types)
× Cultural Variations (20 cities/kingdoms)
× Size Variations (small/medium/large)
× Quality Grades (poor/common/fine/masterwork)
= Thousands of Authentic Records
For it to work, the knowledge has to be there first. That’s what we just built.
What We Built This Past Week
29 Worldbuilding Documents Covering Every Major System
The Knowledge/worldbuilding/ directory now contains 29 files covering every major system in the Nubimancy world. Ten files are fully complete and ready to drive data generation:
- Economics & Currency – the Aurumvale Crown decimal system (1.00 = 1 gold / 0.10 = 1 silver / 0.01 = 1 copper), wages by employment class, 11 kingdom currencies with exchange rates, shipping and portal cost formulas
- Labor & Guilds – employment classification for BC Resources, guild structures, tax brackets, journeyman vs. master wage bands
- Cities – 20 cities, each with export/import specializations, cultural themes, and BC scenario mapping
- Heroes – character backstories, business motivations, The Fivefold Oaths origin story
- Geography, Magic Systems, Kingdoms & Politics, Measurements & Units, Aethernet Assembly, Business Central Teams
Eight more files reached “Framework” status this week – fully structured with all the detail needed for data generation:
- Brewing & Ale Culture – Thorin’s four-grade barrel system (Iron/Bronze/Silver/Gold/Conjunction Dark), preservation requirements, tavern network commerce, festival coordination
- Enchantment Types & Magical Craft – the complete Tier 1–4 enchantment system with pricing ranges, decay mechanics, refresh services, lunar alignment dependencies
- Arena Types & Combat Traditions – Rini’s arena classifications, combat traditions by culture, fighter classification tiers, broadcast rights structure
- Dimensional Pocket Mechanics – Delyra’s Fold (7:1 time acceleration), planar habitat pockets for Weltina’s conservation work, the distinction between portal gates and pocket dimensions
- Portal Network & Mage Specializations – 10/10 city portal coverage split, four mage specializations (Architect/Transit/Creature-Capable/Charter), political closure risk
- Warden Territory System – Weltina’s five-rank Warden Guild, eight terrain types, quota enforcement authority, migration corridor data feeding Bran’s route intelligence
- Patronage & Auction Culture – Weltina’s four-tier conservation patronage system, five auction formats, the broadcast rights sealed-bid process, and why Thorin’s taproom events explicitly avoid auction mechanics
- Preservation Magic & Scroll Technology – Bran’s scroll substrate types, climate-zone preservation tiers, scrying intelligence services, arcane mail service levels, the color-code alert system
Economy Reconciliation
Along the way, we caught and corrected several internal inconsistencies that had accumulated across documents – guard wages had a denomination error (were listed in gold, should be silver/day), the standard barrel volume was inconsistent, inn pricing had a decimal error. All resolved and locked in. The economics-and-currency.md file is now the canonical reference that all other pricing defers to.
73 CSV Schema Files Mapping to AL Tables
The data-planning/ directory now contains 73 CSV schema files. Each file’s header row maps directly to a specific AL table in one of the 19 production extensions, following BC import-ready naming conventions (Country_Region_Code, City_Code, etc.).
Every hero company’s extensions are covered:
| Hero | Extensions | CSV Files |
|---|---|---|
| Nimbus (shared) | NimbusCoreFoundation, NimbusSupply, NimbusExhibition, NimbusManufacturing | 01–30 |
| Bran | ArcaneScrollProcessing, MysticalRoutePlanning, CaravanFestivalCoordination | 31–40 |
| Thorin | DwarvenAleQualityTracking, TavernNetworkRelationshipManagement, CommunityEventOrchestration | 41–49 |
| Delyra | EnchantmentRefreshServices, MultiplanarWorkCenters, PortalShopManagement | 50–56 |
| Rini | DimensionalTournamentBrackets, MultiRealmSportsBroadcasting, FighterProgressionAnalytics | 57–62 |
| Weltina | AdvancedCreatureCareProtocols, MultiHabitatManagement, PatronAuctionManagement | 63–73 |
The cross-extension dependency chain is fully mapped too – for example, ClimateZone data (file 31, Bran’s extension) feeds into PreservationRequirement (file 34), which feeds AleTypeProfile (file 42, Thorin’s extension), which feeds quality tracking downstream. When you generate the climate zone records first, everything that depends on them can be generated in the right order.
Architecture Reference Updated
As a final step, the ArchitecturePlanning.md reference doc was updated to reflect Phase 1 completion – with a new Conceptual→Actual Extension Mapping table, actual extension names in every diagram and reference (replacing conceptual PTE node names from the planning phase), and a Phase 2 Planning section replacing what used to be Next Steps.
What Comes Next
The knowledge foundation is now in place. The next phase is data generation – using the worldbuilding files as source material for AI-assisted generation of the actual CSV content.
The strategy has three tiers:
- High-Detail (Hand-crafted) – Hero companies and their direct relationships. ~1,000 records, created deliberately so every customer, vendor, and item has a story.
- Medium-Detail (Template × Culture) – Background businesses in each city using cultural naming patterns extracted from worldbuilding. Dwarven forges, elven leaf-markets, maritime harbor-side wholesalers. ~5,000 records generated systematically.
- Low-Detail (Systematic Fill) – Scale demonstration data, filling the world enough that reports and analytics look like a real operational environment.
The goal is to have this data generation phase complete before the Phase 2 extension build work begins in earnest – so that when we demonstrate extensions in webinars, there’s a real world behind them.
This is the part of the project that doesn’t show up in a line count or an AppSource listing, but it’s what makes everything else work. If you want to follow along, the Knowledge repository is public on GitHub – all 29 worldbuilding files and all 73 CSV schemas are open.
More updates as the data generation phase kicks off. If you’ve been through this problem yourself – building realistic demo data for complex multi-company BC environments – I’d be interested to hear how you approached it.