Internal Candidate - Do Not Deploy To Production
Gemba-to-Agent Sales V4 Candidate
This preview follows the reset instruction: product footage first, locked visual story second, narration later. The current public v3 video remains untouched.
Voiceover is intentionally not created yet. This candidate exists to QA the software sequence, actual UI content, scene mapping, and product-footage percentage before a natural narrator is recorded.
00:00 / 07:23
Scene Mapping QA
| Time | Scene | Intended Action | Actual UI Content | Draft Narration Target |
|---|---|---|---|---|
| 00:00-01:05 | Sales opening with product b-roll | Explain why hidden process knowledge costs money, quality, speed, M&A integration, and AI readiness. | Desktop capture, evidence, approval, VSM, improvement, and agent governance previews. | Most companies believe their processes are documented. Capture Foundry reveals how work actually happens before leaders cut, change, integrate, or automate it. |
| 01:05-01:17 | Owen selects the process step | Open AAV Batch Review and Deviation Handling and select Review Bioreactor Telemetry. | Process owner workspace with selected process and capture setup. | Owen opens the real process and chooses the exact step that needs proof. |
| 01:17-01:29 | Assign Avery as SME | Assign Review Bioreactor Telemetry to Avery Chen. | Assignment fields show Avery Chen, required evidence, due date, and requested by Owen Wright. | He assigns Avery Chen, the subject matter expert who performs this work. |
| 01:29-01:41 | Email handoff | Show the Capture Foundry assignment email and open the desktop assignment. | Process Capture Assignment email for Review Bioreactor Telemetry with CTA. | Avery receives the assignment by email and opens the exact capture request. |
| 01:41-01:55 | Desktop app opens assignment | Open Capture Foundry Desktop with the assignment loaded. | Process, process step, assigned to, requested evidence, and start capture control. | The desktop application opens with the process, step, owner, and required evidence already loaded. |
| 01:55-02:09 | Consent and screen source | Confirm consent and select the screen to record. | Consent dialog and screen-selection dialog. | Before recording begins, Avery confirms consent and chooses the screen that will be captured. |
| 02:09-02:17 | Countdown and recording indicator | Show countdown and recording state. | Three-two-one countdown and active recording indicator. | The system counts down and starts a controlled recording session. |
| 02:17-02:35 | Review telemetry work | Open batch AAV-2026-0814 and inspect pH telemetry. | AAV-2026-0814, observed pH 7.18, approved range 7.20-7.40. | Avery performs the real work and finds the pH value below the approved range. |
| 02:35-02:47 | Screenshot enters evidence | Take screenshot and show evidence count increase. | Screenshot captured into evidence tray. | She captures the exception as evidence, and the evidence tray updates immediately. |
| 02:47-03:03 | Missing verification note and sensitive handling | Add note, mark sensitive, pause, resume. | Operator verification missing note, sensitive flag, pause and resume controls. | She adds the missing operator verification note, marks sensitive content, pauses, and resumes without losing context. |
| 03:03-03:15 | Submit evidence to process | Stop capture and submit evidence to the process shape. | Review and submit screen with recording, screenshots, notes, and files. | Avery submits the capture package back to the exact process step. |
| 03:15-03:29 | Evidence lands on shape | Open shape evidence detail after submission. | Review Bioreactor Telemetry shape with recording, screenshots, notes, files, decisions, exceptions, and AI summary. | The knowledge is no longer trapped with one employee. It is connected to the process shape reviewers need. |
| 03:29-03:47 | Maya reviews evidence | QA reviewer opens evidence and reviews recording, screenshots, note, and AI summary. | QA review screen with captured evidence and AI summary. | Maya reviews the recording, screenshots, note, and summary before accepting the process as standard work. |
| 03:47-04:01 | Maya requests a change | Request correction for missing QA escalation rule. | Change request comment requiring QA escalation when verification is missing. | Maya requests a correction because the escalation rule is missing. |
| 04:01-04:19 | Owen corrects process map | Add Operator Verification Complete decision with yes/no paths. | Decision added to current process map and saved as version 1.1. | Owen updates the map so every team follows the same approved decision rule and escalation path. |
| 04:19-04:33 | Compare versions | Compare version 1.0 and 1.1. | Version comparison highlights the new decision and escalation path. | The version comparison shows exactly what changed and why. |
| 04:33-04:53 | Sequential approvals | QA, Plant Manager, and Compliance approve one at a time. | Approval statuses change for Maya Patel, Jordan Lee, and Elena Rossi with audit log. | Approval happens one decision at a time, with a clear audit trail. |
| 04:53-05:11 | Create VSM from approved process | Create value stream map from approved process data. | Create Value Stream Map workflow selecting approved process data. | Now the team creates the current-state value stream from approved evidence instead of memory. |
| 05:11-05:35 | Review VSM bottleneck | Open VSM block and review waiting, handoffs, rework, exceptions, lead time. | VSM block details with process time, waiting, handoffs, rework, exceptions, and evidence counts. | The VSM reveals where waiting, rework, handoffs, and exceptions consume capacity and create process cost. |
| 05:35-05:49 | Improvement handoff | Create Gemba, Kaizen, PSP, or Optimization action from the VSM bottleneck. | Improvement action created from VSM evidence. | The finding becomes improvement work instead of another disconnected meeting note. |
| 05:49-06:03 | Generate SOP from approved process | Generate SOP from approved process version. | Approved process populates SOP sections. | The SOP is generated from the approved process, evidence, and decision rules. |
| 06:03-06:19 | Agent readiness | Open Agent Readiness and classify automatable, assisted, and human-only work. | Readiness score with automatable, human assisted, and human only categories. | Only after approval does Capture Foundry ask what can be automated and what must stay under human control. |
| 06:19-06:41 | Agent tests run | Run normal batch, low pH, missing signature, conflicting data, and unauthorized release tests. | Test cases pass, route to human review, or block unauthorized release. | The agent is tested before pilot use. Normal work passes, risky work routes to humans, and unauthorized release is blocked. |
| 06:41-07:05 | Business outcomes | Summarize cost, quality, process, knowledge, M&A, and AI outcomes. | Six outcome areas without survey statistics. | Capture Foundry connects process truth to cost, quality, performance, knowledge retention, M&A integration, and safe AI readiness. |
| 07:05-07:23 | Final CTA | End with the final sales close and CTA. | Before you cut it, change it, integrate it, or automate it, understand it. | Capture the work. Approve the truth. Improve the process. Build the future. |