Stop reconciling a stack of apps that each define your project differently. Your determinations, trades, bonds, lien positions, and payment chains live as one ledger-anchored graph -- and every workspace, field card, and counterparty link is projected from it, never rebuilt by hand.
Why it matters
The modeling surface is where your operating world lives -- not our product catalog, your world. County prevailing-wage determinations, union locals, bonds, lien positions, permit regimes, and payment chains: modeled once as a single graph instead of scattered across disconnected apps. You stop maintaining the same fact in seven systems.
It runs on Cascade, the hierarchical-inheritance engine. Your graph is a closure-tree of nodes, and four merge strategies -- MERGE, UNION, INTERSECT, FLOOR -- inherit values down it, so a county rule set once applies everywhere below. Surfaces are projected from that graph by the page-layout resolver, never precast in code: variation is data, not a hand-built screen.
The work, split
The agent keeps the model current. A new wage determination publishes for your county; it ingests the change, re-projects every surface that depends on it, and proposes the update -- damped, corroborated, and never weakening a compliance or money floor. The calm work of keeping one graph coherent across hundreds of surfaces runs without you.
When a change touches the model structurally -- a new payment chain, or a floor that governs money or compliance -- you ratify it. You decide on a number no one at the table can dispute, with a receipt that traces to the federal determination or the ledger-anchored verification behind it. The graph records who decided, and why.
How it works
Pick your county and your trade. Watch one graph project the working surface for your seat -- desk, field, or counterparty -- and sharpen as your community uses it.