AI Team Development — Field + Office

Why field/office friction is a memory problem; six memory layers mapped to real vault structures; projects and AI-drafted charters; curation, supersession and the Consolidator; field-vs-office conflicts and the Conflict Zone. Lab 1 designs a project's team memory.

1. Module 1 pretest Diagnostic pretest · 5 min
2. Field and office as a memory problem, not a process problem Reading · 15 min
3. Memory layers for a field + office project Reading · 15 min
4. Projects and charters for a site or plant Worked example · 15 min
5. Curating canonical across disciplines Reading · 15 min
6. Field-vs-office and cross-discipline conflicts Reading · 15 min
7. Designing a field-office layout end to end Worked example · 15 min
8. Lab 1: Design the team memory for a field + office project AI role-play lab · 45 min
9. Retrieval: 8 questions across the module Retrieval check · 10 min

AI as context translator between disciplines, vocabulary maps and the four collision classes, the MCP-first hand-off ritual, a worked hand-off chain, and diagnosing a botched hand-off. Lab 2 runs a four-discipline chain.

1. Module 2 pretest Diagnostic pretest · 5 min
2. The bridge pattern: AI as context translator Reading · 15 min
3. Vocabulary maps: same word, different meaning Reading · 15 min
4. The hand-off ritual at discipline boundaries Reading · 15 min
5. A hand-off chain worked end to end Worked example · 15 min
6. Scenario: diagnosing a botched hand-off Scenario · 15 min
7. Lab 2: Run a four-discipline hand-off chain AI role-play lab · 45 min
8. Retrieval: 8 questions across the module Retrieval check · 10 min

Nexus Mobile capture surfaces and caption discipline, what really happens offline, the reconnect check, the AI-supported daily standup, site meetings with Nexus Meetings, Home and Plan as the shared daily picture, and getting data from the tools crews already use. Labs 3 and 4.

1. Module 3 pretest Diagnostic pretest · 5 min
2. Field capture with Nexus Mobile Reading · 15 min
3. The daily field-office standup with AI support Reading · 15 min
4. What really happens offline Reading · 15 min
5. The reconnect check, worked Worked example · 15 min
6. Site meetings with Nexus Meetings Reading · 15 min
7. Plan and Home as the shared daily picture Reading · 15 min
8. Getting data from the tools your crews already use Reading · 15 min
9. Lab 3: Three days of intermittent connectivity AI role-play lab · 45 min
10. Lab 4: Run the morning standup and a site meeting AI role-play lab · 45 min
11. Retrieval: 8 questions across the module Retrieval check · 10 min

One role per person across seven tiers, custom roles capped at Operator, per-project permissions and the access matrix, credentials for AI agents and automations, attribution through owners, credentials and conventions, and an access review after a near miss. Lab 5.

1. Module 4 pretest Diagnostic pretest · 5 min
2. One role per person: mapping a mixed crew to roles Reading · 15 min
3. Per-project permissions and the access matrix Worked example · 15 min
4. AI agents and automations: credentials, least access, proof Reading · 15 min
5. Attribution: who decided, who captured, which assistant Reading · 15 min
6. Scenario: an access review after a near miss Scenario · 15 min
7. Lab 5: Configure access and attribution for a six-actor project AI role-play lab · 45 min
8. Retrieval: 8 questions across the module Retrieval check · 10 min

The compliance reviewer as a participant, regulatory inheritance as structured and superseded entries, audit evidence from the hash-chained audit log, the signed control log and Robo Compliance sealed sessions and auditor portal, a worked permit amendment, and adding a reviewer mid-project. Lab 6.

1. Module 5 pretest Diagnostic pretest · 5 min
2. The compliance reviewer as a participant, not a gate Reading · 15 min
3. Regulatory inheritance into team memory Reading · 15 min
4. Audit evidence that holds up Reading · 15 min
5. A permit amendment, worked Worked example · 15 min
6. Scenario: adding a compliance reviewer to an in-flight project Scenario · 15 min
7. Lab 6: Add a compliance reviewer to an in-flight project AI role-play lab · 45 min
8. Retrieval: 8 questions across the module Retrieval check · 10 min

The 45-minute field-engineer onboarding ritual, coaching the MCP-first personal loop in non-software disciplines, common new-contributor failures and their structural fixes, and onboarding AI agents and outside consultants. Lab 7.

1. Module 6 pretest Diagnostic pretest · 5 min
2. The field-engineer onboarding ritual Reading · 15 min
3. Coaching personal-loop fluency in non-software disciplines Reading · 15 min
4. Common new-contributor failures and the structural fix for each Reading · 15 min
5. Onboarding an AI agent or an outside consultant Reading · 15 min
6. Lab 7: Onboard a new field engineer AI role-play lab · 45 min
7. Retrieval: 8 questions across the module Retrieval check · 10 min

The capstone brief, capturing engineering judgment so assistants inherit it, the blameless multi-discipline retro format, and a worked retro. Lab 8 facilitates a retro.

1. Module 7 pretest Diagnostic pretest · 5 min
2. The capstone brief: what is given and what you must produce Reading · 15 min
3. Capturing engineering judgment so assistants inherit it Reading · 15 min
4. Blameless multi-discipline retros Reading · 15 min
5. A retro worked: the pour that waited Worked example · 15 min
6. Lab 8: Facilitate a blameless retro AI role-play lab · 45 min
7. Retrieval: 8 questions across the module Retrieval check · 10 min

How the exam is built and timed, how the capstone is scored with the four discipline anchor exemplars, an interleaved retrieval check across the course, and the capstone role-play.

1. Module 8 pretest Diagnostic pretest · 5 min
2. Exam readiness: blueprint, item types and timing Reading · 15 min
3. How the capstone is scored: rubric and anchor exemplars Reading · 15 min
4. Retrieval: 8 questions across the course Retrieval check · 10 min
5. Capstone: Stand up and run field-office team memory for one project AI role-play lab · 45 min