fraim 2.0.362-next.4 → 2.0.362

package/dist/registry/stubs/jobs/ai-employee/salesforce/sf-build-automation.md

@@ -0,0 +1,34 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: sf-build-automation
+
+## Intent
+Translate a business process requirement into a live Salesforce Flow — record-triggered, scheduled, or screen — and validate it against real records before activating.
+
+## Outcome
+- **Reviewable deliverable:** A .docx document at docs/salesforce/sf-build-automation-{YYYY-MM-DD}.docx with Flow design specifications, build results (Flow Id, version, status), test results, activation status, and known limitations
+- Salesforce Flow built, tested, and activated (or left inactive if the stakeholder requests manual activation review)
+- Flow version documented with trigger condition, decision logic, and action summary
+
+## Steps
+1. Phase 1: `receive-requirements`
+2. Phase 2: `design-flow`
+3. Phase 3: `build-flow`
+4. Phase 4: `test-flow`
+5. Phase 5: `activate-flow`
+6. Phase 6: `produce-summary`
+7. Phase 7: `submit`
+8. Phase 8: `address-feedback`
+9. Phase 9: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "sf-build-automation" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/salesforce/sf-build-dashboard.md

@@ -0,0 +1,35 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: sf-build-dashboard
+
+## Intent
+Turn a business requirement into a working Salesforce dashboard — query the right objects, build the supporting reports, assemble the dashboard, and validate that every tile loads with real data.
+
+## Outcome
+- **Reviewable deliverable:** A .pptx presentation at docs/salesforce/sf-build-dashboard-{YYYY-MM-DD}.pptx containing dashboard tiles with KPI charts, report summaries, validation results, and data dependencies
+- Report(s) created or updated in Salesforce
+- Dashboard created or updated and verified to load without errors
+- Business stakeholder confirmed each KPI appears on the correct tile
+
+## Steps
+1. Phase 1: `receive-requirements`
+2. Phase 2: `design-reports`
+3. Phase 3: `build-reports`
+4. Phase 4: `build-dashboard`
+5. Phase 5: `validate`
+6. Phase 6: `produce-summary`
+7. Phase 7: `submit`
+8. Phase 8: `address-feedback`
+9. Phase 9: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "sf-build-dashboard" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/salesforce/sf-config-deployment.md

@@ -0,0 +1,35 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: sf-config-deployment
+
+## Intent
+Translate ServiceNow change tickets into Salesforce configuration changes — deploying custom fields, objects, validation rules, and permission sets via the Metadata API — and update the ServiceNow ticket with the deployment result.
+
+## Outcome
+- **Reviewable deliverable:** A .docx document at docs/salesforce/sf-config-deployment-{YYYY-MM-DD}.docx with ServiceNow ticket details, Salesforce configuration intent, deployment results, validation findings, and drift detection report
+- Salesforce configuration deployed and validated
+- Drift detection report comparing intended vs. actual SF state
+- ServiceNow change ticket updated with deployment status
+
+## Steps
+1. Phase 1: `read-change-ticket`
+2. Phase 2: `translate-to-sf-config`
+3. Phase 3: `deploy-and-validate`
+4. Phase 4: `detect-drift`
+5. Phase 5: `update-snow-ticket`
+6. Phase 6: `produce-summary`
+7. Phase 7: `submit`
+8. Phase 8: `address-feedback`
+9. Phase 9: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "sf-config-deployment" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/salesforce/sf-data-management.md

@@ -0,0 +1,34 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: sf-data-management
+
+## Intent
+Execute Salesforce data operations — bulk import, export, deduplication, mass field updates, and data quality cleanup — safely, with a validation step confirming the operation completed as intended.
+
+## Outcome
+- **Reviewable deliverable:** A .docx document at docs/salesforce/sf-data-management-{YYYY-MM-DD}.docx with operation type, scope, execution results, validation outcomes, error analysis, and rollback procedures
+- Data operation completed: records imported, exported, updated, merged, or deleted per the request
+- Validation confirming record counts and field values match the intended outcome
+- Rollback log if the operation was partially applied and needs reversal
+
+## Steps
+1. Phase 1: `receive-request`
+2. Phase 2: `profile-data`
+3. Phase 3: `execute-operation`
+4. Phase 4: `validate-results`
+5. Phase 5: `produce-summary`
+6. Phase 6: `submit`
+7. Phase 7: `address-feedback`
+8. Phase 8: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "sf-data-management" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/salesforce/sf-org-health-check.md

@@ -0,0 +1,38 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: sf-org-health-check
+
+## Intent
+Audit the Salesforce org's health across governor limits, API consumption, storage, security posture, and automation inventory — and surface the top risks before they become outages.
+
+## Outcome
+- **Reviewable deliverable:** A .pptx presentation at docs/salesforce/sf-org-health-check-{YYYY-MM-DD}.pptx containing governor limits utilization tables, API consumption trends, storage projections, security risk summaries, automation inventory, and health score scorecards
+- Governor limits utilization report with red/amber/green status per limit
+- API daily request consumption and trend (7-day rolling)
+- Data and file storage utilization with projected fill date
+- Security health: inactive users with active sessions, profiles with broad permissions, MFA enrollment rate
+- Automation inventory: active Flows, Process Builders, Workflow Rules, Apex triggers — with last-modified date and owner
+
+## Steps
+1. Phase 1: `connect`
+2. Phase 2: `audit-governor-limits`
+3. Phase 3: `audit-api-usage`
+4. Phase 4: `audit-storage`
+5. Phase 5: `audit-security`
+6. Phase 6: `audit-automations`
+7. Phase 7: `produce-summary`
+8. Phase 8: `submit`
+9. Phase 9: `address-feedback`
+10. Phase 10: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "sf-org-health-check" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/salesforce/sf-user-and-access-management.md

@@ -0,0 +1,35 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: sf-user-and-access-management
+
+## Intent
+Execute user and access changes in Salesforce — provisioning users, assigning profiles and permission sets, managing roles, and configuring sharing rules — with a verification step to confirm the intended access was applied.
+
+## Outcome
+- **Reviewable deliverable:** A .docx document at docs/salesforce/sf-user-and-access-management-{YYYY-MM-DD}.docx with request summary, changes applied (before/after values), verification results per change, and any failure remediation steps
+- User records created, updated, or deactivated per the request
+- Profile, permission set, and role assignments applied
+- Sharing rules created or modified if the request requires record-level access
+- Access verified: the affected user can (or cannot) access the intended records
+
+## Steps
+1. Phase 1: `receive-request`
+2. Phase 2: `validate-request`
+3. Phase 3: `execute-changes`
+4. Phase 4: `verify-access`
+5. Phase 5: `produce-summary`
+6. Phase 6: `submit`
+7. Phase 7: `address-feedback`
+8. Phase 8: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "sf-user-and-access-management" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/security/compliance-continuous-monitoring.md

@@ -0,0 +1,31 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: compliance-continuous-monitoring
+
+## Intent
+Between `compliance-review` runs, detect drift — controls whose status has changed since the last bundle (Pass → Fail, evidence expired, policy stale) — and file `compliance:drift` issues before the next audit cycle.
+
+## Outcome
+- **Reviewable deliverable**: A .docx document at docs/compliance/compliance-continuous-monitoring-{YYYY-MM-DD}.docx containing drift analysis summary with control status changes, evidence expiration details, and severity-classified findings.
+- **Filed drift issues**: One per drifted control (deduplicated).
+- **Idempotence**: A second run with no intervening changes files no new issues.
+
+## Steps
+1. Phase 1: `baseline-load`
+2. Phase 2: `current-state-scan`
+3. Phase 3: `drift-analysis`
+4. Phase 4: `drift-report-and-file`
+5. Phase 5: `address-feedback`
+6. Phase 6: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "compliance-continuous-monitoring" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/security/compliance-policy-authoring.md

@@ -0,0 +1,31 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: compliance-policy-authoring
+
+## Intent
+Produce first-draft governance policies required by the active regulations — Information Security, Acceptable Use, Incident Response, Access Control, Data Retention & Disposal, Vendor Management, Change Management, Business Continuity, Data Classification — adapted from the template library under `templates/compliance/policies/` (each template fetched per policy via `get_fraim_file`).
+
+## Outcome
+- **Reviewable deliverable**: Policy documents in .docx format at docs/compliance/policies/{policy-name}-{YYYY-MM-DD}.docx with complete frontmatter (owner, last-reviewed, next-review, related-controls, applicable-regulations) and draft banner.
+- **Draft banner**: Every generated policy carries "Requires legal review before adoption."
+- **Gap closure**: `policy-completeness-check` subsequently passes for all required policies.
+
+## Steps
+1. Phase 1: `policy-scoping`
+2. Phase 2: `policy-drafting`
+3. Phase 3: `policy-review`
+4. Phase 4: `policy-submission`
+5. Phase 5: `address-feedback`
+6. Phase 6: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "compliance-policy-authoring" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/security/compliance-questionnaire-response.md

@@ -0,0 +1,32 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: compliance-questionnaire-response
+
+## Intent
+Answer a customer security questionnaire (SIG Lite, CAIQ, or similar) OR review a customer-supplied DPA, drawing exclusively from the most recent `docs/compliance/compliance-review-*/` bundle. Unanswerable items are flagged, never fabricated.
+
+## Outcome
+- **Reviewable deliverable**: A .docx document at docs/compliance/questionnaire-{customer}-{YYYY-MM-DD}.docx or docs/compliance/dpa-review-{customer}-{YYYY-MM-DD}.docx with evidence-linked answers and unanswered items flagged.
+- **Evidence-linked answers**: Every answer cites a specific evidence artifact in the latest bundle.
+- **Unanswered items flagged**: Items with no supporting evidence carry `unanswered — no supporting evidence in latest compliance-review package`.
+
+## Steps
+1. Phase 1: `questionnaire-ingest`
+2. Phase 2: `evidence-matching`
+3. Phase 3: `answer-drafting`
+4. Phase 4: `self-review`
+5. Phase 5: `response-submission`
+6. Phase 6: `address-feedback`
+7. Phase 7: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "compliance-questionnaire-response" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/security/compliance-requirements-detection.md

@@ -0,0 +1,30 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: compliance-requirements-detection
+
+## Intent
+Analyze feature descriptions and project context to detect applicable compliance frameworks, then update the project configuration.
+
+## Outcome
+- Final artifact: Project `fraim/config.json` updated with confirmed regulations list.
+- **Clear Understanding**: A clear understanding of which compliance frameworks apply to the feature/project.
+
+## Steps
+1. Phase 1: `analyze-features-and-context`
+2. Phase 2: `present-and-confirm`
+3. Phase 3: `update-configuration`
+4. Phase 4: `detection-submission`
+5. Phase 5: `address-feedback`
+6. Phase 6: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "compliance-requirements-detection" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/security/compliance-review.md

@@ -0,0 +1,34 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: compliance-review
+
+## Intent
+Single-invocation compliance umbrella: confirm applicable regulations, build the cross-regulation control crosswalk, run per-regulation evidence-management jobs, aggregate gaps across regulations (dedup via crosswalk), check policy completeness, and bundle everything into an auditor-ready output at `docs/compliance/compliance-review-{YYYY-MM-DD}/`.
+
+## Outcome
+- **Reviewable deliverable**: A .pptx presentation at docs/compliance/compliance-review-{YYYY-MM-DD}.pptx with executive summary, control crosswalk visualization, gap/remediation scorecard, policy status dashboard, and remediation priority matrix.
+- Final artifact: a single compliance report at `docs/compliance/compliance-review-{YYYY-MM-DD}/README.md` containing the executive summary, control crosswalk, gaps and remediation plan, policy status, and run metadata as sections. The per-regulation evidence subfolders sit alongside it in the bundle directory; no other report files are created.
+- **Deduplicated remediation issues**: One issue per unique control gap, labeled with every affected regulation.
+- **Evidence feed**: The bundle is consumed by `generate-audit-evidence` and `soc2-evidence-management` as a first-class evidence source.
+
+## Steps
+1. Phase 1: `applicable-regulation-confirmation`
+2. Phase 2: `control-crosswalk-build`
+3. Phase 3: `per-regulation-evidence-generation`
+4. Phase 4: `gap-analysis-and-remediation-filing`
+5. Phase 5: `policy-gap-check`
+6. Phase 6: `compliance-report-bundle`
+7. Phase 7: `address-feedback`
+8. Phase 8: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "compliance-review" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/security/generate-audit-evidence.md

@@ -0,0 +1,34 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: generate-audit-evidence
+
+## Intent
+Generate comprehensive compliance audit documentation by analyzing system implementations against specific regulatory requirements and evidence.
+
+## Outcome
+- **Reviewable deliverable**: A .pptx presentation at `docs/compliance/generate-audit-evidence-{YYYY-MM-DD}.pptx` generated from the final artifact; this is the outcome delivered for stakeholder review, with the .md below as the canonical agent-side record.
+- Final artifact: The audit report at `docs/compliance/generate-audit-evidence-{YYYY-MM-DD}.md` with evidence matrix, regulation-by-regulation compliance status, remediation roadmap, and technical proof table.
+- **Evidence Matrix**: A technical proof table mapping implementation evidence to regulatory clauses.
+- **Remediation Issues**: GitHub issues automatically filed for any detected compliance gaps.
+- Individual audit reports organized by regulation (e.g., GDPR, SOC2).
+
+## Steps
+1. Phase 1: `compliance-config-analysis`
+2. Phase 2: `evidence-source-identification`
+3. Phase 3: `regulatory-mapping-and-analysis`
+4. Phase 4: `audit-report-generation`
+5. Phase 5: `audit-submission`
+6. Phase 6: `address-feedback`
+7. Phase 7: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "generate-audit-evidence" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/security/regulation-evidence-management.md

@@ -0,0 +1,33 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: regulation-evidence-management
+
+## Intent
+Generate an auditor-ready evidence package for a single regulation — SOC 2, ISO 27001, GDPR, CCPA/CPRA, HIPAA, PCI-DSS, or another configured regulation — by scoping applicable clauses, collecting evidence against each, validating completeness, and filing gaps as remediation issues. One job, parameterized by regulation; the agent picks the correct planning and evidence-collection skills per run.
+
+## Outcome
+- **Reviewable deliverable**: A .pptx presentation at docs/compliance/compliance-review-{YYYY-MM-DD}/regulation-{regulation}-evidence-{YYYY-MM-DD}.pptx with scope statement, evidence matrix dashboard, control-to-artifact mapping, and gap analysis summary.
+- **Scope statement**: Clause-level applicability for the regulation under review.
+- **Evidence matrix**: Clause/control → evidence artifact citations.
+- **Gap remediation issues**: Filed via `gap-analysis-aggregation` for missing / stale items.
+
+## Steps
+1. Phase 1: `evidence-planning-and-scoping`
+2. Phase 2: `automated-evidence-collection`
+3. Phase 3: `evidence-documentation-and-formatting`
+4. Phase 4: `evidence-validation-and-gap-analysis`
+5. Phase 5: `regulation-submission`
+6. Phase 6: `address-feedback`
+7. Phase 7: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "regulation-evidence-management" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/security/security-baseline-setup.md

@@ -0,0 +1,32 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: security-baseline-setup
+
+## Intent
+Draft the minimum viable security baseline for a product from nothing, covering identity, secrets, environment separation, dependency hygiene, and release-review-gate existence. When the project has detected AI/LLM/agent components, also cover the governance questions a code scan can't answer.
+
+## Outcome
+- **Reviewable deliverable**: A .docx document at docs/security/security-baseline-setup-{YYYY-MM-DD}.docx with baseline plan, critical gaps, owners, rollout sequence, and proof signals.
+- Security baseline covering auth, secrets, environments, logging, dependency hygiene, and release review.
+- Explicit launch blockers and review gates before live access or control changes.
+- A conditional AI-governance section - documented tool/model access-boundary policy, a review gate before adding a new model/tool integration - included only when the project has AI/LLM/agent components.
+
+## Steps
+1. Phase 1: `security-baseline-discovery`
+2. Phase 2: `security-control-design`
+3. Phase 3: `security-rollout-plan`
+4. Phase 4: `submit`
+5. Phase 5: `address-feedback`
+6. Phase 6: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "security-baseline-setup" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/security/security-review.md

@@ -0,0 +1,32 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: security-review
+
+## Intent
+Review an explicit security scope, separate confirmed findings from hypotheses, and prepare evidence-backed remediation or escalation guidance.
+
+## Outcome
+- **Reviewable deliverable**: A .pptx presentation at docs/security/security-review-{target}-{YYYY-MM-DD}.pptx with review scope, confirmed findings, hypotheses or gaps, severity rationale, remediation queue, verification evidence, and control mapping.
+- Findings are source-backed with concrete evidence references and redacted snippets.
+- Remediation, issue filing, accepted-risk recording, external disclosure, and live changes happen only after the approval gates in this job and the shared rule are satisfied.
+- When a run turns up systemic baseline gaps (missing identity/secrets/environment-separation controls, no release-review gate, no evidence hooks) rather than isolated per-file findings, `security-baseline-setup` is recommended as a follow-up job instead of re-deriving those process gaps as individual findings.
+
+## Steps
+1. Phase 1: `threat-surface-detection`
+2. Phase 2: `security-scan`
+3. Phase 3: `fix-or-file`
+4. Phase 4: `security-report`
+5. Phase 5: `address-feedback`
+6. Phase 6: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "security-review" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/security/soc2-evidence-management.md

@@ -0,0 +1,32 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: soc2-evidence-management
+
+## Intent
+Generate comprehensive SOC2 compliance evidence packages by automatically collecting, documenting, and formatting evidence from project systems to demonstrate adherence to Trust Service Criteria during annual audits.
+
+## Outcome
+- **Reviewable deliverable**: A .pptx presentation at docs/compliance/soc2-evidence-{YYYY-MM-DD}.pptx with Trust Service Criteria scorecard, evidence collection status by control, remediation roadmap, and gap analysis with supporting evidence narratives.
+- **Automated Collection**: Minimized manual effort in evidence gathering.
+- **Gap Detection**: Identified missing controls and evidence with remediation plans.
+
+## Steps
+1. Phase 1: `evidence-planning-and-scoping`
+2. Phase 2: `automated-evidence-collection`
+3. Phase 3: `evidence-documentation-and-formatting`
+4. Phase 4: `evidence-validation-and-gap-analysis`
+5. Phase 5: `soc2-submission`
+6. Phase 6: `address-feedback`
+7. Phase 7: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "soc2-evidence-management" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/security/vulnerability-triage-and-remediation.md

@@ -0,0 +1,33 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: vulnerability-triage-and-remediation
+
+## Intent
+Normalize an externally supplied vulnerability list into an evidence-backed remediation queue, prioritize by impact and exploitability, and prepare approved remediation or escalation steps.
+
+## Outcome
+- **Reviewable deliverable**: A .docx document at docs/security/vulnerability-triage-{target}-{YYYY-MM-DD}.docx with source inventory, evidence status, impact/exploitability rationale, prioritized queue, approval gates, and verification expectations.
+- Every item is classified as confirmed, credible-but-unconfirmed, insufficient-evidence, out-of-scope, fixed, deferred, or escalated.
+- Production remediation and external disclosure stay blocked until approved.
+
+## Steps
+1. Phase 1: `vulnerability-intake`
+2. Phase 2: `code-surface-confirmation`
+3. Phase 3: `impact-and-exploitability-triage`
+4. Phase 4: `prioritization-and-plan`
+5. Phase 5: `issue-filing-and-fix-recommendation`
+6. Phase 6: `triage-report`
+7. Phase 7: `address-feedback`
+8. Phase 8: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "vulnerability-triage-and-remediation" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/strategy/advisor-interview.md

@@ -0,0 +1,29 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: advisor-interview
+
+## Intent
+Interview one advisor candidate and decide whether to pursue them for the board.
+
+## Outcome
+- **Reviewable deliverable**: A .docx document at `docs/business-development/advisory-board/{candidate-name}-advisor-interview-{YYYY-MM-DD}.docx` with the interview notes, chemistry and value scores, a recommended small test-project, and a pursue / replace decision.
+
+## Steps
+1. Phase 1: `interview-prep`
+2. Phase 2: `conduct-interview`
+3. Phase 3: `score-and-test-project`
+4. Phase 4: `interview-submission`
+5. Phase 5: `address-feedback`
+6. Phase 6: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "advisor-interview" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/strategy/advisory-board-development.md

@@ -0,0 +1,31 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: advisory-board-development
+
+## Intent
+Help a founder find the right advisor candidates for the gaps in their founder-market fit and open warm conversations with them.
+
+## Outcome
+- **Reviewable deliverable**: A .docx document at `docs/business-development/advisory-board/{company-name}-advisor-targets-{YYYY-MM-DD}.docx` with the categorized candidate target list, named connectors, forwardable outreach assets, and outreach status.
+
+> Running the interviews and choosing the board are separate workflows that happen later — see `advisory-board-selection`.
+
+## Steps
+1. Phase 1: `advisor-need-scoping`
+2. Phase 2: `candidate-sourcing`
+3. Phase 3: `connector-mapping-and-outreach`
+4. Phase 4: `advisory-board-submission`
+5. Phase 5: `address-feedback`
+6. Phase 6: `retrospective`
+
+---
+
+> [!IMPORTANT]
+> **For AI Agents:** Do NOT attempt to execute this job based on the Intent/Outcome above.
+> This stub is for discoverability only. The actual job has multiple phases with
+> detailed steps, validation criteria, and required skills.
+>
+> To get full phase-by-phase instructions, call:
+> `get_fraim_job({ job: "advisory-board-development" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.