cambiums by

The operating system for how architecture, engineering, and construction work gets done.

Drawings, field decisions, contracts, costs, people, and conversations move through one accountable operating record.

from cambium (n.) — the living layer where a tree lays down its rings.

The operating map

One practice. One operating loop.

AEC work crosses the field, the office, the books, and the decisions that move a job forward. Cambiums keeps that work connected.

01 · Relationships, pursuits & estimating

Pursuits start with what the practice knows.

02 · Design & technical delivery

Design decisions become coordinated deliverables.

03 · Project delivery & controls

Project controls keep the job aligned.

04 · Field, quality & safety

Field evidence closes the loop.

05 · Commercial, contracts & risk

Commercial terms become owned risk.

06 · Procurement & supply chain

Supply stays aligned with the job.

07 · Workforce & resources

Workforce and resources stay ready.

08 · Finance & enterprise

Finance reflects operating reality.

09 · Information, submissions & handover

Information reaches acceptance and carries forward.

What closes

Work crosses domains until an outcome closes.

  • PursuitAward
  • RequirementApproved design
  • Field eventResolution
  • ChangeCommercial decision
  • NeedDeliveryPayment
  • ReadinessCompliant work
  • RequirementAccepted submission
  • CloseoutNext-job memory
The compounding loop

Capture, verify, recall.

The work enters once. Nothing becomes practice knowledge until someone has checked it.

01 · CAPTURE voicenote email photo message file ingest 02 · VERIFY projects money contracts people vehicles one canonical home per fact extract 03 · RECALL brief draft report alert summary 01 · CAPTURE voicenote email photo message file ingest 02 · VERIFY projects money contracts people vehicles one canonical home per fact extract brief draft report alert summary 03 · RECALL
01 · capture

Voicenotes, emails, photos, messages, and files enter once, with the source and job intact.

02 · verify

Agents connect raw work to projects, money, contracts, and people. What they infer stays marked as inferred until a person accepts it.

03 · recall

The next decision starts from what the practice has already confirmed — obligations, prices, standards, and the judgment a person stood behind.

The trust spine

The gate the record has to pass.

Any tool can remember what happened. What makes a record worth reusing is that it had to get past something first — an owner, a source, a review, a person willing to sign.

  1. 01 Identity & Authority

    Makes it explicit who may see, act, approve, seal, sign, submit, pay, or reverse.

    roles · permissions · professional authority · approval gates

  2. 02 Evidence & Provenance

    Keeps the source, version, locator, transformation, decision, and result together.

    source · version · decision trail · audit record

  3. 03 Interoperability

    Moves work through explicit contracts and adapters instead of brittle copy-paste.

    models · documents · APIs · tenant systems

  4. 04 Workflow & Recovery

    Makes state, ownership, handoffs, failures, retries, and honest stopping visible.

    state · owner · handoff · retry · compensation

  5. 05 Knowledge & Learning

    Carries accepted facts, corrections, outcomes, and professional judgment into the next decision.

    accepted facts · corrections · outcomes · practice memory

  6. 06 Security & Governance

    Protects privacy, IP, retention, professional responsibility, tool governance, and auditability.

    privacy · IP · retention · professional responsibility

The domains show where work happens. The operating loops show what must close. The spine is what keeps an unchecked assumption from hardening into something the next job trusts.

The method

Agentic engineering, in plain terms.

An agent is a program that pursues a goal, remembers what happened, and uses real tools to act. Agentic engineering is the discipline of building with them — treating AI as engineering material, with tolerances, failure modes, and inspection points. Not a chatbot with a to-do list.

The rule that does the most work: whatever produced a result does not get to certify it.

Where the line falls

Humans hold authority. Agents carry the work.

Human Sign contracts Hire crews Take a job Send money Close deals
Agent Draft proposals Redline contracts Reconcile books Route field intelligence Surface follow-ups
Built in practice

Built inside the work.

Cambiums is shaped through the daily operating demands of two AEC practices — one spanning development and construction, the other professional engineering.

New York DEFiNE

Design, development, construction. Ground-up residential, retail rollouts, commercial fit-outs.

  • Pursuit, delivery, and closeout on one project record
  • Books reconciled overnight; the close stays human-approved
  • Field intelligence carried into the job record
  • Subcontractor compliance docs tracked and chased
NY / NJ Polar Engineering

Professional engineering. Permit filings, structural reviews, inspections, condition reports.

  • Permit and inspection queue, deadlines watched
  • Drafts that pull prior-project context
  • Field observations connected to the project record
  • Engineers seal; the system carries the paperwork
cambiums

Every job strengthens the next.

Most practices do the same work twice: once on the job, and again reconstructing what happened on it. The second time is the one that never gets paid for.

  1. 01The work leaves a record, with its source attached.
  2. 02The record carries an action to someone who can own it.
  3. 03The action leaves evidence a person authorised.
  4. 04The evidence becomes judgment the next job starts from.