WBS↔LINK Challenge: Can you build a better Schedule ↔ WBS ↔ Cost crosswalk?

I've spent about 15 years around capital projects, and this is one problem that keeps showing up.

The schedule is developed, structured and coded one way. The cost system another. The owner has a Work Breakdown Structure (WBS). Then contractors bring their own coding structures into the mix.
Same project. Different structures. And somehow, somebody has to make them connect.

I've been working through an idea called WBS↔LINK: an AI-enabled approach to mapping these structures, surfacing what needs review, and eventually carrying approved relationships from one reporting cycle to the next.

WBS↔LINK is still early, and that's exactly why I'm putting it in front of this community. There is a lot of project controls experience here, and I want that expertise to pressure-test both the problem and the approach before I take the solution much further.

So rather than tell you I've solved it, I'm putting the problem out there as a challenge.

I've built a fictional project across three monthly reporting cycles, with schedule, cost, WBS and contractor records.

Your challenge is to build the crosswalk.

Excel. Power Query. SQL. Python. AI. Whatever you use.

Map it. Submit your results. See how your approach scores against the benchmark and other submissions.

But the score is only part of it. Once you've worked through the data, I want to know where the challenge falls short of the real thing.

What would make this harder on one of your projects? What have I missed?
Your experience will help shape the next version of the challenge and, ultimately, WBS↔LINK itself.

Map. Review. Reuse.

WBS↔LINK: https://zp-projects.github.io/wbs-link/

GitHub: https://github.com/ZP-Projects/wbs-link