OpenWOP registry
Canonical signed node-pack registry for the openwop workflow orchestration protocol.
117packs published
160versions total
Ed25519signing algorithm
Catalog
Node packs ship reusable workflow building blocks — typed input/output handlers, control nodes (flow / branching / approval gates), and integrations (HTTP, storage, MCP). Authors drop them into the canvas at edit time; hosts load and verify them at runtime. See the node-packs.md spec for the manifest contract and the SRI + Ed25519 trust model. Mixed packs that also ship agents are flagged + agent.
| Name | Version | Nodes | Description | License | Artifacts |
|---|---|---|---|---|---|
community.openwop-team.demo + agent |
0.1.0 | 1 | First community-namespace demo pack. Mixed pack — one trivial node (`uppercase`) plus one agent (`greeter`) — exercising both extension paths in a single tarball under the open-publish `community.*` tier. Manual Ed25519 signed (not Sigstore) to demonstrate the non-OIDC publishing path documented in registry-operations.md §Step 2. MIT-licensed for SPDX-diversity with the Apache-2.0 core packs. | MIT | manifest · tgz · sig |
core.openwop.a2a |
1.1.0 | 17 | Full A2A (Agent-to-Agent) primitives. Client-side: 12 nodes (discover, send, stream, list/get/cancel tasks, resubscribe, multi-turn coordinator, push-config CRUD). Server-side: workflow IS an A2A agent (server-trigger, agent-card-publish, emit-status, emit-artifact, push-send). Routes through ctx.a2a.* host surface. Tracks spec/v1/a2a-integration.md. | Apache-2.0 | manifest · tgz · sig |
core.openwop.agents |
1.0.1 | 12 | Agent composition primitives. Root agent.run + sub-nodes (tools, memory, parsers, model selector). Composes via expansion semantics and consumes host.aiProviders + host.agentRuntime. | Apache-2.0 | manifest · tgz · sig |
core.openwop.ai |
1.1.3 | 15 | Spec-canonical AI-call pack. v1.0 (chatCompletion, structuredOutput, toolCalling, embeddings) plus v1.1 multi-modal + LLM helpers — image generate/edit/upscale, audio transcribe/synthesize, video generate, rerank, classify, extract, guardrails, transform. Routes through host BYOK aiProviders. | Apache-2.0 | manifest · tgz · sig |
core.openwop.crypto |
1.0.4 | 13 | Pure cryptographic primitives: hashing, HMAC, AEAD encrypt/decrypt, asymmetric sign/verify, JWT mint/verify, TOTP, x509 parse + chain verify. Built on node:crypto (Node 20+). Zero npm deps. Pure with respect to keys passed in via inputs. | Apache-2.0 | manifest · tgz · sig |
core.openwop.data |
1.2.1 | 38 | Spec-canonical data-utility pack. v1.0 baseline (string-case, string-split, array-filter, array-map, object-merge) plus v1.1 additions: string format/regex/encode, array sort/unique/flatten/chunk/zip/reduce, object pick/omit/rename/get-path/set-path, json parse/stringify/schema-validate, jsonpath query, csv parse/stringify, datetime suite, number format/round/clamp, uuid. Zero npm deps (Node 20+). | Apache-2.0 | manifest · tgz · sig |
core.openwop.db |
1.0.0 | 12 | Database adapter primitives — sql, nosql, search, vector. Each gated on its host capability (host.sql, host.nosql, host.searchIndex, host.vectorStore) per. Pack speaks no driver — delegates to ctx.db.*. Parametric SQL only (host enforces). | Apache-2.0 | manifest · tgz · sig |
core.openwop.examples |
1.0.1 | 3 | Spec-canonical examples pack — three minimal nodes (echo, coin-flip, delay-with-progress) that exercise the core node-pack contract end-to-end. Zero npm deps; runs on any Node 20+ host advertising the openwop-node-packs profile. See docs/PACKS-MVP-PLAN.md. | Apache-2.0 | manifest · tgz · sig |
core.openwop.files |
1.0.0 | 19 | File + binary primitives — fs CRUD, base64, mime detection, image / PDF / archive processing, FTP / SFTP / SSH. Capability-gated on host.fs. Hosts MUST enforce sandbox root + path-traversal protection. | Apache-2.0 | manifest · tgz · sig |
core.openwop.flow |
1.1.0 | 29 | Spec-canonical flow-control primitives. 25 nodes covering branching, merging, iteration, aggregation, batching, sorting, deduplication, repetition, suspension, sub-workflow invocation, and Make-style error handlers. Pure or suspending — no external I/O. Zero npm deps. Engine >=1.0.0 <2.0.0. | Apache-2.0 | manifest · tgz · sig |
core.openwop.hitl |
1.0.0 | 3 | Human-in-the-loop primitives. form-request, approval-request, ask-user — each suspends the run via the existing interrupt mechanism. Zero npm deps. | Apache-2.0 | manifest · tgz · sig |
core.openwop.http |
2.0.0 | 23 | HTTP + general transport pack. v2.0: prefers the host-mediated, SSRF-guarded `ctx.http.safeFetch` for all outbound when the host exposes it, falling back to the pack's own `assertPublicUrl` (node:dns) + `globalThis.fetch` otherwise; declares `runtime.requires: ["net.dns","net.outbound"]` for the fallback path. v1.0 baseline: core.openwop.http.fetch (retry, backoff, idempotency). v1.1 additions: openapi-call, GraphQL (query/mutation/subscription), SOAP, gRPC (4 streaming variants), SSE consume, WebSocket client, long-poll, upload (multipart + resumable), download stream, pagination decorators (cursor/offset/link-header), rate-limit-aware retry, circuit breaker, idempotency-key generator, webhook signature verifier (Stripe/GitHub/Slack/raw-hmac). Zero npm deps — Node 20+ fetch/undici; transports requiring native libs delegate to host capabilities. | Apache-2.0 | manifest · tgz · sig |
core.openwop.integration |
1.1.0 | 7 | Integration-layer primitives. v1.0 (email-send, slack-message) plus v1.1 (chat-message-generic, sms-send, voice-call-place, voice-call-tts-greet, notification-push) — provider-neutral cross-cutting integration helpers. | Apache-2.0 | manifest · tgz · sig |
core.openwop.mcp |
1.1.1 | 21 | Spec-canonical MCP (Model Context Protocol) pack. v1.0 four-node client baseline (list-tools, invoke-tool, read-resource, server-status) plus the v1.1 additions: full client-side surface (resources, prompts, completion, logging, ping) AND server-side (workflow IS an MCP server — server-trigger + expose-tool/resource/prompt + handle-sampling/elicitation + provide-roots). Tracks modelcontextprotocol.io 2025-06-18 spec via spec/v1/mcp-integration.md. | Apache-2.0 | manifest · tgz · sig |
core.openwop.messaging |
1.0.0 | 7 | Queue + stream primitives — publish, consume (trigger), ack/nack/dead-letter, stream subscribe/publish. Capability-gated on host.queueBus. Sibling to host.messaging (outbound-egress-only). | Apache-2.0 | manifest · tgz · sig |
core.openwop.obs |
1.0.0 | 7 | Observability emission primitives. Workflows publish logs / metrics / traces / alerts under the canonical openwop.* OTel namespace. Delegates to ctx.observability when the host advertises it, no-ops gracefully otherwise. Zero npm deps. | Apache-2.0 | manifest · tgz · sig |
core.openwop.rag |
1.0.1 | 13 | Retrieval-Augmented-Generation primitives: loaders, splitters, vector ops (thin wrappers over core.openwop.db.vector-*), and retrievers (basic / multi-query / contextual-compression). | Apache-2.0 | manifest · tgz · sig |
core.openwop.skills-bridge + agent |
1.0.0 | 1 | Hybrid pack bridging Anthropic / OpenAI Agent Skills (SKILL.md format, open standard since Dec 2025) to openwop AgentManifests. One converter node + one adapter agent. Positions openwop as the orchestration layer above the Skills standard rather than in competition. | Apache-2.0 | manifest · tgz · sig |
core.openwop.storage |
1.0.0 | 20 | State primitives — kv / table / cache / blob / queue. Each node gated on its specific host capability block (host.kvStorage, host.tableStorage, host.cache, host.blobStorage, host.queue) per RFCs 0015–0019. Pack delegates to ctx.storage.* host surface. Zero npm deps. | Apache-2.0 | manifest · tgz · sig |
core.openwop.triggers |
1.1.0 | 16 | Workflow-trigger pack. Sixteen entry-point shapes — original seven (webhook, schedule, event, envelope, chatMessage, canvas, artifact) plus the v1.1 additions (mailhook, email-imap, form, rss, manual, error, sub-workflow, cron-advanced) and the webhook-response action. Trigger nodes are pass-through executors: they forward `ctx.triggerData` (set by the engine when the trigger fires) to outputs. | Apache-2.0 | manifest · tgz · sig |
core.openwop.web-search |
1.0.0 | 1 | Spec-canonical web-search pack. A single capability-advertised search node that routes through the host's `host.webSearch` adapter (search API + scraping policy + rate-limit + cache layer). When the host does not advertise the surface — as in the OpenWOP demo backend — the node returns a deterministic fixture result so replay determinism holds. This is a PROTOCOL-LAYER node pack (capability-advertised), NOT a host-side exec tool. | Apache-2.0 | manifest · tgz · sig |
vendor.myndhyve.ads-copy-generate |
1.0.0 | 1 | MyndHyve ads.copy.generate — AI-powered multi-variant ad copy generation with per-placement adaptation (truncation to caller-supplied text limits). Routes the AI call through ctx.callAI; replaces the source PlatformSpecRegistry read with caller-supplied inputs.placementTextLimits (resolve upstream from vendor.myndhyve.ads-platforms OR host.adPlatformSpecs). | Apache-2.0 | manifest · tgz · sig |
vendor.myndhyve.ads-creative-validate |
1.0.0 | 1 | MyndHyve ads.creative.validate — full compliance scanner combining built-in policy text rules, placement text-length checks, AND asset-format checks (image/video dimensions, file sizes, durations). Caller supplies placement spec data via inputs (resolve upstream from vendor.myndhyve.ads-platforms OR host.adPlatformSpecs). | Apache-2.0 | manifest · tgz · sig |
vendor.myndhyve.ads-export |
1.0.0 | 1 | MyndHyve ads.export.pack — pure-logic export pack builder. Bundles copy variants + creative assets + tracking links into a structured AdExportPack record (JSON-serializable). Lifted from src/canvas-types/campaign-studio/ads-studio/export/AdExportPackService.ts. No host capabilities required; deterministic. | Apache-2.0 | manifest · tgz · sig |
vendor.myndhyve.ads-image-generate |
1.0.0 | 1 | MyndHyve ads.image.generate — generate ad creative images via the host's ctx.callImageGenerator (host.aiProviders.imageGeneration sub-capability from spec PR #48). Batches N prompts through one host call each, computes per-placement dimensions from caller-supplied placementSpec, applies platform/style/brand-color prompt enhancement, and aggregates safety-filter stats. First consumer of the new sub-capability. | Apache-2.0 | manifest · tgz · sig |
vendor.myndhyve.ads-metrics-import |
1.0.0 | 1 | MyndHyve ads.metrics.import — pure-logic aggregation of ad metric snapshots. Caller supplies snapshots[]; pack filters by platformAdIds + optional platform/dateRange, validates each entry, and computes weighted aggregations (overallCtr / overallCpc / overallRoas / overallConversionRate + per-platform breakdown). Mirrors source AdMetricsService.getAggregatedMetrics math. No host capabilities required. | Apache-2.0 | manifest · tgz · sig |
vendor.myndhyve.ads-platforms |
1.0.0 | 1 | MyndHyve ads.platform.specs — pure-data executor exposing the creative specs for 9 ad platforms (amazon, google, linkedin, meta, pinterest, reddit, snapchat, tiktok, x) across their placements. ~1500 LOC of platform spec data (aspect ratios, text limits, file sizes, format support, CTA presets, safe zones, caption + audio guidance) inlined verbatim from src/canvas-types/campaign-studio/ads-studio/platforms/. No host capabilities required. | Apache-2.0 | manifest · tgz · sig |
vendor.myndhyve.ads-policy |
1.0.0 | 1 | MyndHyve ads.policy.check — built-in policy text-rule scanner. Detects claims (guarantees, income, superlatives), trademark mentions, prohibited content (before/after, deceptive urgency), discriminatory targeting. Caller-supplied placement text-limits + trust-guardrail results for fuller coverage; standalone for text-rule-only checks. | Apache-2.0 | manifest · tgz · sig |
vendor.myndhyve.ads-publish-google |
1.0.0 | 1 | MyndHyve ads.publish.google — publish an ad to Google Ads API v18 (Search + Display). Symmetric companion to ads-publish-meta. Resolves 2 secrets (OAuth + developer-token) via ctx.secrets.resolve, then runs the 4-step publish pipeline (budget → campaign → ad-group → ad) with best-effort REMOVE-rollback. Supports 6 bidding strategies + 6 channel types + responsive_search & responsive_display ad formats. | Apache-2.0 | manifest · tgz · sig |
vendor.myndhyve.ads-publish-meta |
1.0.0 | 1 | MyndHyve ads.publish.meta — publish an ad to Meta Marketing API v21.0 (Facebook/Instagram). First consumer of the secrets.resolveInPack sub-capability (spec PR #52). Resolves OAuth token via ctx.secrets.resolve, then runs the 4-step publish pipeline (creative → campaign → ad set → ad) with best-effort rollback on failure. Validates all 6 Meta enums (objective, status, bidStrategy, billingEvent, targeting flexible-spec, placements) pre-flight. Maps Meta API errors to retryable/non-retryable per spec failure-mode glossary. | Apache-2.0 | manifest · tgz · sig |
vendor.myndhyve.ads-publish-tiktok |
1.0.0 | 1 | MyndHyve ads.publish.tiktok — publish an ad to TikTok Marketing API v1.3. Third + final platform-publish pack of the Stage 5 cohort. Single OAuth secret (Access-Token header, not Bearer); TikTok envelope { code, message, data } where code !== 0 means business error even on HTTP 200; optional image upload by URL before ad creation. 3-step pipeline (campaign → adgroup → ad; no separate budget). No rollback per TikTok API semantics (no hard-delete via this surface); partialState surfaced for manual cleanup. | Apache-2.0 | manifest · tgz · sig |
vendor.myndhyve.ads-studio-core |
1.0.0 | 4 | MyndHyve Ads Studio core — four pure-logic executors lifted from src/canvas-types/campaign-studio/nodes/adsStudioPack/. ads.brief.build (CreativeBriefBuilder), ads.variant.plan (VariantPlanService), ads.video.qa (VideoQAService), ads.winner.synthesize (WinnerSynthesisService). All four executors are deterministic — no host capabilities required beyond the core NodeContext. Marks the Phase A pilot of the canvas-type executor migration per openwop/openwop#11. | Apache-2.0 | manifest · tgz · sig |
vendor.myndhyve.ads-tools |
1.0.0 | 2 | MyndHyve Ads Studio tools — 2 pure-logic executors (ads.brief.extract, ads.tracking.link) lifted from src/canvas-types/campaign-studio/ads-studio/. Both are deterministic — no AI calls, no host capabilities. brief.extract derives an AdBrief from caller-supplied page sections; tracking.link builds UTM-tagged per-platform URLs with click-ID macros. | Apache-2.0 | manifest · tgz · sig |
vendor.myndhyve.ads-video-generate |
1.0.0 | 1 | MyndHyve ads.video.generate — generate ad creative videos via the host's ctx.callVideoGenerator (aiProviders.videoGeneration sub-capability from spec PR #53). Symmetric companion to ads-image-generate but adapted for video (single video per call, host hides async polling internally, typical 30-120s latency). Caller-supplied placementSpec.videoSpec replaces source's PlatformSpecRegistry lookup. | Apache-2.0 | manifest · tgz · sig |
vendor.myndhyve.agent-orchestration |
1.0.0 | 12 | MyndHyve agent-orchestration pack. Six nodes that operate on protocol primitives — spawn, delegate-smart, consensus-vote, message-send, skill-invoke, swarm-execute. Routes through the host's agent runtime (ctx.agentRuntime.*). Inherits suspend mechanics for low-confidence escalation. | Apache-2.0 | manifest · tgz · sig |
vendor.myndhyve.ai |
1.0.0 | 3 | MyndHyve envelope-protocol AI nodes. Distinct from core.openwop.ai (which ships provider-agnostic chat-completion + structured-output + embeddings) — this pack ships MyndHyve-specific nodes that work with typed envelopes (`prd.create`, `theme.create`, etc.) emitted into the workflow's envelope stream, and prompts resolved from MyndHyve's prompt library by ID. | Apache-2.0 | manifest · tgz · sig |
vendor.myndhyve.app-builder |
1.0.0 | 2 | MyndHyve App Builder typeIds — app-builder.per-screen (single-task screen generation: chat-send → typed-envelope-await with bounded retry) + app-builder.iterate-tasks (multi-task serial loop over feature tasks with task-level failure isolation). Both consume host.chat + host.aiEnvelope.await. Host concerns (progress cards, telemetry, pilot materializer) intentionally NOT in pack — pack returns categorized task results that host MAY render however it wishes. | Apache-2.0 | manifest · tgz · sig |
vendor.myndhyve.brand |
1.1.0 | 14 | MyndHyve brand-workflow pack. 14 nodes — 8 theme (analyze/discovery/generate/implement/publish/review/templates/validate) + 6 persona (discover/generate/keywordStrategy/publish/review/validate). Each is an AI-driven envelope-emitting node anchored on the brand canvas type. Routes through ctx.brand.* + ctx.aiEnvelope.generate. | Apache-2.0 | manifest · tgz · sig |
vendor.myndhyve.campaign-sequence |
1.0.0 | 3 | MyndHyve campaign-sequence step executors — three pure-control nodes (wait, tag, condition) lifted from src/canvas-types/campaign-studio/sequences/sequenceStepModules.ts. Self-contained: only ctx.inputs + ctx.log; no host capabilities required beyond core NodeContext. The integration siblings (email, sms, webhook) ship in a follow-up pack once openwop NodeContext extensions for host.email / host.sms / host.http land. | Apache-2.0 | manifest · tgz · sig |
vendor.myndhyve.campaign-sequence-integration |
1.0.1 | 3 | MyndHyve campaign-sequence integration nodes — email, sms, webhook. Companion pack to vendor.myndhyve.campaign-sequence (which carries the 3 pure-control nodes). Declares `host.campaignMessaging` peerDependency for the email + sms surface (matching MyndHyve's EmailSMSAdapterService shape); webhook is self-contained via Node 20 fetch + bundled HMAC signature. | Apache-2.0 | manifest · tgz · sig |
vendor.myndhyve.canvas |
1.0.0 | 4 | First vendor-namespace pack. Ships MyndHyve canvas-coordination nodes — canvasRead / canvasWrite / canvasCreate / crossCanvasInvoke — preserving the `core.coordination.*` typeIds in the wild (typeId-preserve strategy from the migration plan §4). The pack itself is MyndHyve-internal: hosts that don't advertise `host.canvas: supported` cannot register it. | Apache-2.0 | manifest · tgz · sig |
vendor.myndhyve.chat |
1.0.0 | 6 | MyndHyve chat-bridge nodes — sendMessage, progressCard, updateCard, phaseInputGate, approvalGate, clarificationGate. Routes through the host's chat adapter (ctx.chat.*) + ctx.suspend for HITL gates. Preserves the core.chat.* typeIds in the wild. | Apache-2.0 | manifest · tgz · sig |
vendor.myndhyve.data-integration |
1.0.0 | 8 | MyndHyve data-integration pack. 7 nodes for fetching from typed data sources (REST / GraphQL / A2A / MCP), transforming results, applying bindings to UI templates, and managing run-scoped variables. Routes through ctx.dataIntegration.* host adapter. | Apache-2.0 | manifest · tgz · sig |
vendor.myndhyve.entities |
1.0.0 | 5 | MyndHyve entities + validation + asset-decision + messaging primitives. 5 nodes covering project creation, cross-stage validation (deterministic, no LLM), workspace asset decision gates (brand / persona / KB), and chat send/reply via the messaging connector layer. | Apache-2.0 | manifest · tgz · sig |
vendor.myndhyve.kanban |
1.0.0 | 7 | MyndHyve kanban-coordination pack. 7 nodes covering board lifecycle, task management (assign + AI-powered decompose), timeline planning, automation rules, and resource monitoring. Routes through ctx.kanban.* host adapter. | Apache-2.0 | manifest · tgz · sig |
vendor.myndhyve.knowledge-tools |
1.0.0 | 2 | MyndHyve knowledge-tools — first reference consumer of the v1 host.knowledge surface. Two typeIds: (1) knowledge.retrieve — thin pass-through over ctx.knowledge.retrieve with optional score-floor filtering; (2) knowledge.augment-prompt — composition primitive that retrieves + renders a Sources block + builds an augmented user message + emits a citation list. Host advertises host.knowledge: supported per spec/v1/host-capabilities.md §host.knowledge. | Apache-2.0 | manifest · tgz · sig |
vendor.myndhyve.landing-page |
1.0.0 | 7 | MyndHyve landing-page executors — 7 nodes (landing.{content.generate, structure.create, variants.generate, theme.apply, tracking.setup, page.validate, page.publish}). Lifted from src/canvas-types/campaign-studio/nodes/pageBuilder/. Two AI-call sites (content.generate, variants.generate) route through ctx.callAI; the original useDesignSystemStore + useIntegrationStore reads are replaced with input-passthrough — the workflow author resolves design tokens + tracking integrations upstream and feeds them into the executor. | Apache-2.0 | manifest · tgz · sig |
vendor.myndhyve.launch-studio |
1.0.0 | 2 | MyndHyve Launch Studio pack. 2 nodes for the LS backbone: link a project to a step + propagate inherited artifact context, and dispatch ready WOP stack items (todo → doing) for a step's canvas type. | Apache-2.0 | manifest · tgz · sig |
vendor.myndhyve.market-intel-ad-angles |
1.0.0 | 1 | MyndHyve market-intel.ad-angles — generates 5-10 ad-angle briefs from VoC research + ICP/product context via one AI call. Each brief carries angleName, segment, corePain, promise, mechanism, proof requirements, objections to handle, 3-5 hook variants, recommended CTA, source quotes, and a 5-dimension score (volume / intensity / commercialIntent / clarity / uniqueness + weighted total). Briefs are sorted by total score descending. Second marketIntel pack of the Stage 5 cohort. | Apache-2.0 | manifest · tgz · sig |
vendor.myndhyve.market-intel-audience-targeting |
1.0.0 | 1 | MyndHyve market-intel.audience-targeting — generate per-platform paid-media targeting packs (interests + keywords + community placements + audience definitions) for 6 ad platforms (meta / google / linkedin / tiktok / reddit / x) from market-research data (communities + angles). One AI call. Outputs cross-platform insights + testing sequence (phased) + budget allocation. Seventh marketIntel pack of the Stage 5 cohort. | Apache-2.0 | manifest · tgz · sig |
vendor.myndhyve.market-intel-community-rank |
1.0.0 | 1 | MyndHyve market-intel.community-rank — rank candidate communities (from a discovery step or connector) by VoC research relevance. Per-community: relevanceScore (0..1) + signalQuality (high/medium/low) + ICP problem alignment + expected intent stages + search strategy + risk factors. Distinct from market-intel.ai-discovery (which generates NEW community suggestions): this pack ranks EXISTING candidates. Ninth marketIntel pack of the Stage 5 cohort. | Apache-2.0 | manifest · tgz · sig |
vendor.myndhyve.market-intel-content-extraction |
1.0.0 | 1 | MyndHyve market-intel.content-extraction — extract structured content from raw HTML via one ctx.callAI. Outputs title, cleaned content, author, publishedAt, contentType, engagement metrics, tags, summary, and relevantQuotes. Sits between host.webResearch.fetchBatch and market-intel.voc-extraction in the canonical pipeline. Fifth marketIntel pack of the Stage 5 cohort. | Apache-2.0 | manifest · tgz · sig |
vendor.myndhyve.market-intel-discovery |
1.0.0 | 1 | MyndHyve market-intel.ai-discovery — AI-powered source-discovery via one ctx.callAI. Given a topic + optional industry/audience/platforms, returns relevant URLs, communities (with platform / relevanceScore / estimatedPostCount), and search queries. Replaces the manual URL-input step of the marketIntel research pipeline. Third marketIntel pack of the Stage 5 cohort. | Apache-2.0 | manifest · tgz · sig |
vendor.myndhyve.market-intel-opportunity-scoring |
1.0.0 | 1 | MyndHyve market-intel.opportunity-scoring — score and rank communities AND messaging angles on a 5-dimension scale (volume / intensity / commercialIntent / clarity / uniqueness, weighted total) given a VoC corpus + community metadata. Composable primitive slotting between voc-extraction (aggregator) and ad-angles (downstream). Source-side this prompt is used inside the market-intel.research orchestrator; published here as a standalone typeId so workflow authors can compose it directly. Fourth marketIntel pack of the Stage 5 cohort. | Apache-2.0 | manifest · tgz · sig |
vendor.myndhyve.market-intel-query-builder |
1.0.0 | 1 | MyndHyve market-intel.query-builder — generate intent-mapped search queries (4-8 query groups × 4 intent stages, 2-4 variations each, synonym maps, platform hints) + per-competitor query packs (comparison/switching/alternative) + topic clusters from ICP + product context. Pairs with ai-discovery: query-builder produces 'what to search for', ai-discovery produces 'where to search'. Eighth marketIntel pack of the Stage 5 cohort. | Apache-2.0 | manifest · tgz · sig |
vendor.myndhyve.market-intel-thread-triage |
1.0.0 | 1 | MyndHyve market-intel.thread-triage — cost-aware pre-filter for VoC extraction. Triages candidate threads into priority tiers (critical/high/medium/low/skip), predicts VoC value + intent stages + tag types, estimates extraction tokens per thread, and builds an extraction queue within token budget. Sits between ai-discovery and voc-extraction in the canonical pipeline. Sixth marketIntel pack of the Stage 5 cohort. | Apache-2.0 | manifest · tgz · sig |
vendor.myndhyve.market-intel-voc |
1.0.0 | 1 | MyndHyve market-intel.voc-extraction — extract Voice of Customer records (verbatim quotes + tagType + intentStage + confidence + rationale) from a single piece of content via a single AI call. First marketIntel pack of the Stage 5 cohort. Schema validation strips invalid records with per-record warnings; output preserves source structure (records + summary + warnings). | Apache-2.0 | manifest · tgz · sig |
vendor.myndhyve.web-research |
1.0.0 | 4 | MyndHyve web-research pack — 4 nodes for the search → fetch → research → synthesize pipeline. webSearch + fetchUrls + researchWeb route through the host's webResearch adapter (search API + scraping policy + rate-limit + cache layer); synthesize composes results into a typed envelope via the AI envelope surface. | Apache-2.0 | manifest · tgz · sig |
vendor.myndhyve.wop-refinement |
1.0.0 | 1 | MyndHyve WOP feature-refinement node — wop.feature.refine. Driven by a `feature.breakdown` LLM envelope; decides whether a stack item is actionable as a node, executable as a chain, must be split into sub-items, needs clarification, or should be blocked. Enforces hard `maxDepth` + `maxGeneratedItems` constraints regardless of LLM proposal. Used by both runner-driven dispatch (StackAutoplayRunner) and chain-driven sub-workflows. | Apache-2.0 | manifest · tgz · sig |
vendor.openwop.rust-hello yanked |
1.0.0 | 1 | Reference WASM node pack proving RFC 0008 ABI v1 works end-to-end across an independent toolchain. One node type: vendor.openwop.rust-hello.greet. | Apache-2.0 | manifest · tgz · sig |
Agent packs ship reusable agent personas — each one bundles
a system prompt, a tool allowlist, a memory shape, and handoff schemas. They
are addressed by AgentRef and resolved at run time through the
host's agent runtime, so the same pack can plug into supervisor, ReAct, or
deep-research orchestration patterns. See
RFC 0003 (Active)
for the manifest contract. Mixed packs that also ship nodes are flagged
+ nodes.
| Name | Version | Agents | Description | License | Artifacts |
|---|---|---|---|---|---|
community.openwop-team.demo + nodes |
0.1.0 | 1 | First community-namespace demo pack. Mixed pack — one trivial node (`uppercase`) plus one agent (`greeter`) — exercising both extension paths in a single tarball under the open-publish `community.*` tier. Manual Ed25519 signed (not Sigstore) to demonstrate the non-OIDC publishing path documented in registry-operations.md §Step 2. MIT-licensed for SPDX-diversity with the Apache-2.0 core packs. | MIT | manifest · tgz · sig |
core.openwop.agent-examples |
1.1.0 | 5 | Reference / smoke-fixture agent pack. Exercises every shape on agent-manifest.schema.json: inline systemPrompt, systemPromptRef, conversation memory, scratchpad memory, non-empty toolAllowlist, and handoff.{task,return}SchemaRef. Validates the `agents[]` extension to the pack manifest (per agent-manifest.schema.json +). Vendor-neutral: no model pinned — hosts resolve via their BYOK aiProviders surface. | Apache-2.0 | manifest · tgz · sig |
core.openwop.agents.api-designer |
1.0.0 | 1 | API design agent. Authors OpenAPI 3.1, AsyncAPI 3.0, and JSON Schema 2020-12 documents from natural-language briefs. Pure-agent pack. | Apache-2.0 | manifest · tgz · sig |
core.openwop.agents.audit-summarizer |
1.0.0 | 1 | Audit-trail summarizer agent. Compresses raw audit logs into executive summaries, highlights anomalies, tracks pattern shifts over time via long-term memory. Pure-agent pack. | Apache-2.0 | manifest · tgz · sig |
core.openwop.agents.classifier |
1.0.0 | 1 | Fast classification agent. Caller supplies labels + optional rationale schema; agent picks the best-fit label(s). Stateless, single-shot. Pure-agent pack. | Apache-2.0 | manifest · tgz · sig |
core.openwop.agents.code-reviewer |
1.0.0 | 1 | Code review agent. Reviews diffs or files for correctness, style, security, and design. Diff-aware prompting; cites file:line in findings. Pure-agent pack. | Apache-2.0 | manifest · tgz · sig |
core.openwop.agents.deep-research |
1.0.2 | 1 | Long-horizon research agent. Plans, dispatches sub-investigations, retrieves from RAG + web, writes up findings. Mirrors LangGraph Deep Agents (planner + subagents + filesystem). Pure-agent pack. | Apache-2.0 | manifest · tgz · sig |
core.openwop.agents.devops-crew |
1.0.0 | 3 | DevOps crew. Planner decomposes runbook → executor runs steps via host.fs + host.queueBus + http → verifier confirms desired state. Gated on host fs + queue capabilities. | Apache-2.0 | manifest · tgz · sig |
core.openwop.agents.doc-writer |
1.0.0 | 1 | Technical documentation author. Produces README sections, API docs, architecture notes, and changelogs from source material. RAG-grounded. Pure-agent pack. | Apache-2.0 | manifest · tgz · sig |
core.openwop.agents.document-author |
1.0.0 | 1 | Office-document authoring agent — produces PDF / Word / Excel / PowerPoint deliverables from briefs. Pure-agent pack. | Apache-2.0 | manifest · tgz · sig |
core.openwop.agents.expense-categorizer |
1.0.0 | 1 | Expense categorization agent. Classifies expenses against a policy-defined chart of accounts and flags policy violations. Pure-agent pack. | Apache-2.0 | manifest · tgz · sig |
core.openwop.agents.frontend-designer |
1.0.0 | 1 | Frontend / UI design agent. Produces design-system-aware component specs, page layouts, and Storybook-style mocks from briefs. Mirrors Anthropic's `frontend-design` skill (top-installed in marketplace). | Apache-2.0 | manifest · tgz · sig |
core.openwop.agents.git-author |
1.0.0 | 1 | Git authoring agent — drafts commit messages, PR bodies, release notes, and changelog entries from diffs. Pure-agent pack. | Apache-2.0 | manifest · tgz · sig |
core.openwop.agents.invoice-extractor |
1.0.0 | 1 | Invoice extraction agent. OCR-aware structured extraction of vendor, line items, totals, tax, payment terms from PDF or scanned-image invoices. Pure-agent pack. | Apache-2.0 | manifest · tgz · sig |
core.openwop.agents.long-doc-summarizer |
1.0.0 | 1 | Long-document summarizer using map-reduce. Splits input into chunks, summarizes each, then synthesizes a final summary. Handles documents that exceed any single LLM's context window. Pure-agent pack. | Apache-2.0 | manifest · tgz · sig |
core.openwop.agents.policy-reviewer |
1.0.0 | 1 | Policy reviewer agent. Reads content (docs, emails, ads, code) against a set of policy rules and flags violations with rationale. Pure-agent pack. | Apache-2.0 | manifest · tgz · sig |
core.openwop.agents.react |
1.0.2 | 1 | Canonical ReAct (Reason + Act) loop agent. Pure-agent pack — ships one agent manifest with a configurable toolAllowlist. Composes via dispatch and consumes host.aiProviders + host.agentRuntime. The 'hello world' of openwop agents. | Apache-2.0 | manifest · tgz · sig |
core.openwop.agents.research-crew |
1.0.0 | 4 | Multi-agent research crew. 4 specialists — planner / retriever / critic / writer — bundled into one pack for dispatch via orchestrator. Mirrors CrewAI's sequential/hierarchical crew templates. | Apache-2.0 | manifest · tgz · sig |
core.openwop.agents.sales-coach |
1.0.0 | 1 | Sales Coach agent. Analyzes call transcripts, identifies coaching moments, recommends next steps, and tracks rep development over time via long-term memory. Pure-agent pack. | Apache-2.0 | manifest · tgz · sig |
core.openwop.agents.sdr |
1.0.0 | 1 | Sales Development Representative agent. Researches prospects, drafts outreach (email/LinkedIn/SMS), schedules follow-ups. Persists prospect history to long-term memory. Pure-agent pack. | Apache-2.0 | manifest · tgz · sig |
core.openwop.agents.structured-extractor |
1.0.0 | 1 | Production-grade structured extraction agent. Caller supplies a JSON Schema; agent extracts conforming output with an auto-fix loop on validation failure. Mirrors LangGraph Trustcall. Pure-agent pack. | Apache-2.0 | manifest · tgz · sig |
core.openwop.agents.supervisor |
1.0.2 | 1 | Multi-agent supervisor. Routes user tasks to specialized subagents via dispatch + orchestrator semantics. Mirrors LangGraph Supervisor and CrewAI's hierarchical-process pattern. Pure-agent pack. | Apache-2.0 | manifest · tgz · sig |
core.openwop.agents.support-crew |
1.0.0 | 3 | Support 3-agent crew. Triage → Resolver → Escalator. Single dispatch handles the full ticket lifecycle. | Apache-2.0 | manifest · tgz · sig |
core.openwop.agents.support-resolver |
1.0.0 | 1 | Customer support resolver agent. KB-grounded answers with explicit citation, escalation handoff on low confidence. Pure-agent pack. | Apache-2.0 | manifest · tgz · sig |
core.openwop.agents.support-triage |
1.0.0 | 1 | Customer support triage agent. Categorizes inbound tickets, routes to the right queue, surfaces severity + customer-segment signals. Pure-agent pack. | Apache-2.0 | manifest · tgz · sig |
core.openwop.agents.test-author |
1.0.0 | 1 | Test authoring agent. Generates unit, integration, and e2e tests from source code or specs. Pure-agent pack. | Apache-2.0 | manifest · tgz · sig |
core.openwop.skills-bridge + nodes |
1.0.0 | 1 | Hybrid pack bridging Anthropic / OpenAI Agent Skills (SKILL.md format, open standard since Dec 2025) to openwop AgentManifests. One converter node + one adapter agent. Positions openwop as the orchestration layer above the Skills standard rather than in competition. | Apache-2.0 | manifest · tgz · sig |
Artifact-type packs register typed artifact schemas (a
JSON Schema + export targets) into a host's artifact registry — so workflow
outputs (one-pagers, brand kits, SOWs) are typed, validated, and exportable.
They are declarative: a manifest with kind: "artifact-type"
and an artifactTypes[] array, no runtime. See
RFC 0075
(publishable per RFC 0107).
| Name | Version | Types | Description | License | Artifacts |
|---|---|---|---|---|---|
core.openwop.artifact-types |
1.0.0 | 2 | Example artifact-type pack — proves the kind:'artifact-type' pack tier registers its declared types through the host artifact-type registry (registrationSource:'pack'), advertised under host.artifactTypes and served at /schemas/artifacts/{id}.schema.json. | Apache-2.0 | manifest · tgz · sig |
Connection packs ship portable provider definitions — OAuth /
API-key auth, scopes, and reach (MCP / OpenAPI / integration) — that make a
host's connection registry installable for third-party providers. They are
declarative: a manifest with kind: "connection" and a
provider object, no runtime and no credential material
(enforced). See
RFC 0095
(publishable per RFC 0107).
| Name | Version | Provider | Description | License | Artifacts |
|---|---|---|---|---|---|
| Atlassian | |||||
core.openwop.connections.jira |
1.0.0 | 1 | Jira connection pack — Atlassian OAuth2 (3LO) provider for Jira Cloud. DEPLOY-GATED. Reach is `mcp` against Atlassian's official first-party remote MCP server (the Rovo MCP server, https://mcp.atlassian.com/v1/mcp), which fronts Jira (and Confluence) under the signed-in user's permissions. Carries NO secret; the operator supplies the OAuth client id/secret host-side. | Apache-2.0 | manifest · tgz · sig |
| GitHub | |||||
core.openwop.connections.github |
1.0.0 | 1 | GitHub connection pack — OAuth2 provider definition, reached via the official GitHub MCP server. Demonstrates the openwop-app connection-pack loader: drop this pack in and `github` becomes a resolvable provider. Carries NO secret; the operator supplies the OAuth client id/secret host-side. | Apache-2.0 | manifest · tgz · sig |
| Google-ads | |||||
core.openwop.connections.google-ads |
1.0.0 | 1 | Google Ads connection pack — OAuth2 provider for the Google Ads REST API. Reach is `openapi`: Google Ads has no first-party global MCP server; the manifest declares the global Google OAuth hosts and points at the REST API reference, consumed by the core.openwop.http nodes. Carries NO secret; the operator supplies the OAuth client id/secret + developer token host-side. One of the three ad platforms Campaign Studio syncs (Google / Meta / LinkedIn Ads). | Apache-2.0 | manifest · tgz · sig |
| Google-workspace | |||||
core.openwop.connections.google-workspace |
1.0.0 | 1 | Google Workspace connection pack — OAuth2 PKCE provider for Drive, Calendar, and Gmail via the Google APIs. Registry parity for the reference app's BUILT-IN `google` provider (day-1 UX P10 / C3): the app itself never loads this pack (the builtin wins by id precedence anyway — this pack deliberately uses the distinct id `google-workspace` so OTHER hosts can adopt it without shadowing semantics); it exists so packs.openwop.dev offers a Google productivity-suite connection alongside microsoft365 — previously the registry's only Google entry was google-ads. Read scopes are the day-1 consent; gmail.send / calendar.events are WRITE groups behind a separate re-consent. Carries NO secret; the operator supplies the OAuth client id/secret host-side. | Apache-2.0 | manifest · tgz · sig |
| Linkedin-ads | |||||
core.openwop.connections.linkedin-ads |
1.0.0 | 1 | LinkedIn Ads connection pack — OAuth2 provider for the LinkedIn Marketing API. Reach is `openapi`: the manifest declares the global LinkedIn OAuth hosts and points at the Marketing API reference, consumed by the core.openwop.http nodes. Carries NO secret; the operator supplies the client id/secret host-side. One of the three ad platforms Campaign Studio syncs (Google / Meta / LinkedIn Ads). | Apache-2.0 | manifest · tgz · sig |
| Meta-ads | |||||
core.openwop.connections.meta-ads |
1.0.0 | 1 | Meta (Facebook/Instagram) Ads connection pack — OAuth2 provider for the Meta Marketing API. Reach is `openapi`: the manifest declares the global Meta OAuth hosts and points at the Marketing API reference, consumed by the core.openwop.http nodes. Carries NO secret; the operator supplies the app id/secret host-side. An available provider (the parallel ad platform to google-ads); one of the three ad platforms Campaign Studio syncs. | Apache-2.0 | manifest · tgz · sig |
| Microsoft 365 | |||||
core.openwop.connections.microsoft365 |
1.0.0 | 1 | Microsoft 365 connection pack — OAuth2 provider for Teams, Outlook (Mail/Calendar), and SharePoint via the Microsoft Graph API. DEPLOY-GATED. Reach is `openapi` against the Microsoft Graph OpenAPI surface: Microsoft's first-party remote MCP servers are per-tenant/preview (a tenant-templated URL, not a single global https endpoint the manifest can fix), so a stable Graph OpenAPI path is the honest day-1 reach (capability honesty). Carries NO secret; the operator supplies the OAuth client id/secret host-side. | Apache-2.0 | manifest · tgz · sig |
| Netsuite | |||||
core.openwop.connections.netsuite |
1.0.0 | 1 | Oracle NetSuite connection pack — OAuth2 provider for the NetSuite SuiteTalk REST API (ERP / finance). Reach is `openapi`: NetSuite has no first-party global MCP server, and its REST base + OAuth hosts are PER-ACCOUNT (`https://{account}.suitetalk.api.netsuite.com`), supplied per connection via instanceUrlTemplate (the schema's own NetSuite example). Carries NO secret; the operator supplies the integration/client credentials host-side. Bound by lib.finance.invoice-ap (post to ERP). | Apache-2.0 | manifest · tgz · sig |
| Notion | |||||
core.openwop.connections.notion |
1.0.0 | 1 | Notion connection pack — OAuth2 provider for Notion pages + databases. DEPLOY-GATED. Reach is `mcp` against Notion's official first-party hosted MCP server (https://mcp.notion.com/mcp, Streamable HTTP), which searches/reads/creates/updates workspace content under the connected user's permissions. Notion consent is a static developer-portal capability set rather than per-request OAuth scopes (scopeModel `capabilities`). Carries NO secret; the operator supplies the OAuth client id/secret host-side. | Apache-2.0 | manifest · tgz · sig |
| Salesforce | |||||
core.openwop.connections.salesforce |
1.0.0 | 1 | Salesforce connection pack — OAuth2 (web-server flow) provider for the Salesforce REST API. DEPLOY-GATED. Reach is `openapi`: Salesforce has no single global first-party MCP server (the API lives on a per-org `*.my.salesforce.com` instance host, supplied per connection via instanceUrlTemplate), so a documented OpenAPI/REST surface is the honest day-1 reach. Carries NO secret; the operator supplies the connected-app consumer key/secret host-side. | Apache-2.0 | manifest · tgz · sig |
| Tiktok-ads | |||||
core.openwop.connections.tiktok-ads |
1.0.0 | 1 | TikTok Ads connection pack — OAuth2 provider for the TikTok Business (Marketing) API. Reach is `openapi`: the manifest declares the TikTok business-api OAuth hosts and points at the Marketing API reference. Carries NO secret; the operator supplies the app id/secret host-side. The third ad platform Campaign Studio dispatches to — TikTok authenticates with an `Access-Token` header (not `Authorization: Bearer`), handled host-side by the ads-dispatch adapter. | Apache-2.0 | manifest · tgz · sig |
| Workday | |||||
core.openwop.connections.workday |
1.0.0 | 1 | Workday connection pack — OAuth2 provider for the Workday REST API (HCM / People). DEPLOY-GATED. Reach is `openapi`: Workday has no first-party global MCP server, and its OAuth authorize/token endpoints plus REST base are TENANT-SPECIFIC (`https://{instance}.workday.com/{tenant}/.`), supplied per connection via instanceUrlTemplate. The manifest declares the global https hosts and the per-tenant template; the operator fills the tenant at connection time (capability honesty). Carries NO secret; the operator supplies the API-client id/secret host-side. | Apache-2.0 | manifest · tgz · sig |
Workflow-chain packs ship reusable sub-workflows — a parameterized
DAG of nodes that callers invoke as a single step (and that expands inline at edit
time). They are declarative: a manifest with kind: "workflow-chain"
and a chains[] array, no runtime. See
RFC 0013
(publishable per RFC 0107).
| Name | Version | Chains | Description | License | Artifacts |
|---|---|---|---|---|---|
core.openwop.workflows.approvals |
1.0.0 | 2 | Real-work workflow pack — the Approvals cluster, the single most-used enterprise automation shape (Power Automate's #1 template is a sign-off flow with ~3.35M instantiations): Request Sign-off (an open gate any team member can approve — the zero-config marquee) and Two-Stage Sign-off (an ordered approval chain: stage two is only asked after stage one approves — sequential chains are DAG composition, not a new primitive). Gates support quorum (requiredApprovals), named approvers (approverRefs), and out-of-office delegation (an approver's active delegation lets their delegate act, counted as ONE identity). All tenant values are run parameters (replay-deterministic). | Apache-2.0 | manifest · tgz · sig |
core.openwop.workflows.content |
1.0.0 | 2 | Real-work workflow pack — the Content & Monitoring cluster: watch an RSS/Atom feed for new items and watch any web page for changes, each pairing a schedule trigger with durable seen-state in host KV storage (deterministic per-source key; the first run treats everything as new and seeds the state). NO host RSS poller exists — adding an 'rss' ingestion source to /v1/trigger-subscriptions is wire territory (see) — so these chains ARE the poller: pair each with a Schedule and the scheduler does the polling. Authored over shipped node typeIds (core.trigger.schedule + core.openwop.http.fetch + core.storage.kv-get/kv-set + core.ai.chatCompletion + core.openwop.integration.notification-push). No external sends — digests are in-app notifications, so no approval gate is needed. All tenant values are run parameters (replay-deterministic). | Apache-2.0 | manifest · tgz · sig |
core.openwop.workflows.data-ops |
1.1.0 | 4 | Real-work workflow pack — the Data Ops cluster, the one shape-family the Zapier/n8n and Microsoft canons don't cover (surfaced by the Make/Workato research): collapsing many records into one output (the aggregator canon), one-way movement of records between systems, and content routing (send a record down the right branch). Roll Up, Records → Table, Records → System (one-way upsert behind a human sign-off), and Content Router (route a record to the matching branch by a field predicate — the Make router shape, gated via edge conditions). Uses only shipped, executable nodes (core.flow.aggregate-{numeric,text,table} + core.flow.router + core.ai.chatCompletion + core.chat.approvalGate + core.openwop.http.openapi-call + core.openwop.integration.notification-push). The write is ONE-WAY movement keyed on an external id (re-runs update, never duplicate) behind a human approval — it is NOT a bidirectional sync. All tenant values are run parameters (replay-deterministic). | Apache-2.0 | manifest · tgz · sig |
core.openwop.workflows.devops |
1.0.0 | 4 | Real-work workflow pack — the DevOps cluster: senior-style code review of a diff, changelog/release-notes drafting from a commit log, CI-failure diagnosis from a signature-verified webhook, and a stale-issue gardener over the public GitHub API. All four are ADVISORY — they analyze and notify in-app, never write to your repo or post comments (an authenticated GitHub write path would bind a connection behind an approval gate; deferred until the MCP-reach connection binding has a chain precedent). These chains do not run the Code Reviewer / Git Author AGENTS — those remain chat-drivable via the agents surface; the chains use short chain-local prompts over core.ai.chatCompletion. All tenant values are run parameters (replay-deterministic). | Apache-2.0 | manifest · tgz · sig |
core.openwop.workflows.exec-ops |
1.1.0 | 3 | Real-work workflow pack. The Executive / Chief-of-Staff cluster: Daily Executive Briefing, Meeting Prep & Attendee Dossier, and Board / Investor Update Pack. Reasons with core.ai.chatCompletion over real tenant data (feature.crm / feature.analytics) and, where a workflow touches an external system, binds a connection pack via core.openwop.http.openapi-call (connectionRef) — so a configured connection runs live and an unconfigured one surfaces a connect prompt rather than failing. Every external send is gated by core.chat.approvalGate; the read-only briefing is ungated. All tenant-specific values are run parameters (replay-deterministic). Resolves fully on hosts that ship the feature + http/mcp + chat packs (the OpenWOP reference app); the connection bindings are configured by the operator under Access & data → Connections. | Apache-2.0 | manifest · tgz · sig |
core.openwop.workflows.finance |
1.1.0 | 3 | Real-work workflow pack — the Finance cluster: Invoice → AP Processing, Month-End Close Checklist, and Expense/Budget Approval + anomaly detection. Reasons with core.ai.chatCompletion; recommends ERP actions (validation + posting) provider-agnostically via core.openwop.connectors.erp-action (NetSuite when connected); every posting/reimbursement runs through a threshold core.chat.approvalGate. All tenant-specific values are run parameters (replay-deterministic). Resolves on hosts shipping the http + ai + chat + kb + integration packs. Published under core.openwop.workflows.* (openwop-team key). | Apache-2.0 | manifest · tgz · sig |
core.openwop.workflows.inbox |
1.0.0 | 3 | Real-work workflow pack — the personal-productivity Inbox cluster: triage your own inbox (classify, draft the urgent reply, digest the rest), nudge unanswered threads, and debrief calls into coaching notes. Distinct from core.openwop.workflows.support (a customer-support mailbox with queue routing): these serve YOUR inbox and YOUR calls. Drafting uses core.email.draft — it creates a draft in your mailbox and never sends (the draft is the human gate); the one real send (follow-up nudger) waits on an approval. All tenant values are run parameters (replay-deterministic). | Apache-2.0 | manifest · tgz · sig |
core.openwop.workflows.it-support |
1.2.1 | 1 | Real-work workflow pack — the IT / Support cluster: Incident Triage & Major-Incident Comms. An AI classifier assesses each incident's severity; routine incidents go to a recommended knowledge-base article and a ticket, while major incidents go to human-approved stakeholder updates in Slack — and each incident finishes with a post-incident summary. All tenant values are run parameters (replay-deterministic). Resolves on hosts shipping the kb + http + ai + chat + integration packs. Published under core.openwop.workflows.* (openwop-team key). | Apache-2.0 | manifest · tgz · sig |
core.openwop.workflows.knowledge |
1.0.0 | 3 | Real-work workflow pack — the internal Knowledge cluster: employee policy/HR Q&A grounded in your Knowledge Base, compliance review of documents against your policy corpus, and structured document summarization. Distinct from core.openwop.workflows.support (customer-facing): these serve EMPLOYEES over internal policy collections. Authored entirely over shipped node typeIds (feature.kb.nodes.rag + core.ai.chatCompletion + core.flow.if + core.chat.approvalGate + core.openwop.integration.*). Populate the underlying collections in the Knowledge feature (or via knowledge-sync from Drive/OneDrive/Dropbox/Box) — these chains READ the app KB; they do not build a separate index. Every external send waits on a human approval gate. All tenant values are run parameters (replay-deterministic). | Apache-2.0 | manifest · tgz · sig |
core.openwop.workflows.lighthouse |
1.1.0 | 5 | Real-work workflow pack (follow-on). The five zero-config 'lighthouse' workflows from the catalog — Lead Triage, Account Brief, Renewal & Churn-Risk Digest, RFP Response, and Post-Meeting Follow-up — authored entirely over node typeIds shipped with this host (feature.crm/kb/analytics + core.ai.chatCompletion + core.chat.approvalGate + core.openwop.integration.*). Each rides real tenant data through the feature node packs, reasons with the LLM node, gates every external send behind a human approval, and delivers a usable artifact. Tenant-specific values are RUN PARAMETERS (never hardcoded) so the expansion stays replay-deterministic. Picking one in the builder instantiates a fully-editable, runnable, assignable workflow. | Apache-2.0 | manifest · tgz · sig |
core.openwop.workflows.market-intel |
1.1.0 | 2 | Real-work workflow pack (+). Market-intelligence digest + a SHIFT digest (research the current period, then diff against the prior run via market-intel.shift-detect → an in-voice shift summary) authored entirely over PUBLISHED node packs (vendor.myndhyve.market-intel-* + core.openwop.ai), so they expand + run on any conformant host. Published under the `core.openwop.workflows.*` namespace (openwop-team signing key); the registry adds `signing` at publish time. | Apache-2.0 | manifest · tgz · sig |
core.openwop.workflows.marketing |
1.1.0 | 4 | Real-work workflow pack — the Marketing & Advertising cluster: Full Campaign Launch, Ad Performance Optimization Loop, Content Brief Generator, and Content Repurposing. Reasons with core.ai.chatCompletion over real tenant data (feature.crm / feature.kb / feature.cms / feature.email); reads/optimizes the ad platforms provider-agnostically via the core.openwop.connectors.ad-* capability nodes (Meta or Google, whichever the tenant connected). The optimization loop routes within-guardrail changes to auto-apply and out-of-guardrail changes to a core.chat.approvalGate via a core.flow.if conditional node (open-question resolution: a flow conditional, not a new primitive). Every launch/publish/apply is approval- or guardrail-gated; all tenant values are run parameters (replay-deterministic). Published under core.openwop.workflows.* (openwop-team key). | Apache-2.0 | manifest · tgz · sig |
core.openwop.workflows.people-hr |
1.2.0 | 3 | Real-work workflow pack — the People / HR cluster: Employee Onboarding Orchestrator, Offboarding & Access Revocation, and Leave/PTO Request Routing. Reasons with core.ai.chatCompletion; binds Microsoft 365 via core.openwop.http.openapi-call connectionRef, recommends HRIS actions provider-agnostically via core.openwop.connectors.hris-action (Workday today), and provider-agnostic ticketing (Jira/ServiceNow) via the core.openwop.connectors.ticket-* capability nodes; every account/HRIS mutation and every team-facing send is gated by core.chat.approvalGate. All tenant-specific values are run parameters (replay-deterministic). Resolves on hosts shipping the http + ai + chat + integration packs; connections are configured under Access & data → Connections. Published under core.openwop.workflows.* (openwop-team key). | Apache-2.0 | manifest · tgz · sig |
core.openwop.workflows.research |
1.0.0 | 1 | Real-work workflow pack — the Research cluster: turn a question into a short, cited web brief. Rides the unified web search (core.web.search → the host.webResearch surface): live results when a search key is configured (BYOK secret 'web-search' on the keys page, or the host's OPENWOP_WEBSEARCH_API_KEY), an honest demo placeholder when not — the synthesis says so plainly instead of pretending. For deep, multi-source, long-horizon research use the Deep Research AGENT in chat; this chain is the quick-brief shape. All tenant values are run parameters (replay-deterministic). | Apache-2.0 | manifest · tgz · sig |
core.openwop.workflows.starters |
1.0.0 | 6 | Starter workflow pack — the simple-pipe on-ramp tier: short single-trigger→action recipes (webhook→notify, form→table, schedule→digest, fetch→store) that run in under a minute with zero connections, before you graduate to the AI-agent packs. Trigger-shaped starters begin with a core.trigger.* pass-through entry node: bind them to a live source with a trigger subscription (POST /v1/trigger-subscriptions — webhook, email, or form) or a Schedule; on a manual run the trigger payload is empty, so bind a source to see them shine. External sends stay behind a human approval gate; in-app notifications are direct. All tenant values are run parameters (replay-deterministic). | Apache-2.0 | manifest · tgz · sig |
core.openwop.workflows.support |
1.0.0 | 5 | Real-work workflow pack — the Customer Support cluster, the #1 surveyed agent use case the gallery previously had zero templates for: KB-grounded answering, email triage (draft-only — the human sends), customer-ticket routing, sentiment/brand-risk escalation, and CSAT follow-up. Authored entirely over node typeIds shipped with this host (feature.kb + core.ai.chatCompletion + core.flow.if + core.chat.approvalGate + core.email.draft + core.openwop.connectors.ticket-create + core.openwop.integration.*). Every external SEND waits on a human approval gate (core.email.draft creates a draft and never sends — the draft itself is the human gate). Distinct from core.openwop.workflows.it-support: that pack routes IT incidents by severity; this one serves customer-facing support (intent, queues, CSAT). All tenant values are run parameters (replay-deterministic). | Apache-2.0 | manifest · tgz · sig |
vendor.openwop.workflow-chain-sample |
1.0.0 | 2 | Reference workflow-chain pack proving the manifest format works end-to-end across schema validation, registry indexing, and the reference expansion library. Two chains: a 1-node 'summarize text' chain showing literal parameter substitution, and a 2-node 'fetch-and-summarize' chain showing multi-node DAG composition with edge wiring and capability propagation. In-tree only (NOT published to packs.openwop.dev); the canonical proof that the chain-pack contract is implementable with real-world-shaped content. | Apache-2.0 | manifest · tgz · sig |
Prompt packs ship reusable, versioned prompt templates — named,
parameterized text with model hints — that a host's prompt library resolves at run
time (with the override hierarchy of RFC 0029). They are declarative: a
manifest with kind: "prompt" and a prompts[] array, no runtime. See
RFC 0027
(publishable per RFC 0107).
| Name | Version | Templates | Description | License | Artifacts |
|---|---|---|---|---|---|
vendor.openwop.prompt-sample |
1.0.0 | 2 | Reference prompt pack proving the manifest format works end-to-end across schema validation, registry indexing, and the in-memory PromptStore's installPackTemplates seam. Two templates: a writer-system prompt and a critic-system prompt — the minimal pair that lets a multi-agent workflow author point a `writer` + `critic` node pair at vendor-published prompts via `prompt:writer-system@1.0.0` / `prompt:critic-system@1.0.0` refs. In-tree only (NOT published to packs.openwop.dev); the canonical proof that the prompt-pack contract is implementable with real-world-shaped content. | Apache-2.0 | manifest · tgz · sig |
Card packs ship reusable, prompt-driven AI chat cards — a
typed input form + a prompt template + an output contract — that a host's chat
surface (host.chat.cardPacks) resolves and executes through its AI
envelope. They are declarative: a manifest with kind: "card"
and a cards[] array, no runtime; card-input content is treated as
contentTrust: "untrusted". See
RFC 0071
(publishable per RFC 0107).
| Name | Version | Cards | Description | License | Artifacts |
|---|---|---|---|---|---|
vendor.openwop.card-sample |
1.0.0 | 2 | Reference chat-card pack — two portable, host-agnostic AI chat cards: a text summarizer and a meeting action-item extractor. Demonstrates the card manifest contract (typed inputs from the portable subset, a prompt template with placeholder mapping, no runtime). | Apache-2.0 | manifest · tgz · sig |
Trust & verification
Every tarball is signed with the registry's Ed25519 root key. Hosts running in verified trust mode (per node-packs.md §Trust model) MUST verify each .tgz against this key before unpacking.
/keys/openwop-registry-root.pubroot public key (PEM, Ed25519)
Verification recipe (Node 20+)
const { createPublicKey, verify } = require('node:crypto');
const { readFileSync } = require('node:fs');
const pub = createPublicKey({ key: readFileSync('root.pub'), format: 'pem' });
const ok = verify(null, readFileSync('pack.tgz'), pub, readFileSync('pack.sig'));
// ok === true if the tarball is signed by this registry's root keyAPI
The registry is read-only; programmatic access via the documented endpoints:
/.well-known/openwop-registrydiscovery — declares all endpoint templates/v1/index.jsonfull pack catalog/v1/packs/{name}/index.jsonper-pack metadata + versions list/v1/packs/{name}/-/{version}.jsonversion manifest/v1/packs/{name}/-/{version}.tgzsigned tarball/v1/packs/{name}/-/{version}.sigEd25519 signature
Pack schemas declared with a $id URL of the form https://packs.openwop.dev/{name}/{version}/<schema>.json resolve to the schema content extracted from the signed tarball. The tarball is canonical; the mirrored URL is a derived view — consumers wanting cryptographic integrity should verify against the tarball (see node-packs.md §"Schema $id resolution").
Publishing a pack
Submissions land via maintainer pull request — write API is intentionally not exposed. Build the pack, sign the tarball with your private key, commit alongside the manifest, open a PR. CI validates JSON parsing, sha256 integrity, signature presence, and (in verified mode) signature correctness before merge. The deploy ships on merge to main.
Detailed flow: registry/README.md.
Namespaces
core.*— reserved for the openwop working group; spec-canonical packs only.vendor.<org>.*— under control of a specific vendor organization.community.<author>.*— open-publish; first-claim wins per name.
private.* and local.* namespaces MUST NOT appear in this registry; they're for host-internal and in-repo packs respectively.