bRRAInSkills stacks · Practitioner
v2.0

AI Coding with bRRAIn — Industry Edition

Drive an AI coding assistant on engineered work with pinned standards, verifiable gates and human-owned life-safety calls.

Level
Practitioner
Learning time
18 hours
Price
$499
Credential
Valid 3 years
Enroll on learn.brrain.io See the syllabus
What's new in v2.0

What changed in this edition.

  • Session method is now MCP-first: start_brain_session, live session files created at open, and record_assistant_turn / record_decision / record_learning during work. The git-based open/closure checklists are taught as an alternative for git-mirrored teams.
  • New lessons on connecting Claude Code, Claude Desktop or VS Code to the vault through brrain-mcp, on per-project permissions, and on model choice: the Handler is bRRAIn's default, commercial models are opt-in, and an external assistant is a separate data flow to approve.
  • New document-memory lesson: Mega-parser ingestion of drawings and specification PDFs, full-text search with filetype: filters, and confirming values against the original in the raw-byte viewer.
  • POPE tagging corrected to the POPE-Tagging Standard v1.1 (persons, orgs, places, events, plus projects and products); discipline and standards move to their own metadata fields.
  • New lessons on the standards-conformance gate, the audit trail for AI-touched work, Correction & Supersession, handovers, ownership scenarios and a complete worked retro; every content lesson ends with an applied exercise and a retrieval prompt.
  • Labs are AI role-plays in the browser; the capstone is a written package AI-scored against a published rubric with four anchor exemplars, one per discipline.
Outcomes

What you will be able to do.

  • You will be able to connect an AI coding assistant to your organization's vault and run a governed, recorded session on a discipline project.
  • You will be able to seed and maintain a project's standards register, units, glossary and tool-chain file so assistant output is edition-pinned, unit-explicit and correctly worded.
  • You will be able to find drawings, specifications and reports in the vault and confirm every value an assistant uses against the original source.
  • You will be able to drive BIM, mine-planning, CAD/CAM/PLM and civil design tools with an assistant, choosing between vendor APIs and open formats per task.
  • You will be able to pass AI-touched engineered work through DRC, FAT, model-check and standards-conformance gates with recorded evidence.
  • You will be able to keep life-safety and regulatory decisions with named engineers through the privileged path, and assemble the audit evidence behind them.
  • You will be able to classify failures, run blameless retros and turn findings into owned, dated changes to templates, files and gates.

Who it's for

  • Senior and principal engineers in Construction, Mining, Manufacturing or Civil adopting AI assistants in design and analysis work
  • Project engineers who use BIM, CAD/CAM, mine-planning or civil design tools daily
  • Engineering consultants integrating AI assistance into client deliverables
  • Tool-chain power users who automate Autodesk, Bentley, Siemens, Hexagon, Maptek, Datamine or similar software

Not covered here

  • Pure software engineering (see AI Coding with bRRAIn, the same loop without the industry overlay)
  • Multi-disciplinary team flow (see course 2 of the stack)
  • Physical-delivery release train (see course 3 of the stack)
  • Industry architecture (see course 4 of the stack)
  • Teaching discipline codes or tools themselves, and professional licensure
Syllabus

7 modules, 65 lessons.

About 18 hours of learning. Open a module to see every lesson.

  1. Discipline Foundations 7 lessons · 1 h 30 min

    Why engineered work changes the AI coding loop: edition-pinned codes, explicit units, project nomenclature and tool-chain versions; the cost profile of fabrication in physical work; what transfers from software AI coding; and the bRRAIn surfaces an engineer uses.

    1. Pretest: what you already know Diagnostic pretest · 5 min
    2. Why discipline matters in AI prompts Reading · 15 min
    3. Standards as memory: codes, specs and regulations as canonical context Reading · 15 min
    4. The cost of fabrication in physical-world work Reading · 15 min
    5. Industry overlay vs software-only AI coding: what changes, what stays Reading · 15 min
    6. The bRRAIn surfaces an engineer actually uses Reading · 15 min
    7. Module 1 retrieval check Retrieval check · 10 min
  2. Governed Workspace, Session Method and Discipline Memory 11 lessons · 3 h

    Connect Claude Code, Claude Desktop or VS Code to the vault through brrain-mcp; run the MCP-first session method; choose permissions and models for a project; seed the standards register, units, glossary and tags; record discipline decisions; and review AI-assisted work in Nexus. Lab 1 seeds a workspace and proves it.

    1. Pretest: governed workspace and session method Diagnostic pretest · 5 min
    2. Connecting your coding assistant to the vault Worked example · 15 min
    3. The session method, MCP-first Reading · 15 min
    4. Permissions, models and what leaves the building Reading · 15 min
    5. Seeding the standards register Worked example · 15 min
    6. Units and nomenclature in canonical memory Reading · 15 min
    7. POPE tagging for engineering files Worked example · 15 min
    8. The discipline decision record Reading · 15 min
    9. Reviewing AI-assisted work in Nexus: the checking engineer's view Scenario · 15 min
    10. Lab 1: Seed a discipline workspace and prove it works AI role-play lab · 45 min
    11. Module 2 retrieval check Retrieval check · 10 min
  3. Documents and Tool-Chain Integration 10 lessons · 2 h 45 min

    Find and verify drawings and specifications in the vault; drive BIM (Construction), mine planning and simulation (Mining), CAD/CAM/PLM (Manufacturing) and civil design suites (Civil) with an assistant; pivot to IFC, LandXML, STEP, MTConnect or AAS where it fits; and stop API hallucination with version-pinned tool-chain notes. Lab 2 drives a tool-chain task end to end.

    1. Pretest: documents and tool chains Diagnostic pretest · 5 min
    2. Drawings, specifications and reports in the vault Worked example · 15 min
    3. Driving an AI assistant against BIM (Construction) Worked example · 15 min
    4. Driving an AI assistant against mine planning and simulation (Mining) Worked example · 15 min
    5. Driving an AI assistant against CAD, CAM and PLM (Manufacturing) Worked example · 15 min
    6. Driving an AI assistant against civil design suites (Civil) Worked example · 15 min
    7. The open-format pivot: IFC, LandXML, STEP, MTConnect and AAS Reading · 15 min
    8. Tool-chain API notes: stopping API hallucination at the source Worked example · 15 min
    9. Lab 2: Drive a discipline tool-chain task end to end AI role-play lab · 45 min
    10. Module 3 retrieval check Retrieval check · 10 min
  4. Discipline Prompts and Verifiable Gates 12 lessons · 3 h 45 min

    Prompts that respect codes, units and nomenclature; the DRC, FAT, model-check and standards-conformance gates; life safety as a hard invariant; the audit trail for AI-touched work; and a gated change end to end. Lab 3 engineers prompts and gates for a life-safety task; Lab 4 catches three induced failures.

    1. Pretest: discipline prompts and verifiable gates Diagnostic pretest · 5 min
    2. Prompts that respect codes, units and nomenclature Worked example · 15 min
    3. The DRC gate: design rule check Reading · 15 min
    4. The FAT gate: factory acceptance test Reading · 15 min
    5. The model-check gate: interference and modelling standards Reading · 15 min
    6. The standards-conformance gate: checking every citation Worked example · 15 min
    7. Life safety as a hard invariant Reading · 15 min
    8. The audit trail for AI-touched engineered work Reading · 15 min
    9. A gated change end to end (worked example with fading) Worked example · 15 min
    10. Lab 3: Engineer prompts and gates for a life-safety task AI role-play lab · 45 min
    11. Lab 4: Catch and correct three induced discipline failures AI role-play lab · 45 min
    12. Module 4 retrieval check Retrieval check · 10 min
  5. Memory Discipline and Standards Interpretation 8 lessons · 2 h 15 min

    Capture standards interpretations with condition and scope; bring prior interpretations into prompts; consolidate a session into canonical project files; correct and supersede openly; and hand a project to another engineer. Lab 5 consolidates a week of records and handles a correction.

    1. Pretest: memory discipline and interpretation Diagnostic pretest · 5 min
    2. Capturing standards interpretations Worked example · 15 min
    3. Using prior interpretations as context Reading · 15 min
    4. Consolidating a discipline session: what to promote, what to leave Reading · 15 min
    5. Correcting and superseding engineering knowledge Reading · 15 min
    6. Handing a project to another engineer Scenario · 15 min
    7. Lab 5: Consolidate a discipline session and handle a correction AI role-play lab · 45 min
    8. Module 5 retrieval check Retrieval check · 10 min
  6. Triage and Retrospectives 8 lessons · 2 h 15 min

    AI-versus-human ownership with consequence class; the discipline failure-class taxonomy; blameless retros with honest three-bucket attribution; ownership scenarios across four disciplines; and a complete worked retro. Lab 6 runs a retro on an induced failure.

    1. Pretest: triage and retrospectives Diagnostic pretest · 5 min
    2. AI-versus-human triage with physical consequences Reading · 15 min
    3. The discipline failure-class taxonomy Reading · 15 min
    4. The blameless retro for discipline work Reading · 15 min
    5. Ownership calls across four disciplines Scenario · 15 min
    6. A complete retro, worked Worked example · 15 min
    7. Lab 6: Run a discipline retro on an induced failure AI role-play lab · 45 min
    8. Module 6 retrieval check Retrieval check · 10 min
  7. Capstone and Exam Readiness 9 lessons · 2 h 30 min

    The capstone package and how it is scored; planning and pacing the build; the retro section; the four anchor exemplars; the exam format and strategy; and the reasoning traps candidates most often fall into. Ends with the capstone lab.

    1. Pretest: capstone and exam readiness Diagnostic pretest · 5 min
    2. The capstone brief: a discipline deliverable package Reading · 15 min
    3. Planning and pacing the capstone build Reading · 15 min
    4. The capstone retro section Worked example · 15 min
    5. Anchor exemplars: what 92, 78, 71 and 54 look like Reading · 15 min
    6. The certification exam: format, strategy and readiness Reading · 15 min
    7. Patterns candidates most often get wrong Scenario · 15 min
    8. Capstone lab: submit your discipline deliverable package AI role-play lab · 45 min
    9. Module 7 retrieval check Retrieval check · 10 min
Labs and capstone

Practice against someone who pushes back.

Labs run in your browser as AI role-plays. An AI plays the person on the other side of the scenario — with their own goals and objections — and your work is scored against the published rubric. There is nothing to install.

  • Lab 1 · Governed Workspace, Session Method and Discipline Memory

    Seeding a discipline project workspace (register, units, glossary, tags, decisions) with a project principal who challenges every line

  • Lab 2 · Documents and Tool-Chain Integration

    Driving a discipline tool-chain task (IFC schedule, airflow requirement, roughing program or culvert sizing) and reviewing an assistant draft with planted defects

  • Lab 3 · Discipline Prompts and Verifiable Gates

    Engineering prompts and a gate plan for a life-safety change with the engineer of record

  • Lab 4 · Discipline Prompts and Verifiable Gates

    Reviewing an AI-drafted deliverable with three planted discipline failures under deadline pressure

  • Lab 5 · Memory Discipline and Standards Interpretation

    Consolidating a week of session records and handling a late-discovered wrong interpretation

  • Lab 6 · Triage and Retrospectives

    Facilitating a blameless retro on an AI-touched incident with a frustrated project director

  • Lab 7 · Capstone and Exam Readiness

    Submitting a discipline deliverable package to a meticulous checking-engineer scorer

Capstone

Discipline deliverable package: from brief to prepared-for-sign-off, with gates, records and retro

Artefact submitted in the capstone lab, AI-scored against the published rubric

Pass mark: 72%

Scored on

  • Workspace, session method and memory records20%
  • Standards, units and nomenclature fidelity20%
  • Prompting and tool-chain integration20%
  • Verifiable gates and life-safety handling25%
  • Triage and retrospective15%
Exam and credential

One exam. A credential anyone can verify.

The exam

Items per form
59
Time allowed
120 min
Pass mark
72%
Performance tasks
4
Attempts included
2
Wait between attempts
7 days
  • Online and timed, taken on learn.brrain.io.
  • Your form is assembled for you from the course's item bank, so no two candidates sit the same paper.
  • Performance tasks are conducted by an AI examiner: you work through a realistic scenario and are scored against a published rubric.

The credential

  • A verifiable digital badge in your name.
  • A public verification page at learn.brrain.io/verify, so an employer or client can confirm it.
  • Valid for 3 years.
  • Renewal: At 3 years by passing the then-current exam; CE modules keep the credential current between renewals
Questions

Frequently asked.

Do I need to install anything for the labs?

No. Labs and the capstone run in your browser on learn.brrain.io as AI role-plays: an AI plays the person on the other side of the scenario, and your work is scored against the rubric published with the course.

How is the exam delivered?

Online and timed: 59 items in 120 minutes, on a form assembled for you from the course's item bank. 4 of the items are performance tasks conducted by an AI examiner: you do the work rather than pick an answer. The pass mark is 72%.

What if I don't pass first time?

You have 2 attempts, with a 7-day wait after an unsuccessful attempt. Further exam attempts can be bought for $299 each.

How long is the credential valid?

3 years. You receive a verifiable digital badge with a public verification page at learn.brrain.io/verify, so anyone can confirm it is genuine.

I hold the v1 credential. Is it still valid?

Yes. Credentials earned on v1 remain valid and verifiable at learn.brrain.io/verify. When you renew, you sit the then-current version of the exam.

Can my company enroll a team?

Yes. Firms can buy a certification bundle for $2,999 per firm per year — see the pricing page — or contact us to arrange enrollment for a larger group.

Also in bRRAInSkills stacks

Related courses.

See every bRRAInSkills stacks course · Full catalog

Enroll

AI Coding with bRRAIn — Industry Edition

Drive an AI coding assistant on engineered work with pinned standards, verifiable gates and human-owned life-safety calls.

Enroll on learn.brrain.io Back to all courses