How Darwin Is Structured
Darwin is best understood as a layered platform.
Each layer has a different responsibility inside the request-to-baseline workflow:
request → clarify → estimate → review → approve → track → learn
Operational Layer
Section titled “Operational Layer”Darwin.Site is where users do the work.
It is the operational workspace for:
- intake and clarification of work requests
- project creation and project summaries
- estimations, revisions, reports, comparisons, and review findings
- modules, price lists, materials, labor, expenses, and catalog context
- IFC and 2D QTO quantity workflows
- files, comments, tasks, and activity history
- approval requests and approval decisions
- actual-cost entry, cost tracking, and variance review
For a learner, this means Darwin.Site is the place where the workflow becomes visible and actionable.
Domain Layer
Section titled “Domain Layer”Darwin.API stores the business model.
It preserves:
- work request and task state
- project context
- reusable cost logic
- price snapshots and provenance
- quantity provenance
- approval decisions and approved baselines
- active baseline references for cost control
- actual-cost and variance records
This matters because tasks, requests, approvals, baselines, and actual costs are connected, but they are not interchangeable.
Access Layer
Section titled “Access Layer”Darwin.Auth and Darwin.Admin govern who can enter the platform and what customer instance they operate within.
Darwin.Auth handles authentication, invitations, password recovery, and tenant-aware access.
Darwin.Admin handles platform governance: users, instances, assignments, invitations, and delegated instance-owner operations.
Enablement and Market Layer
Section titled “Enablement and Market Layer”Darwin.Learn teaches the product and operating model. Darwin.Landing explains the product publicly.
Strategic Meaning
Section titled “Strategic Meaning”Darwin is no longer a small estimating app. It is a platform for reusable cost knowledge, governed estimating, and lifecycle cost intelligence.
The important learning point is that Darwin should not be understood as disconnected features. A project, request, estimate, approval, baseline, actual cost, and variance report are stages in one operating model.