AI Workflow Specialist Applicant Proof Surface

Summary

This reusable role page presents John P. Barros III as an AI Workflow Specialist focused on workflow assessment, practical automation, structured outputs, production monitoring, governance, documentation, and business-impact reporting. It uses a public job post as raw role-archetype material without turning the target company into a public page.

Canonical Route

https://webmnem.here.now/ai-workflow-specialist/

Role Surface

ai-workflow-specialist

Surface scope: Reusable role archetype surface

Workbench

/Users/johnbarros/Documents/Codex/10_websites/ai-workflow-specialist

Owner Path

/Users/johnbarros/Documents/Codex/03_employment_engine/AI-Automation-Employment/role-surfaces/ai-workflow-specialist

The owner path is a canonical storage home. It is not the first editing location.

Proof Modules

Workflow assessment and roadmap

The proof stack supports current-state process mapping, bottleneck discovery, automation prioritization, phased implementation planning, and source-of-truth discipline.

Production-ready AI workflows

The operating model emphasizes structured inputs and outputs, validation steps, human review points, exception handling, and stable browser surfaces instead of loose chatbot output.

Governance, testing, and change management

The operating approach treats AI adoption as a managed workflow: approved inputs, review points, monitoring, user guidance, prompt standards, and approval gates.

Reporting and business impact

The role surface frames automation around cycle-time reduction, accuracy improvements, adoption, KPI reporting, and executive-readable proof rather than novelty.

Primary Proof Links

AI Director proof surface: Shows John explaining AI implementation, governance, delivery judgment, and executive-facing technology work.
Business OS Extraction Sprint: Shows the workflow extraction method: inspect current-state operations, map sources of truth, and define what should be automated.
Chat-First Surface Shell: Shows how John turns AI interaction into a usable browser workflow instead of a loose chatbot.
WebMNEM: Shows how John keeps technical notes, work history, and public project context available for review.

Secondary Proof Links

Surface Assistant Reference: Shows the interaction pattern behind a focused role assistant: direct answers, useful follow-up questions, and clear boundaries.
WebMNEM SEO Command Layer: Shows how workflow and market analysis can become an organized execution system.
WebMNEM Market Deployment Engine: Shows how operational insight can be turned into deployable systems and reporting views.

Evidence Boundaries

This page supports workflow assessment, AI-enabled automation design, focused assistant design, documentation discipline, and governance-oriented implementation.
This page does not replace formal verification of employment history, credentials, certifications, manufacturing-domain tenure, regulated QA ownership, or private client outcomes.
The source job post is raw material for role extraction, not a reason to create a company-named public site.
Company-specific targeting belongs in the resume, cover letter, application notes, and application record unless a custom public company page is explicitly approved.

Approval Gates

Do not create a company-named public page without explicit approval.
Do not sync generated output to the owner folder without human approval.
Do not deploy to WebMNEM or Netlify without human approval.
Do not Git push without human approval.
Do not overwrite assistant packs in owner folders without human approval.
Do not copy large source trees into the workbench without human approval.

Validation Requirements

Workbench folder exists.
Required folder skeleton exists.
SITE_MANIFEST.json parses.
publish-map.json parses.
mission-control.txt and mission-control.md exist.
llms.txt exists.
proof-map.json exists.
Assistant pack exists for bounded proof interpreter mode.
Private application-context note exists.
Public route is role archetype, not company-named.
No owner sync occurred.
No deploy occurred.
Compiler receipts exist.

Compiler Boundary

No sync, deploy, publish, Git push, owner overwrite, or large source copy was performed by the compiler.

Role Surface Doctrine

Do not create new websites from scratch. New role site equals compiled variant of the existing applicant proof surface system. Latest approved surface in, role-specific variation out. Extract the role. Do not immortalize the company. The company gets the cover letter, resume, application packet, private notes, and submission receipt. The role gets the public website. The proof stack gets reused. Company-specific public pages require explicit approval.

# AI Workflow Specialist Applicant Proof Surface ## Summary This reusable role page presents John P. Barros III as an AI Workflow Specialist focused on workflow assessment, practical automation, structured outputs, production monitoring, governance, documentation, and business-impact reporting. It uses a public job post as raw role-archetype material without turning the target company into a public page. ## Canonical Route `https://webmnem.here.now/ai-workflow-specialist/` ## Role Surface `ai-workflow-specialist` Surface scope: Reusable role archetype surface ## Workbench `/Users/johnbarros/Documents/Codex/10_websites/ai-workflow-specialist` ## Owner Path `/Users/johnbarros/Documents/Codex/03_employment_engine/AI-Automation-Employment/role-surfaces/ai-workflow-specialist` The owner path is a canonical storage home. It is not the first editing location. ## Proof Modules ### Workflow assessment and roadmap The proof stack supports current-state process mapping, bottleneck discovery, automation prioritization, phased implementation planning, and source-of-truth discipline. ### Production-ready AI workflows The operating model emphasizes structured inputs and outputs, validation steps, human review points, exception handling, and stable browser surfaces instead of loose chatbot output. ### Governance, testing, and change management The operating approach treats AI adoption as a managed workflow: approved inputs, review points, monitoring, user guidance, prompt standards, and approval gates. ### Reporting and business impact The role surface frames automation around cycle-time reduction, accuracy improvements, adoption, KPI reporting, and executive-readable proof rather than novelty. ## Primary Proof Links - [AI Director proof surface](https://john-barros-director-ai-technology.netlify.app/): Shows John explaining AI implementation, governance, delivery judgment, and executive-facing technology work. - [Business OS Extraction Sprint](https://business-os-extraction-sprint.netlify.app/): Shows the workflow extraction method: inspect current-state operations, map sources of truth, and define what should be automated. - [Chat-First Surface Shell](https://chat-first-surface-shell.netlify.app/): Shows how John turns AI interaction into a usable browser workflow instead of a loose chatbot. - [WebMNEM](https://webmnem.here.now/): Shows how John keeps technical notes, work history, and public project context available for review. ## Secondary Proof Links - [Surface Assistant Reference](https://surface-assistant.netlify.app/): Shows the interaction pattern behind a focused role assistant: direct answers, useful follow-up questions, and clear boundaries. - [WebMNEM SEO Command Layer](https://webmnem-seo-command-layer.netlify.app/): Shows how workflow and market analysis can become an organized execution system. - [WebMNEM Market Deployment Engine](https://webmnem-market-deployment-engine.netlify.app/): Shows how operational insight can be turned into deployable systems and reporting views. ## Evidence Boundaries - This page supports workflow assessment, AI-enabled automation design, focused assistant design, documentation discipline, and governance-oriented implementation. - This page does not replace formal verification of employment history, credentials, certifications, manufacturing-domain tenure, regulated QA ownership, or private client outcomes. - The source job post is raw material for role extraction, not a reason to create a company-named public site. - Company-specific targeting belongs in the resume, cover letter, application notes, and application record unless a custom public company page is explicitly approved. ## Approval Gates - Do not create a company-named public page without explicit approval. - Do not sync generated output to the owner folder without human approval. - Do not deploy to WebMNEM or Netlify without human approval. - Do not Git push without human approval. - Do not overwrite assistant packs in owner folders without human approval. - Do not copy large source trees into the workbench without human approval. ## Validation Requirements - Workbench folder exists. - Required folder skeleton exists. - SITE_MANIFEST.json parses. - publish-map.json parses. - mission-control.txt and mission-control.md exist. - llms.txt exists. - proof-map.json exists. - Assistant pack exists for bounded proof interpreter mode. - Private application-context note exists. - Public route is role archetype, not company-named. - No owner sync occurred. - No deploy occurred. - Compiler receipts exist. ## Compiler Boundary No sync, deploy, publish, Git push, owner overwrite, or large source copy was performed by the compiler. ## Role Surface Doctrine Do not create new websites from scratch. New role site equals compiled variant of the existing applicant proof surface system. Latest approved surface in, role-specific variation out. Extract the role. Do not immortalize the company. The company gets the cover letter, resume, application packet, private notes, and submission receipt. The role gets the public website. The proof stack gets reused. Company-specific public pages require explicit approval.