01 · Ask
It starts with a real question
Infrastructure professionals don't think in prompts. They think in opportunities, risks, projects and decisions. So we follow one business development question from start to finish, the way a practitioner would actually ask it: plain language, no jargon. Your domain knowledge matters most.
02 · Structure
Good questions have structure
Behind every question sits shared context: sector, geography, stage, stakeholders, intent. The community learns faster when everyone starts from the same language. This is where OpenConstruct begins.
03 · Method
Methods matter more than models
The difference between a good answer and a bad one is rarely the AI model. It is the method used to solve the problem. OpenConstruct captures those methods as reusable Skills, framing, tools, agents and all.
04 · Skill
Skills are institutional knowledge made reusable
Every organization develops ways of working, and most of it stays trapped in documents and people's heads. A Skill turns a proven workflow into a reusable asset anyone can run, written in plain Markdown that declares its inputs, the tools it needs, and the agents it runs.
05 · Evidence
Skills call the evidence
Skills don't guess. They reach into project records, procurement data, geospatial systems, risk intelligence, market signals and external sources. Evidence first, opinion second.
06 · Specialists
Specialists do what they do best
Some systems understand projects, some geography, some entities, some risk. OpenConstruct coordinates specialists, Records, Entity, Geospatial and Signals, instead of asking one system to know everything.
07 · Collaborate
Intelligence emerges from collaboration
The strongest answers rarely come from a single source. Project data, entities, risk signals, spatial context and market intelligence are analyzed together. That's how fragmented information becomes intelligence.
08 · Grounded
Every answer is grounded
Every recommendation traces back to projects, documents, agencies, contracts, risks and sources. The planned California transit projects come back ranked, sourced and ready to act on. Transparency is how trust is built.
09 · Compound
Knowledge compounds
A useful answer rarely ends with one decision. It creates new questions: market expansion, partner selection, pursuit strategy, competitive analysis, risk review. One workflow becomes many.
10 · Assemble
Workflows become applications
When a workflow is repeatedly useful, it becomes an application. Add context and the pieces light up, assembling the skills, tools and agents into one reusable build. The community doesn't start from scratch every time; it builds on what already works.
11 · Lenses
The same question, many lenses
Every grounded answer can be explored more than one way: a table to scan, a dashboard to monitor, a map to walk the ground, an alert to stay ahead. The form follows the work, not the other way around.
12 · Monitor
A lens for the long view
Risk-weighted, mapped and live, the same workflow becomes a dashboard you could watch every week, tracing each number back to the projects and sources beneath it.
13 · Spatial
A lens on the ground
Where the planned corridors actually are, what each is worth, and how risky, so the spatial picture tells you where to focus first.
14 · Library
The library grows
Every workflow added by the community becomes a building block for everyone else. One prompt becomes a Skill, one Skill becomes an Application, one Application becomes institutional knowledge. That's how industries learn.