2SOLID AI
Professional Scope
The scope of professional services described on this site.
§01 — Instrument
M = 0
bending moment in a funicular rib under uniform load — the arch form above carries its deck in pure compression
funicular theorem · bridge.js
That is what scope means here: every load assigned a path, every path a member, every member an owner. Nothing carried by accident.
§02 — The structure
Datasheet — the bridge is the argument.
A scope document and a structure are the same object: a map of what carries what. The instrument above is a real load-path diagram — read it as our working definition.
| 01Structure type | tied through-arch | deck carried between two inclined ribs |
|---|---|---|
| 02Arch rib profile | y = 4h·s(L−s)/L² | the funicular parabola for uniform deck load |
| 03Rib load mode | compression only | the funicular form — the shape that bends least |
| 04Suspenders | y = a·cosh((ξ−p)/a) + q | true catenaries solved through both anchor points |
| 05Lateral stability | cross-braced lattice | ribs tied against transverse load |
| 06Span behaviour | load → suspenders → rib → abutments | a continuous, explicit load path |
§03 — The argument
Scope is a load path for responsibility.
A structure fails where a load has no member; an engagement fails where a duty has no owner. The articles below divide the firm's work the way the bridge divides its load — explicit paths, named members, and honest boundaries where someone else must carry the final weight.
§04 — Articles of scope
The divisions, and what each one delivers.
Two pillars — engineering and product design — with project management as the spine across both. BIM is a working method, not a deliverable class.
| 01Architectural engineering | spatial systems → building envelope | concepts → coordinated drawing sets |
|---|---|---|
| 02Structural engineering | load paths → members → connections | analysis → calculation & drawing packages |
| 03Civil engineering | site → grading → servicing | site documentation |
| 04Mechanical engineering — MEP | HVAC · plumbing · electrical | systems design → coordinated specifications |
| 05Software & AI engineering | applications · models · agents | systems → tested, deployed software |
| 06Industrial design | form · ergonomics · CMF · DFM | concepts → tooling-ready surfacing & specs |
| 07Prototyping | PCB · mechanical/3D · firmware | boards & parts → validated builds |
| 08Project management | the spine across both pillars | scope, sequence, coordination record |
| 09BIM | method — not a deliverable | models used as coordination instruments |
§05 — Division of responsibility
What we carry — and what we never pretend to.
The honest boundary is structural: some loads are ours, some belong to the client, and some only an authority or a licensed professional in the jurisdiction can carry.
Within scope
The firm's members.
- Defined deliverables — drawings, models, calculations, prototypes, validation records
- Coordination across disciplines — one firm, one record trail
- Design intent carried through to fabrication and construction documents
- Stated limits — where licensed review applies, it is named in the scope
Outside our scope
Loads other members carry.
- Permits and approvals — issued by authorities, never promised by us
- Sealing and statutory submission — appropriately qualified professionals authorized in the applicable jurisdiction
- Site data and program decisions — supplied and owned by the client
- An authority's decision — no honest firm guarantees another body's verdict
§06 — Engagement record
Every engagement keeps a file.
Scope is only real if it is written down. The record classes an engagement maintains — from definition to closeout.
Responsibility, kept on record
per engagement · firm standard
- SCOPE
Written scope of work — what is in, what is out, who owns each boundary
- MILESTONES
Staged checkpoints — reviewable states, not calendar promises
- DELIVERABLES
Document classes per article — drawings, models, calculations, builds
- REVISIONS
Controlled changes — recorded, never ambient
- COMMUNICATIONS
Decisions kept in the record — the file is the memory
- CLOSEOUT
Acceptance record — the scope closes when the deliverables do
Define the load path.
Tell us what needs carrying — we'll return a scope with every member owned.