fraim 2.0.362-next.4 → 2.0.362

package/dist/registry/stubs/jobs/ai-employee/engineering/mobile-app-development.md

@@ -0,0 +1,43 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: mobile-app-development
+
+## Intent
+Create production-ready mobile applications from concept to store submission, following platform best practices (Apple HIG / Material 3) and store policies (App Store Review Guidelines / Play Store Policies). Single job parameterized by `platform` (`ios`, `android`, or `both` for cross-platform builds) — composes the platform-specific skill set based on a Phase 1 decision.
+
+## Outcome
+- **Production Mobile App**: Fully functional iOS .ipa and/or Android .aab ready for store submission.
+- **Complete Documentation**: Technical, API, and user docs.
+- **Compliance Validation**: Privacy manifest / Data Safety form; AI disclosure; export compliance; accessibility.
+- **Monitoring Setup**: Crash reporting, performance monitoring, analytics.
+- **Artifact Handoff**: Binary path(s), mapping/symbol files, version metadata — symmetric across platforms so the submission job consumes a uniform contract.
+
+## Steps
+1. Phase 1: `platform-selection`
+2. Phase 2: `project-setup`
+3. Phase 3: `architecture-design`
+4. Phase 4: `core-implementation`
+5. Phase 5: `integration-setup`
+6. Phase 6: `performance-optimization`
+7. Phase 7: `compliance-validation`
+8. Phase 8: `observability-setup`
+9. Phase 9: `code-change-gate`
+10. Phase 10: `store-preparation`
+11. Phase 11: `deployment-review`
+12. Phase 12: `deployment`
+13. Phase 13: `monitoring-setup`
+14. Phase 14: `submit`
+15. Phase 15: `address-feedback`
+16. Phase 16: `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: "mobile-app-development" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/engineering/mobile-app-rejection-response.md

@@ -0,0 +1,34 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: mobile-app-rejection-response
+
+## Intent
+Respond to an app store rejection — analyze the cited guideline / policy, gather evidence, draft a Resolution Center / Policy Center reply, post it, and decide next steps (clarify-and-resubmit, ship a fixed binary, or escalate via App Review Board / Play appeal). Single job parameterized by `platform` — composes Apple-specific or Play-specific guidance based on a Phase 1 decision. Reused on every rejection cycle. Triggered from `mobile-app-submission` → `monitor-and-respond` when a rejection is received.
+
+## Outcome
+- **A Posted Reply**: A Resolution Center (iOS) or Policy Center (Android) message responding to the rejection is sent.
+- **A Clear Decision**: One of three paths chosen and acted on: (a) Clarify-and-Resubmit, (b) Ship a Fixed Binary, (c) Escalate (App Review Board / Play appeal).
+- **Audit Trail**: The full rejection thread, evidence collected, and decision rationale captured in `docs/<store>/rejections/<submission-id>.md`.
+
+## Steps
+1. Phase 1: `platform-selection`
+2. Phase 2: `rejection-analysis`
+3. Phase 3: `evidence-gathering`
+4. Phase 4: `response-drafting`
+5. Phase 5: `submit`
+6. Phase 6: `address-feedback`
+7. Phase 7: `post-reply`
+8. Phase 8: `re-evaluate-resubmit-or-appeal`
+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: "mobile-app-rejection-response" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/engineering/mobile-app-submission.md

@@ -0,0 +1,37 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: mobile-app-submission
+
+## Intent
+Submit a mobile binary to the destination app store. Single job parameterized by `platform` — composes the App Store Connect (iOS) or Google Play Console (Android) flow based on a Phase 1 decision. Reused on every release. Covers the store-side end-to-end: metadata, screenshots, privacy disclosures, demo creds (where applicable), reviewer notes, and the actual Submit-for-Review click. Routes any rejection into `mobile-app-rejection-response`.
+
+## Outcome
+- **Submitted Version**: A store version is in `Waiting for Review` / `In Review` / `In review` status with all required fields filled and one binary attached.
+- **Demo-Ready Account** (sign-in apps only): Synthetic reviewer account exists and is seeded with realistic data.
+- **Submission Audit Trail**: A submission ID, build/version code, and complete log of fields filled in the project's evidence dir.
+- **Monitoring Hook**: Either approval is recorded, or the rejection routes into `mobile-app-rejection-response` with full context preserved.
+
+## Steps
+1. Phase 1: `platform-selection`
+2. Phase 2: `policy-preflight`
+3. Phase 3: `metadata-authoring`
+4. Phase 4: `screenshots-and-graphics`
+5. Phase 5: `privacy-disclosure`
+6. Phase 6: `store-specific-fields`
+7. Phase 7: `demo-account-and-review-info`
+8. Phase 8: `submit`
+9. Phase 9: `submit-for-review`
+10. Phase 10: `monitor-and-respond`
+11. Phase 11: `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: "mobile-app-submission" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/engineering/project-scaffolding.md

@@ -0,0 +1,39 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: project-scaffolding
+
+## Intent
+Scaffold a new FRAIM project from 0 to 80% production-ready, setting up test infrastructure, port management, issue filing, MCP connectivity, source organization, and e2e tests. The agent reads reference templates, analyzes the project context, and generates code adapted to the specific project's language, framework, and conventions.
+
+## Outcome
+- A working project scaffold with all core components:
+  - `src/core/utils/git-utils.{ext}` with port management and branch-based database naming
+  - `{project-root}/test-utils.{ext} (in the project's test directory)` with BaseTestCase, tag filtering, and runTests
+  - `src/issues.{ext}` with issue filing endpoint for the project's configured issue tracker
+  - `src/mcp-server.{ext}` with MCP server entry point (/health, /mcp)
+  - `{project-root}/shared-server-utils.{ext} (in the project's test directory)` with e2e helpers (startTestServer, sendMCPRequest, waitForServer)
+  - `e2e/` directory with a sample end-to-end test
+- Generated code adapted to the project's detected language and framework
+- Next-step guidance for deployment or feature building
+
+## Steps
+1. Phase 1: `project-analysis`
+2. Phase 2: `core-infrastructure`
+3. Phase 3: `test-infrastructure`
+4. Phase 4: `server-and-integration`
+5. Phase 5: `validation-and-next-steps`
+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: "project-scaffolding" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/engineering/system-migration.md

@@ -0,0 +1,41 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: system-migration
+
+## Intent
+Migrate an existing system from one stack or boundary to another with explicit baseline capture, one-unit-at-a-time execution, domain-aware parity review, and cutover readiness discipline.
+
+## Outcome
+- `workListPath`: `docs/migration/{issue_number}-migration-{runId}-work-list.md`
+- `migrationReviewPath`: `docs/migration/{issue_number}-migration-{runId}-review.md`
+- Final artifact: `workListPath`
+- Review evidence: `migrationReviewPath`
+- Each migration unit is either completed against an explicit parity contract or left with a documented blocker, deferral, or rollback note
+
+## Steps
+1. Phase 1: `migration-scoping`
+2. Phase 2: `migration-unit-discovery`
+3. Phase 3: `baseline-capture`
+4. Phase 4: `parity-contract-authoring`
+5. Phase 5: `migration-scope-slicing`
+6. Phase 6: `migrate-next-unit`
+7. Phase 7: `parity-review`
+8. Phase 8: `coverage-cross-analysis`
+9. Phase 9: `fix-gaps`
+10. Phase 10: `advance-or-loop`
+11. Phase 11: `cutover-readiness`
+12. Phase 12: `submit`
+13. Phase 13: `address-feedback`
+14. Phase 14: `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: "system-migration" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/engineering/technical-design.md

@@ -0,0 +1,34 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: technical-design
+
+## Intent
+Turn an approved feature spec into a concrete, implementable design before code is written.
+
+## Outcome
+- **Reviewable deliverable**: A markdown RFC at `docs/rfcs/{issue_number}-{slug}-technical-design.md`, with Architecture Overview, Implementation Strategy, Validation Plan, Risk Assessment, and Spike Findings (if applicable).
+- **Validation Plan**: A clear plan for how implementation will be tested.
+- **Spike Findings**: A documented proof-of-concept only when uncertainty is real.
+- **Feedback Resolution**: Confirmation that prior feedback was addressed.
+
+## Steps
+1. Phase 1: `requirements-analysis`
+2. Phase 2: `design-authoring`
+3. Phase 3: `technical-spike` (Conditional)
+4. Phase 4: `architecture-gap-review`
+5. Phase 5: `design-completeness-review`
+6. Phase 6: `design-submission`
+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: "technical-design" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/engineering/work-completion.md

@@ -0,0 +1,29 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: work-completion
+
+## Intent
+Systematically merge completed repository work into the main codebase, verify the default branch, and clean up issue artifacts when appropriate.
+
+## Outcome
+- **Merged Code**: The feature branch is successfully merged into `{{proxy.config.repository.defaultBranch | NO_OP | "main"}}`, or an already-merged PR is confirmed.
+- **Verified Default Branch**: The default branch contains the merge and CI passes after merge.
+- **Closed Issue**: The issue tracker reflects completed status when the selected completion path includes issue closure.
+- **Clean Workspace**: Local/remote feature branches and issue worktrees are deleted only after safety guards pass.
+
+## Steps
+1. Phase 1: `resolution-merge`
+2. Phase 2: `resolution-verification`
+3. Phase 3: `resolution-cleanup`
+
+---
+
+> [!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: "work-completion" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/engineering/write-dev-docs.md

@@ -0,0 +1,32 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: write-dev-docs
+
+## Intent
+Write developer documentation — API references, integration guides, architecture overviews, or onboarding guides — that reduces time-to-first-success for developers and cuts support burden by making answers findable before questions are asked.
+
+## Outcome
+- **Reviewable deliverable**: A markdown documentation artifact at `docs/rfcs/{issue_number}-{slug}-developer-documentation.md`, with comprehensive developer documentation including overview, audience-specific guides, code examples, API references, integration instructions, and troubleshooting.
+- **Doc Plan**: Scope, audience, and structure agreed before writing.
+- **Draft Docs**: Complete documentation matching the agreed plan.
+- **Review**: Technical accuracy verified against source code or system behavior.
+
+## Steps
+1. Phase 1: `doc-planning`
+2. Phase 2: `doc-drafting`
+3. Phase 3: `doc-review`
+4. Phase 4: `dev-docs-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: "write-dev-docs" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/executive-assistance/analyze-transcript.md

@@ -0,0 +1,32 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: analyze-transcript
+
+## Intent
+Turn a raw meeting or session transcript into structured, actionable insights — Items Learned, Actionable Items, and Other Important Notes — ready to act on or route into downstream FRAIM workflows.
+
+## Outcome
+- **Reviewable deliverable**: a .docx review copy generated from the final artifact via the author-docx skill at submission; this is the outcome delivered for review, with the .md below as the canonical agent-side record.
+- Final artifact: `docs/business-ops/transcript-{YYYY-MM-DD}.md`
+- A markdown document with three structured sections approved by the user, grounded entirely in the transcript with no hallucinated owners, deadlines, or facts.
+
+## Steps
+1. Phase 1: `intake-transcript`
+2. Phase 2: `extract-insights`
+3. Phase 3: `validate-output`
+4. Phase 4: `present-for-approval`
+5. Phase 5: `submit`
+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: "analyze-transcript" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/executive-assistance/calendar-triage.md

@@ -0,0 +1,31 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: calendar-triage
+
+## Intent
+Defend the manager's calendar for the week by proposing, per meeting, whether to keep, delegate, decline, reschedule, or replace it with focus time, with every change gated on the manager's confirmation.
+
+## Outcome
+- **Reviewable deliverable**: A .docx document at docs/business-ops/calendar-triage-{YYYY-MM-DD}.docx with a per-event recommendation and a pending action for each proposed change.
+- A triaged week where each meeting carries a recommendation, and each proposed change is a pending HITL action awaiting the manager's approval.
+
+## Steps
+1. Phase 1: `triage-scope`
+2. Phase 2: `gather-connectors`
+3. Phase 3: `propose-changes`
+4. Phase 4: `produce-triage`
+5. Phase 5: `submit`
+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: "calendar-triage" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/executive-assistance/chief-of-staff-briefing.md

@@ -0,0 +1,31 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: chief-of-staff-briefing
+
+## Intent
+Give the manager one daily briefing that answers "what needs me today?" by synthesizing across every connector they have configured (email, calendar, chat), rather than checking each tool separately.
+
+## Outcome
+- **Reviewable deliverable**: A .docx document at docs/business-ops/chief-of-staff-briefing-{YYYY-MM-DD}.docx with the ranked priorities, the calendar strip, and a connector-availability summary.
+- A ranked, source-tagged list of what needs the manager today, plus a calendar view annotated ATTEND / DELEGATE / SKIP.
+
+## Steps
+1. Phase 1: `triage-scope`
+2. Phase 2: `gather-connectors`
+3. Phase 3: `synthesize-brief`
+4. Phase 4: `produce-brief`
+5. Phase 5: `submit`
+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: "chief-of-staff-briefing" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/executive-assistance/executive-assistant.md

@@ -0,0 +1,31 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: executive-assistant
+
+## Intent
+Handle executive-assistant requests by routing live context and requested actions through Ashley MCP without recreating Ashley's data model inside FRAIM.
+
+## Outcome
+- **Reviewable deliverable**: A .docx document at docs/business-ops/executive-assistant-{YYYY-MM-DD}.docx with context availability, briefing summary, action items, and next steps
+- A concise executive-assistant brief or action summary grounded in available Ashley context
+
+## Steps
+1. Phase 1: `triage-request`
+2. Phase 2: `gather-context`
+3. Phase 3: `route-actions`
+4. Phase 4: `produce-brief`
+5. Phase 5: `submit`
+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: "executive-assistant" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/executive-assistance/meeting-preparation.md

@@ -0,0 +1,31 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: meeting-preparation
+
+## Intent
+Prepare the manager for a specific meeting by assembling attendee context, prior-thread history, an agenda, and the decisions they must make, drawn from whatever connectors are configured.
+
+## Outcome
+- **Reviewable deliverable**: A .docx document at docs/business-ops/meeting-prep-{slug}-{YYYY-MM-DD}.docx with attendee context, context since the last meeting, a suggested agenda, decisions needed, and pre-reads.
+- A prep brief specific to one meeting, source-tagged to the connectors that supplied each fact.
+
+## Steps
+1. Phase 1: `identify-meeting`
+2. Phase 2: `gather-connectors`
+3. Phase 3: `assemble-brief`
+4. Phase 4: `produce-prep`
+5. Phase 5: `submit`
+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: "meeting-preparation" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/finance/business-banking-setup.md

@@ -0,0 +1,29 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: business-banking-setup
+
+## Intent
+Get a founder set up with the right business bank account for their company.
+
+## Outcome
+- **Reviewable deliverable**: A .docx document at `docs/company-creation/banking/{company-name}-banking-{YYYY-MM-DD}.docx` with a shortlist + trade-offs, a recommended primary (and backup), and an account-opening checklist.
+
+## Steps
+1. Phase 1: `banking-needs-intake`
+2. Phase 2: `bank-options-research`
+3. Phase 3: `account-setup-checklist`
+4. Phase 4: `banking-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: "business-banking-setup" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/finance/cloud-credits-application.md

@@ -0,0 +1,34 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: cloud-credits-application
+
+## Intent
+Apply for startup cloud credits through one selected provider path: `aws-activate`, `google-cloud`, or `microsoft-azure`.
+
+## Outcome
+- Final artifact: provider application, support ticket, or referral-path submission completed or staged for user approval.
+- Provider-specific status captured for AWS Activate, Google Cloud for Startups, or Microsoft for Startups.
+- Applicant identity, eligibility assumptions, and any manual follow-up requirements documented.
+
+## Steps
+1. Phase 1: `gather-user-info`
+2. Phase 2: `select-provider-path`
+3. Phase 3: `navigate-to-provider`
+4. Phase 4: `sign-in-to-provider`
+5. Phase 5: `fill-application`
+6. Phase 6: `review-application`
+7. Phase 7: `submit-application`
+8. Phase 8: `verify-application-status`
+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: "cloud-credits-application" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/finance/community-funding-preparation.md

@@ -0,0 +1,34 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: community-funding-preparation
+
+## Intent
+Architect a high-impact crowdfunding campaign (Kickstarter, Indiegogo) by engineering sustainable reward tiers, crafting a viral narrative, and auditing logistics risks.
+
+## Outcome
+- **Reviewable deliverable**: A .docx document at docs/fundraising/community-campaign-{YYYY-MM-DD}.docx with campaign blueprint, reward tiers, narrative story arc, logistics risk audit, and ready-to-publish assets.
+- **Economic Safety**: Reward tiers validated against margin requirements.
+- **Viral Narrative**: A story arc designed for community evangelism.
+
+## Steps
+1. Phase 1: `scoping`
+2. Phase 2: `campaign-discovery`
+3. Phase 3: `reward-tier-engineering`
+4. Phase 4: `campaign-story-design`
+5. Phase 5: `logistics-risk-audit`
+6. Phase 6: `campaign-package-assembly`
+7. Phase 7: `campaign-submission`
+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: "community-funding-preparation" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/finance/financial-analysis.md

@@ -0,0 +1,33 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: financial-analysis
+
+## Intent
+Build a linked three-statement financial model that gives founders and CFOs a single source of truth for revenue, burn, and cash position - with scenario modeling and board-ready output.
+
+## Outcome
+- **Reviewable deliverable**: A .pptx presentation at docs/finance/financial-analysis-{YYYY-MM-DD}.pptx containing linked three-statement model with P&L, balance sheet, cash flow statements, ratio analysis dashboard (gross margin, burn multiple, CAC payback, LTV:CAC), and base/bull/bear scenario modeling.
+- **Ratio Analysis**: Gross margin, burn multiple, CAC payback, and LTV:CAC calculated and trended.
+- **Scenario Modeling**: Base, bull, and bear scenarios with key driver sensitivities.
+- **Board Export**: Executive summary with burn runway and inflection points highlighted.
+
+## Steps
+1. Phase 1: `data-gathering`
+2. Phase 2: `three-statement-modeling`
+3. Phase 3: `ratio-analysis`
+4. Phase 4: `recommendations`
+5. Phase 5: `financial-analysis-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: "financial-analysis" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/finance/fpa-and-forecasting.md

@@ -0,0 +1,33 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: fpa-and-forecasting
+
+## Intent
+Build a driver-based financial forecast and annual operating plan that replaces static budget spreadsheets with a living model that updates when business assumptions change.
+
+## Outcome
+- **Reviewable deliverable**: A .pptx presentation at docs/finance/fpa-and-forecasting-{YYYY-MM-DD}.pptx containing driver-based annual operating plan with 4-8 identified drivers, base/bull/bear scenario analysis, department-level budget tables, headcount plan, revenue targets, and board summary.
+- **Driver Model**: 4-8 key business drivers identified and parameterized.
+- **Three Scenarios**: Base, bull, and bear cases with explicit assumption sets.
+- **AOP Summary**: Department-level budget with headcount, OpEx, and revenue targets.
+
+## Steps
+1. Phase 1: `driver-identification`
+2. Phase 2: `model-build`
+3. Phase 3: `scenario-analysis`
+4. Phase 4: `aop-review`
+5. Phase 5: `fpa-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: "fpa-and-forecasting" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/finance/fundraising-prospect-discovery.md

@@ -0,0 +1,33 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: fundraising-prospect-discovery
+
+## Intent
+Systematically identify and prioritize the highest-probability funding sources (VCs, Angels, or Crowdfunding platforms) by analyzing competitor history and investor thesis alignment.
+
+## Outcome
+- **Reviewable deliverable**: A .docx document at docs/fundraising/prospect-hit-list-{YYYY-MM-DD}.docx with prioritized investor prospects, fit scores, reframing advice, and contact mechanisms.
+- **Strategic Clarity**: Direct evidence of who is funding the space and where the "open slots" are.
+- **Entry Points**: Identified contact mechanisms or application portals for each prospect.
+
+## Steps
+1. Phase 1: `scoping`
+2. Phase 2: `market-scan`
+3. Phase 3: `entity-discovery`
+4. Phase 4: `thesis-alignment`
+5. Phase 5: `prospect-delivery`
+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: "fundraising-prospect-discovery" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.