Context

Every project exists within a world of requirements, constraints, decisions, assumptions, relationships, and history. Yet the knowledge that gives a project meaning is scattered across drawings, documents, spreadsheets, emails, conversations, and people’s memories. Corvus makes context native to the project itself, creating one underlying understanding that can inform everything you draw, model, calculate, coordinate, decide, and ultimately share with all of the other disciplines you are working with.

Start with what is already true.

Before you draw anything, the project already knows a great deal. It exists at a particular location, on a particular property, within a particular climate, jurisdiction, and regulatory environment. There may be existing buildings, utilities, easements, topography, neighboring properties, environmental conditions, historic protections, or infrastructure that will shape what is possible. Bring that knowledge into Corvus from the beginning, then let it become richer as the project develops.

Make context native to the project.

Project information should not live somewhere beside the work. Corvus treats context as part of the project itself, alongside its geometry, objects, relationships, and history. Site conditions can inform the model. Program requirements can inform spaces. Regulations can inform the things they govern. Budget, schedule, performance criteria, and owner requirements can remain connected to the decisions they affect. Context becomes part of the underlying project rather than another collection of information that has to be coordinated with it.

Know more than what was drawn.

A drawing can tell you that a wall is there, but it rarely tells you everything that caused it to be there. Perhaps the room requires acoustic separation. Perhaps the tenant requested it. Perhaps the fire strategy requires it. Perhaps an existing column made another arrangement impossible. Perhaps it was simply the best idea at the time. Corvus gives the project a way to carry those reasons forward, so the work can preserve not only what was decided, but why.

Give the project a memory.

Architecture accumulates knowledge continuously. A survey arrives. The owner changes the program. An engineer establishes a criterion. The planning department clarifies a requirement. A field condition contradicts the record drawings. A decision is made in a meeting. An assumption becomes a fact. Corvus lets that evolving knowledge remain connected to the project, so decisions, assumptions, approvals, sources, relationships, and history do not disappear simply because the people working on the building have moved on to the next problem.

Keep information connected to its source.

A requirement came from somewhere. A dimension may come from a survey, a soil condition from a geotechnical report, a performance criterion from an engineer, a product limitation from a manufacturer, an approval from an authority, or a decision from a meeting. Corvus keeps project knowledge connected to its source, so you can understand what the project believes to be true, where that understanding came from, and what evidence supports it.

Not all information carries the same weight.

A client preference is not a code requirement. A consultant recommendation is not an approval. An assumption is not a verified condition. A proposed solution is not a decision. Corvus can distinguish where information came from, who has authority over it, what it applies to, how certain it is, whether it has been verified, and whether something else has since taken its place. Context is not simply knowing more things about a project. It is understanding what those things mean.

Know what you do not know.

Design begins with uncertainty. The survey may not have arrived. The structural system may be unresolved. Existing conditions may need to be verified. The owner may not have selected a tenant. The authority having jurisdiction may not have responded. Corvus lets assumptions remain assumptions, questions remain questions, and unresolved conditions remain visible until something changes. You should never have to make uncertain information look certain simply because the software needs a value.

Let knowledge become more certain.

Projects move from ambiguity toward specificity. Early on, you may know only that the building needs a place to gather. Later, it becomes a 200-person assembly space. Later still, its occupancy, exiting, acoustics, lighting, finishes, equipment, accessibility, and performance requirements become known. Corvus lets project knowledge develop the same way, accumulating specificity without forcing you to define everything before you understand it. Start with what you know, add what you learn, and carry that intelligence forward.

Understand what governs the project.

Every project operates within systems larger than itself. Zoning, building codes, accessibility requirements, environmental regulations, historic protections, owner standards, campus guidelines, engineering criteria, measurement standards, and contractual obligations can all shape what may be designed and built. Corvus gives those requirements a place within the project, including which standards apply, where they came from, what authority they carry, and which parts of the work they govern.

Connect requirements to the things they govern.

A height limit should not live only in a zoning memo. A required fire rating should not live only in a code analysis. An acoustic criterion should not disappear into a consultant report. A rentable-area methodology should not exist only in somebody's spreadsheet. Corvus connects project context to the things it affects, so the model can know the height limit, the wall can know its required rating, the room can know its occupancy, and the floor can know how its area is measured.

Understand the economics of the building.

Budget, cost, rentable area, usable area, efficiency, leasing assumptions, development targets, operating costs, procurement, funding, and phasing are not administrative facts surrounding architecture. They help determine it. Corvus brings the economic context of the project closer to the design itself, so a commercial building can understand how its geometry becomes rentable area, a development can understand the efficiency it is trying to achieve, and a design decision can be considered alongside the financial consequences it creates.

Understand the place.

A location is more than an address or a pair of coordinates. Climate, sun, wind, rain, snow, topography, vegetation, geology, water, hazards, neighboring buildings, streets, transportation, infrastructure, history, culture, and community all contribute to the conditions from which architecture emerges. Corvus gives those conditions a place within the project, so the site is not merely where the model happens to be located. It becomes part of what the project knows.

Understand what is already there.

Existing buildings are full of imperfect knowledge. Record drawings disagree with reality. Renovations were never documented. Materials are unknown. Concealed conditions remain concealed. A wall may be original, altered, protected, load-bearing, contaminated, or none of the above. Corvus lets existing conditions become understood over time, allowing record information, field observations, measurements, photographs, scans, reports, and investigations to contribute to the same evolving understanding without pretending that uncertainty has disappeared.

Let decisions leave a trail.

Design is made from thousands of decisions, and together those decisions become the building. Corvus can preserve the reasoning that matters, including what was considered, what was decided, who was involved, what informed the decision, and what other parts of the project depend upon it. Months or years later, understanding why something happened should not require searching through old emails, meeting minutes, screenshots, and somebody else's memory. The project should remember.

Understand what depends on what.

Decisions rarely exist in isolation. A planning approval may determine the allowable massing. A structural assumption may influence the floor depth. A tenant requirement may affect the core. A product selection may depend on a performance criterion that depends on a code requirement. Corvus can preserve these relationships so the project becomes more than a collection of facts. It becomes a connected understanding of what depends on what, and why.

See consequences before they become problems.

Change is inevitable, but its consequences are not always obvious. Move a wall, and a room gets smaller. Move the wall because of a shaft, and occupancy, clearances, furniture, area calculations, acoustics, cost, coordination, and other decisions may be affected too. When geometry and context belong to the same underlying project, Corvus can help surface the relationships that matter, making it easier to understand not simply what changed, but what the change means.

Understand context across time.

What is true today may not have been true yesterday, and it may not remain true tomorrow. A requirement can be superseded. An assumption can be verified. A proposed condition can be approved. An existing building can become demolition, temporary work can become necessary during construction, and a future phase can depend on a decision that has not yet been made. Corvus gives context a history, so the project can understand not only what is true, but when it became true, how it changed, and what came before it.

Ask better questions.

The most useful system is not always the one with the fastest answer. Sometimes it is the one that recognizes what still needs to be resolved. Has this assumption been verified? Does this requirement still apply? What decisions depend on this approval? Which spaces no longer satisfy the program? What changed when the authority revised its interpretation? What information is missing before this can be decided? Corvus can use the context of the project to help you interrogate the work, surface uncertainty, and direct attention toward the decisions that matter.

Stop explaining the project to AI.

AI becomes far more useful when it understands what you are working on, but today that understanding has to be reconstructed again and again. Upload the documents. Explain the requirements. Describe the site. Provide the background. Correct the assumptions. Tell it what has already been decided. Corvus takes a different approach. When context is native to the project, AI can begin with an understanding of the work already underway instead of asking the architect to continually rebuild that understanding from scratch.

Give AI something better than a prompt.

A prompt is a moment. A project is a history of geometry, objects, relationships, requirements, sources, decisions, uncertainty, approvals, alternatives, and change. That context gives AI something far richer to work with. Corvus can help research a requirement, find its source, explain why something was decided, identify conflicting information, surface an unresolved assumption, trace the consequences of a change, compare alternatives against project criteria, or help determine what needs attention next. Not because AI has been asked to imagine the project, but because Corvus already understands it.

Keep design deeply human.

Understanding the project does not give software the right to design it. Corvus can retrieve information, check requirements, connect relationships, remember decisions, question assumptions, and surface consequences, but architecture still requires judgment, intuition, interpretation, negotiation, imagination, and intent. Project Context is not about handing those decisions to the machine. It is about giving people a clearer understanding of the world within which those decisions are being made.

Everything in its place. And a place for everything.

Drawings, models, worksheets, schedules, quantities, presentations, and timelines are different ways of seeing and working with the same project. Project Context gives all of them a shared understanding of the site, the people, the requirements, the constraints, the ambitions, the decisions, the uncertainties, the history, and the reasons why. The knowledge surrounding the building no longer has to remain scattered around it. In Corvus, it can become part of the project itself.

Join our waitlist.

You’ve already waited 49 years. What’s another two? AEC professionals have spent decades jumping through hoops and creating workarounds for convoluted software. No one dares to build something that will challenge the status quo. It's time for something fundamentally different and unapologetically human. Join the waitlist.