fraim 2.0.362-next.4 → 2.0.362-next.5

package/dist/registry/scripts/domains/folders.js

@@ -0,0 +1,55 @@
+"use strict";
+var __importDefault = (this && this.__importDefault) || function (mod) {
+    return (mod && mod.__esModule) ? mod : { "default": mod };
+};
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.GLOBAL_RULE_PATHS = void 0;
+exports.isSafeDomainId = isSafeDomainId;
+exports.isSafeRegistryPath = isSafeRegistryPath;
+exports.jobDomainFromRegistryPath = jobDomainFromRegistryPath;
+exports.discoverJobDomains = discoverJobDomains;
+exports.domainRulePath = domainRulePath;
+const node_fs_1 = __importDefault(require("node:fs"));
+const node_path_1 = __importDefault(require("node:path"));
+function isSafeDomainId(domain) {
+    return /^[a-z][a-z-]*$/.test(domain) && !['__proto__', 'constructor', 'prototype'].includes(domain);
+}
+function isSafeRegistryPath(value, kind) {
+    return typeof value === 'string' && new RegExp(`^${kind}/[a-zA-Z0-9_/-]+\\.md$`).test(value)
+        && !value.includes('//') && !value.split('/').some(part => part === '.' || part === '..');
+}
+/** Extract a folder, never a frontmatter declaration, leaf-name alias or employee. */
+function jobDomainFromRegistryPath(path) {
+    if (typeof path !== 'string')
+        return null;
+    const clean = path.replace(/\\/g, '/').replace(/^registry\//, '');
+    if (!isSafeRegistryPath(clean, 'jobs'))
+        return null;
+    const rolePath = /^jobs\/(?:ai-employee|ai-manager|personalized-employee)\//.test(clean);
+    const match = clean.match(rolePath
+        ? /^jobs\/(?:ai-employee|ai-manager|personalized-employee)\/([a-z][a-z-]*)\/[^/]+\.md$/
+        : /^jobs\/([a-z][a-z-]*)\/[^/]+\.md$/);
+    return match && isSafeDomainId(match[1]) ? match[1] : null;
+}
+/** Discover domain names from job folders in a registry, synced home or personalized home. */
+function discoverJobDomains(...roots) {
+    const domains = new Set();
+    for (const root of roots) {
+        for (const relative of ['jobs/ai-employee', 'jobs/ai-manager', 'stubs/jobs/ai-employee', 'stubs/jobs/ai-manager', 'jobs', 'ai-employee/jobs', 'ai-manager/jobs']) {
+            const directory = node_path_1.default.join(root, relative);
+            if (!node_fs_1.default.existsSync(directory))
+                continue;
+            for (const entry of node_fs_1.default.readdirSync(directory, { withFileTypes: true })) {
+                if (entry.isDirectory() && isSafeDomainId(entry.name) && !['ai-employee', 'ai-manager', 'personalized-employee'].includes(entry.name))
+                    domains.add(entry.name);
+            }
+        }
+    }
+    return [...domains].sort();
+}
+exports.GLOBAL_RULE_PATHS = ['rules/constitution.md', 'rules/evidence-cardinality.md'];
+function domainRulePath(domain) {
+    if (!isSafeDomainId(domain))
+        throw new Error('Invalid domain folder');
+    return 'rules/' + domain + '/' + domain + '.md';
+}

package/dist/registry/scripts/learning/entry-authoring.js

@@ -10,23 +10,12 @@ exports.readerWordCount = readerWordCount;
 exports.validateEntry = validateEntry;
 exports.renderEntry = renderEntry;
 exports.isLearningScaffolding = isLearningScaffolding;
-const node_fs_1 = __importDefault(require("node:fs"));
 const node_path_1 = __importDefault(require("node:path"));
-const catalog_1 = require("../domains/catalog");
-// Relative to the shipped helper, never to the job's working directory.
-let catalog = { schemaVersion: 2, mapVersion: 0, domains: {} };
-try {
-    const candidate = JSON.parse(node_fs_1.default.readFileSync(node_path_1.default.join(__dirname, '..', '..', 'domains.json'), 'utf8'));
-    if (candidate?.schemaVersion !== 2 || !candidate.domains || typeof candidate.domains !== 'object' || Array.isArray(candidate.domains))
-        throw new Error('Invalid domain catalog');
-    catalog = candidate;
-}
-catch {
-    console.warn('Learning domain catalog unavailable: restore or sync domains.json beside the installed scripts, then retry domain resolution. Existing source files are preserved.');
-}
-const domainData = (effectiveCatalog) => ({ mapVersion: effectiveCatalog?.mapVersion ?? 0, domains: effectiveCatalog?.schemaVersion === 2 && effectiveCatalog.domains && typeof effectiveCatalog.domains === 'object' && !Array.isArray(effectiveCatalog.domains) ? Object.keys(effectiveCatalog.domains).filter(domain => domain !== 'global' && /^[a-z][a-z-]*$/.test(domain)) : [] });
-function deriveDomain(origins, effectiveCatalog = catalog) {
-    const map = domainData(effectiveCatalog);
+const folders_1 = require("../domains/folders");
+const domains = (0, folders_1.discoverJobDomains)(node_path_1.default.join(__dirname, '../..'));
+const domainData = (effectiveDomains) => ({ mapVersion: 3, domains: effectiveDomains });
+function deriveDomain(origins, effectiveDomains = domains) {
+    const map = domainData(effectiveDomains);
     const unknown = (reason) => ({ status: 'needs-domain', value: null, reason, mapVersion: map.mapVersion });
     if (!origins.length)
         return unknown('No originating job recorded');
@@ -34,9 +23,9 @@ function deriveDomain(origins, effectiveCatalog = catalog) {
     for (const origin of origins) {
         // Current folder identity wins; job declarations are no longer domain authority.
         // Missing provenance is not a connect request and must remain unresolved.
-        const selected = origin.registryPath ? (0, catalog_1.selectCatalogDomain)(effectiveCatalog, origin.registryPath) : null;
-        if (selected?.selection === 'mapped') {
-            decisions.push({ value: selected.domain, basis: 'catalog' });
+        const selected = origin.registryPath ? (0, folders_1.jobDomainFromRegistryPath)(origin.registryPath) : null;
+        if (selected && effectiveDomains.includes(selected)) {
+            decisions.push({ value: selected, basis: 'category' });
             continue;
         }
         return unknown(`No current domain folder for ${origin.name}; retain original provenance for review`);
@@ -46,8 +35,8 @@ function deriveDomain(origins, effectiveCatalog = catalog) {
     return { status: 'resolved', ...decisions[0], mapVersion: map.mapVersion };
 }
 /** Resolve an existing entry without rewriting its source, ID, dates or approval. */
-function storedEntryDomain(content, storageDomain, effectiveCatalog = catalog) {
-    const map = domainData(effectiveCatalog);
+function storedEntryDomain(content, storageDomain, effectiveDomains = domains) {
+    const map = domainData(effectiveDomains);
     const unknown = (reason) => ({ status: 'needs-domain', value: null, reason, mapVersion: map.mapVersion });
     const fields = (label) => [...content.matchAll(new RegExp(`^\\*\\*${label}\\*\\*:\\s*([^\\r\\n]+)\\r?$`, 'gm'))].map(match => match[1].trim());
     const domains = fields('Domain');
@@ -63,7 +52,7 @@ function storedEntryDomain(content, storageDomain, effectiveCatalog = catalog) {
     }
     const origins = fields('Originating job').flatMap(value => value.split(';').map(value => value.trim()).filter(Boolean));
     if (origins.length)
-        return deriveDomain(origins.map(registryPath => ({ name: registryPath, registryPath })), effectiveCatalog);
+        return deriveDomain(origins.map(registryPath => ({ name: registryPath, registryPath })), effectiveDomains);
     // Undecorated files contain intentionally global preferences and patterns.
     // An old umbrella filename alone never proves a current domain assignment.
     if (storageDomain === 'global' && (!declared || declared === 'global'))
@@ -71,13 +60,13 @@ function storedEntryDomain(content, storageDomain, effectiveCatalog = catalog) {
     return unknown('Historical entry needs original job provenance or an explicit manager domain decision');
 }
 /** Select entry blocks for one job while retaining provenance in the original text. */
-function selectStoredLearningEntries(content, storageDomain, targetDomain, includeGlobal = true, effectiveCatalog = catalog) {
+function selectStoredLearningEntries(content, storageDomain, targetDomain, includeGlobal = true, effectiveDomains = domains) {
     const headings = [...content.matchAll(/^#{2,6}\s+\[(?:P-)?(?:CRITICAL|HIGH|MED|MEDIUM|LOW|IMPORTANT|MONITOR)\].*$/gm)];
     const blocks = headings.length ? headings.map((heading, index) => content.slice(heading.index, headings[index + 1]?.index ?? content.length).trim()) : [content.trim()].filter(Boolean);
     const entries = [];
     let unresolved = 0;
     for (const block of blocks) {
-        const decision = storedEntryDomain(block, storageDomain, effectiveCatalog);
+        const decision = storedEntryDomain(block, storageDomain, effectiveDomains);
         if (decision.status === 'needs-domain')
             unresolved++;
         else if (decision.value === targetDomain || (includeGlobal && decision.value === 'global'))

package/dist/registry/scripts/learning/run-publication.js

@@ -397,7 +397,7 @@ async function verifyCapabilityDelivery(action, input, options) {
             // publishes supporting edits under the target rule's approval.
             const registryFile = node_path_1.default.join(options.projectPath, 'registry', normalized);
             if (!node_fs_1.default.existsSync(registryFile) || !sameDeliveryText(node_fs_1.default.readFileSync(registryFile, 'utf8'), resolved.content)) {
-                sharedCatalogAvailable = false;
+                sharedSourcesAvailable = false;
             }
             else {
                 snapshot(registryFile, resolved.content);
@@ -417,43 +417,18 @@ async function verifyCapabilityDelivery(action, input, options) {
     let reachable = true;
     const sharedCallers = [];
     const supportingPublications = new Map();
-    let sharedCatalogAvailable = true;
+    let sharedSourcesAvailable = true;
     const captureRuleSelection = (callerPath) => {
         const paths = load('core/utils/project-fraim-paths');
         const workspace = paths.getWorkspaceFraimPath(options.projectPath);
         const user = paths.getUserFraimDirPath();
         snapshot(node_path_1.default.join(workspace, 'config.json'));
         snapshot(node_path_1.default.join(user, 'config.json'));
-        const machineCatalog = node_path_1.default.join(user, 'domains.json');
-        const workspaceCatalog = node_path_1.default.join(workspace, 'domains.json');
-        const registryCatalog = node_path_1.default.join(options.projectPath, 'registry/domains.json');
-        const syncedCatalog = node_fs_1.default.existsSync(machineCatalog) ? machineCatalog : workspaceCatalog;
-        const baselineCatalog = node_fs_1.default.existsSync(syncedCatalog) ? syncedCatalog : registryCatalog;
-        for (const file of [machineCatalog, workspaceCatalog, registryCatalog])
-            snapshot(file);
         for (const [level, root] of [['Project', node_path_1.default.join(workspace, 'personalized-employee')], ['Manager', manager.contentRoot], ['Org', org.contentRoot]]) {
-            const file = node_path_1.default.join(root, 'domains.json');
-            snapshot(file);
-            if (node_fs_1.default.existsSync(file)) {
-                const sourceHome = (0, owner_identity_1.resolveOwnerHome)(options.projectPath, level, { runtimeModule: options.runtimeModule });
-                if (sourceHome.requiresPublish)
-                    supportingPublications.set(file, sourceHome);
-                if (shared && level === 'Project')
-                    sharedCallers.push({ file, expectedHash: snapshots.get(node_path_1.default.resolve(file)).sha256 });
-            }
             // An override created after verification must invalidate the proof.
             snapshot(node_path_1.default.join(root, targetPath));
             snapshot(node_path_1.default.join(root, callerPath));
         }
-        if (shared) {
-            // An installed catalog alone cannot prove that the shared selection
-            // shipped in the reviewed repository revision and current remote HEAD.
-            if (!node_fs_1.default.existsSync(registryCatalog) || !node_fs_1.default.existsSync(baselineCatalog)
-                || !sameDeliveryText(node_fs_1.default.readFileSync(registryCatalog, 'utf8'), node_fs_1.default.readFileSync(baselineCatalog, 'utf8')))
-                sharedCatalogAvailable = false;
-            else
-                sharedCallers.push({ file: registryCatalog, expectedHash: snapshots.get(node_path_1.default.resolve(registryCatalog)).sha256 });
-        }
     };
     for (const caller of input.callers) {
         const callerHome = options.resolveHome(caller.owner);
@@ -535,13 +510,13 @@ async function verifyCapabilityDelivery(action, input, options) {
         }
     };
     verifySnapshots();
-    if (!sharedCatalogAvailable)
+    if (!sharedSourcesAvailable)
         return { published: false, reference: target, contentHash, reachable, localFiles, ...reviewEvidence };
     for (const [file, sourceHome] of supportingPublications) {
         if (!options.runtimeModulePath)
             throw new Error('capability-publication-required');
-        // Rule approval never authorizes publishing supporting catalog or rule edits.
-        const supporting = publishRunFile(options.projectPath, file, sourceHome, input.operationKey || 'catalog-delivery-check', snapshots.get(node_path_1.default.resolve(file)).sha256, options.runtimeModulePath, undefined, true);
+        // Rule approval never authorizes publishing supporting rule edits.
+        const supporting = publishRunFile(options.projectPath, file, sourceHome, input.operationKey || 'rule-delivery-check', snapshots.get(node_path_1.default.resolve(file)).sha256, options.runtimeModulePath, undefined, true);
         verifySnapshots();
         if (!supporting.published)
             return { ...supporting, contentHash, reachable, localFiles, ...reviewEvidence };

package/dist/registry/stubs/jobs/ai-employee/ai-engineering/aeo-optimization.md

@@ -0,0 +1,43 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: aeo-optimization
+
+## Intent
+Implement verified answer-engine optimization improvements with reusable website source, truthful metadata, regression checks, and comparable deployed results.
+
+## Outcome
+- Tested, reviewable website changes addressing verified AEO findings.
+- Evidence connects each change to its source, built artifact, tests and reviewed revision.
+- After authorized delivery, a deployed-page check and comparable rescan, or an explicit pending measurement record when deployment or provider access is unavailable.
+
+## Steps
+<!-- The discovery stub's phase tracker reads this list; phase bodies and routing are inherited above. -->
+1. Phase 1: `implement-scoping`
+2. Phase 2: `aeo-baseline`
+3. Phase 3: `implement-repro` (bugs only)
+4. Phase 4: `implement-tests`
+5. Phase 5: `aeo-source-plan`
+6. Phase 6: `implement-code`
+7. Phase 7: `implement-validate`
+8. Phase 8: `aeo-artifact-validation`
+9. Phase 9: `implement-security-review`
+10. Phase 10: `implement-regression`
+11. Phase 11: `implement-quality`
+12. Phase 12: `implement-completeness-review`
+13. Phase 13: `implement-architecture-update`
+14. Phase 14: `implement-submission`
+15. Phase 15: `address-feedback`
+16. Phase 16: `retrospective`
+17. Phase 17: `aeo-rescan`
+
+---
+
+> [!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: "aeo-optimization" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/ai-engineering/author-ai-evals.md

@@ -0,0 +1,33 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: author-ai-evals
+
+## Intent
+Author a runner-compatible evaluation suite for an AI agent or model, with dataset provenance, metric definitions, approval-evidenced thresholds, and an executed baseline result.
+
+## Outcome
+- **Eval Suite**: A committed, runner-compatible eval configuration covering task completion, tool use, hallucination, and safety dimensions.
+- **Dataset Manifest**: Provenance, version, retention category, and purpose-limitation for every dataset used.
+- **Thresholds**: Metric thresholds backed by explicit evidence or flagged as open decisions requiring product owner approval.
+- **Baseline Result**: An executed run captured via the repository's eval runner, not compilation alone.
+
+## Steps
+1. Phase 1: `eval-scoping`
+2. Phase 2: `eval-authoring`
+3. Phase 3: `eval-execution`
+4. Phase 4: `eval-ci-integration`
+5. Phase 5: `eval-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: "author-ai-evals" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/ai-engineering/create-ai-agent.md

@@ -0,0 +1,33 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: create-ai-agent
+
+## Intent
+Design, configure, and deploy a production AI agent for a named use case and platform, with explicit tool permissions, knowledge configuration, and validation evidence.
+
+## Outcome
+- **Agent Definition**: Instructions, persona, and behavioral guardrails committed to the repository.
+- **Platform Deployment Package**: Platform-specific configuration and deployment artifact.
+- **Tool and Knowledge Configuration**: Explicit tool allowlist and knowledge source manifest.
+- **Validation Evidence**: Tested against intended use cases with a walkthrough record.
+
+## Steps
+1. Phase 1: `agent-scoping`
+2. Phase 2: `agent-design`
+3. Phase 3: `platform-build`
+4. Phase 4: `agent-validation`
+5. Phase 5: `agent-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: "create-ai-agent" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/ai-engineering/create-hub-configured-agent.md

@@ -0,0 +1,34 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: create-hub-configured-agent
+
+## Intent
+Help a manager turn a local AI-agent account, cloud-credit route, or provider setup into a Hub configured agent. The job asks which underlying agent to use, creates or reuses the smallest launch command needed, registers the profile in Hub, and validates that the profile appears in Hub settings without storing secrets.
+
+## Outcome
+- A Hub configured-agent profile stored in user-level Hub state, normally `~/.fraim/hub-configured-agents.json`.
+- The configured agent appears in Hub settings with `id`, `label`, `baseHostId`, and one canonical `command`: ordered environment assignments or literal sourced setup files, followed by the bare base CLI and supported settings.
+- Stored `setupScript` is unsupported and fails closed. Explicit recovery replaces that one record with a complete canonical command and removes `setupScript`, preserving script arguments, preparation order, persistent account/home, runner and timeout. No automatic conversion or migration-backup path exists.
+- Existing base-CLI env-prefix commands remain valid. User-authored account wrappers and profile functions require migration: extract their preparation without losing account selection. Standard CLI installation shims on prepared PATH remain supported, including CMD files.
+- Validation proves the registered launch command changes the expected CLI-visible environment or config without printing secret values.
+- If an equivalent command/profile already exists, the job performs no duplicate write and reports the existing profile as the outcome.
+
+## Steps
+1. Ask which underlying agent or local CLI the manager wants to configure. Do not restrict the answer to today's built-in examples; use the Hub-supported base agent when one exists, and call out missing Hub support when the chosen agent cannot currently be registered.
+2. **Multi-Agent Request Check**: If the manager's request names more than one base agent/profile in the same message (for example, "configure claude-ios and claude-tpg"), list every named agent back to the manager as `requestedAgents` and confirm the full set before proceeding. Work through `select-base-cli` (steps 3-6 below), `inspect-existing-setup`, `create-local-setup-script`, `register-hub-profile`, and `validate-configured-agent` once per named agent within this same run — do not stop after the first when more were named. If a genuine blocker (missing credentials, missing Hub support, ambiguous identity) stops one agent partway through, record the specific blocker for that agent and continue with the remaining named agents rather than abandoning the whole request.
+3. Ask for the user-visible label and stable id. If omitted, derive an id from the label using lowercase kebab case.
+4. Ask whether this profile should use cloud credits, a different endpoint, a different account/subscription, a provider route, or an existing local setup script. Capture only the non-secret intent and paths.
+5. Infer the setup approach from the manager's answer and local evidence. Common examples include profile/config routing, alternate account setup, an existing script, or cloud-credit/provider routing artifacts already present on the machine.
+6. If the requested setup depends on missing provider credentials, endpoint access, or model access, stop with the missing prerequisite rather than creating a partial or fake configuration.
+
+---
+
+> [!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: "create-hub-configured-agent" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/ai-engineering/enable-web-mcp.md

@@ -0,0 +1,33 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: enable-web-mcp
+
+## Intent
+Make an existing web product's approved capabilities available through MCP, covering transport, authentication, least-privilege tool selection, validation, and client connection instructions.
+
+## Outcome
+- **MCP Server**: A running MCP server exposing the approved capabilities as validated tools.
+- **Authentication**: Secure authentication wired at the server level using the product's existing auth mechanism.
+- **Tool Manifest**: A documented tool catalog with Zod schemas, descriptions, and example responses.
+- **Client Connection Instructions**: Verified connection instructions for target AI clients (Claude, Cursor, GitHub Copilot, etc.).
+
+## Steps
+1. Phase 1: `mcp-discovery`
+2. Phase 2: `mcp-design`
+3. Phase 3: `mcp-implementation`
+4. Phase 4: `mcp-validation`
+5. Phase 5: `mcp-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: "enable-web-mcp" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/ai-engineering/evaluate-ai-agent.md

@@ -0,0 +1,32 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: evaluate-ai-agent
+
+## Intent
+Evaluate an existing AI agent for task completion, tool use, hallucination, safety, and regressions using the target platform's supported evaluation interface or the repository's existing eval harness.
+
+## Outcome
+- **Evaluation Report**: Per-case results with each result linked to its evaluator, dataset version, run timestamp, and trace/evidence location.
+- **Aggregate Metrics**: Pass rates and metric scores for each evaluation dimension.
+- **Regression Assessment**: Comparison against prior baseline where a baseline exists.
+- **Deployment Recommendation**: Pass, hold, or conditional verdict with explicit evidence.
+
+## Steps
+1. Phase 1: `eval-setup`
+2. Phase 2: `eval-run`
+3. Phase 3: `eval-analysis`
+4. Phase 4: `eval-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: "evaluate-ai-agent" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/ai-engineering/mcp-server-creation.md

@@ -0,0 +1,35 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: mcp-server-creation
+
+## Intent
+Create an MCP (Model Context Protocol) server that wraps an application's existing REST API as AI-callable tools, enabling AI agents to interact with the application programmatically.
+
+## Outcome
+- **Functional MCP Server**: A running MCP server exposing application APIs as tools with proper Zod schema validation.
+- **Authentication**: Secure API key or token-based authentication wrapping all tool calls.
+- **Documentation**: Tool catalog with descriptions, input/output schemas, and usage examples.
+
+## Steps
+1. Phase 1: `api-discovery`
+2. Phase 2: `server-scaffolding`
+3. Phase 3: `tool-definition`
+4. Phase 4: `authentication-setup`
+5. Phase 5: `build-and-test`
+6. Phase 6: `documentation`
+7. Phase 7: `code-change-gate`
+8. Phase 8: `mcp-server-submission`
+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: "mcp-server-creation" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/ai-engineering/publish-mcp-app.md

@@ -0,0 +1,28 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: publish-mcp-app
+
+## Intent
+Publish and distribute a Model Context Protocol (MCP) server application to major AI marketplaces and app stores (like ChatGPT and Claude).
+
+## Outcome
+- The MCP app is successfully submitted for approval to all targeted platforms.
+- A status report detailing the submission state, verification challenges, and expected wait times.
+
+## Steps
+1. Phase 1: `verify-assets`
+2. Phase 2: `publishing-review`
+3. Phase 3: `execute-publishing`
+4. Phase 4: `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: "publish-mcp-app" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/bank-compliance/banking-evidence-audit.md

@@ -0,0 +1,32 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: banking-evidence-audit
+
+## Intent
+Audit a banking or KYC evidence package for source lineage, missing records, exception handling, and reviewer readiness.
+
+## Outcome
+- **Reviewable deliverable**: A human-readable audit report at `docs/banking/{case-id}/{case-id}-{YYYY-MM-DD}-audit-report.docx`.
+- Evidence map tying each requirement to source artifact, evidence id, owner, and time period.
+- Exception report for missing, stale, contradictory, unverifiable, or redacted evidence.
+- Reviewer handoff with recommendation; blocking gaps prevent a pass conclusion.
+
+## Steps
+1. Phase 1: `audit-scope`
+2. Phase 2: `evidence-review`
+3. Phase 3: `exception-analysis`
+4. Phase 4: `audit-decision`
+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: "banking-evidence-audit" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/bank-operations/kyc-case-review.md

@@ -0,0 +1,32 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+
+# FRAIM Job: kyc-case-review
+
+## Intent
+Prepare a banking KYC case review package from supplied evidence, preserving unresolved checks and routing final approval to an authorized reviewer.
+
+## Outcome
+- **Reviewable deliverable**: A human-readable KYC review artifact at `docs/banking/{case-id}/{case-id}-{YYYY-MM-DD}-kyc-review.docx`.
+- **KYC recommendation**: A clear review posture such as `ready_for_reviewer`, `needs_human_review`, or `blocked_by_missing_evidence`, with reasons.
+- **Evidence pack**: A readable Word artifact tying the recommendation to evidence ids, source notes, observations, and a receipt.
+- **Audit handoff**: Stable artifact paths that `banking-evidence-audit` can consume later.
+
+## Steps
+1. Phase 1: `case-intake`
+2. Phase 2: `evidence-collection`
+3. Phase 3: `kyc-decision`
+4. Phase 4: `evidence-package`
+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: "kyc-case-review" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/career/career-networking.md

@@ -0,0 +1,46 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+---
+{
+  "name": "career-networking",
+  "displayName": "Networking Plan"
+}
+---
+
+# FRAIM Job: career-networking
+
+## Intent
+Build and operate a systematic networking strategy: who to contact, when to contact them, how to personalize outreach, and how to turn warm-path intelligence into real application leverage.
+
+## Outcome
+- A `Networking Plan` DOCX at `docs/career/{slug}-career-networking-{YYYY-MM-DD}.docx`
+- Canonical markdown source at `docs/career/{slug}-career-networking-{YYYY-MM-DD}.md`, generated before the DOCX export
+- >=3 connection tiers per target company: Tier 1 (hiring managers), Tier 2 (employees), Tier 3 (thought leaders)
+- Warm connection path research for Tier 1 and Tier 2 contacts
+- Personalized outreach message templates per tier (<=5 sentences, specific to recipient background)
+- Networking calendar covering >=3 weeks with outreach and follow-up timing
+- Status tracker for each target contact
+- Role-linked recommendations about whether to network before applying, after applying, or instead of applying
+- All LinkedIn write actions (connection requests, messages) performed browser-based via existing skills, as a post-approval action after the manager approves the plan
+
+## Steps
+1. Phase 1: `gather-networking-context`
+2. Phase 2: `map-target-strategy`
+3. Phase 3: `identify-and-score-contacts`
+4. Phase 4: `draft-outreach-messages`
+5. Phase 5: `plan-public-engagement`
+6. Phase 6: `assemble-networking-plan`
+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: "career-networking" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.

package/dist/registry/stubs/jobs/ai-employee/career/career-spec.md

@@ -0,0 +1,41 @@
+<!-- FRAIM_DISCOVERY_STUB -->
+---
+{
+  "name": "career-spec",
+  "displayName": "Career Strategy"
+}
+---
+
+# FRAIM Job: career-spec
+
+## Intent
+Build a plain-language Career Strategy that helps the user understand where they fit best, what proof they already have, what gaps to close, and which CAREEna job to run next.
+
+## Outcome
+- A `Career Strategy` DOCX at `docs/career/{slug}-career-spec-{YYYY-MM-DD}.docx` using `get_fraim_file({ path: "templates/career/CAREER-STRATEGY-TEMPLATE.md" })`, marked `PERSONAL - CAREER CONFIDENTIAL`
+- Canonical markdown source at `docs/career/{slug}-career-spec-{YYYY-MM-DD}.md`, generated before the DOCX export
+- Customer analysis for hiring companies, family/dependents, and the user
+- Value proposition assessment in plain language, backed by evidence from the user's history
+- Target segment recommendation: company stage, size, industry, and role type
+- Gap analysis and next actions framed as specific steps to close, not permanent deficits
+- Recommended CAREEna path that names the next 1-3 jobs to run based on the user's situation
+
+## Steps
+1. Phase 1: `gather-career-context`
+2. Phase 2: `analyze-customers`
+3. Phase 3: `synthesize-positioning`
+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: "career-spec" })`
+>
+> Then follow all phases using `seekMentoring` at each phase transition.