Skip to content
OpenCorvus

Inspect the team before use

Active database publication

Viral Content

Evidence-backed audience and trend research, testable concepts, complete text-led campaign copy, independent review, and canonical delivery without promised engagement.

Install in OpenCorvusDownload this exact revisionTrust model

Opens the installed OpenCorvus desktop app. The client re-downloads and re-verifies this exact revision, then asks you for an install scope. No desktop app yet? Install OpenCorvus first

Bound execution graph

Workflow and handoffs

The graph shows who owns each step and which earlier result it depends on. It explains the team's collaboration contract; it is not live task progress and does not schedule Agents from the page.

Bound revision · 1 workflows · 7 nodes · 7 Agents
Bound revision20a82bf4
01Evidence-backed Content Campaign7 nodes
  1. 01viral-brief-strategistPublishes the bounded campaign brief.root
  2. 02viral-audience-researcherPublishes attributable audience evidence.← viral-brief-strategist
  3. 03viral-trend-researcherPublishes dated trend evidence.← viral-brief-strategist
  4. 04viral-concept-strategistJoins both research branches into a selected concept.← viral-audience-researcher + viral-trend-researcher
  5. 05viral-copy-producerPublishes complete campaign copy.← viral-concept-strategist
  6. 06viral-content-reviewerIndependently reviews the single copy-pack predecessor.← viral-copy-producer
  7. 07viral-delivery-ownerPublishes canonical campaign resources and matching interactive Artifacts.← viral-content-reviewer
Evidence output1

Intended scope

Use for evidence-backed, text-led campaign concepts and copy variants.

  • Product pillarswork
  • Agent roster7 declared roles
  • Declared workflows1 complete responsibility and dependency graphs
  • Full capability projection3 Skills · 4 tools · 0 MCP refs

Walkthrough pinned revision

Role and dependency walkthrough

This workflow explanation is pinned to the current package digest. It is not a running Agent session, timer, or generated language-model output. Real execution occurs in the OpenCorvus client.

builtin/viral-content@2026.08.19.1package sha256:20a82bf4715dbe07b0138d435c4a354cf68cf1330b9a5a940c4f74adee281bdf

A node becomes schedulable only after its depends_on evidence is terminal. This page explains that contract and does not advance runtime state.

evidence-backed-content-campaign

Evidence-backed Content Campaign

  1. 01viral-brief-strategistdepends_on: []
  2. 02viral-audience-researcherdepends_on: viral-brief-strategist
  3. 03viral-trend-researcherdepends_on: viral-brief-strategist
  4. 04viral-concept-strategistdepends_on: viral-audience-researcher, viral-trend-researcher
  5. 05viral-copy-producerdepends_on: viral-concept-strategist
  6. 06viral-content-reviewerdepends_on: viral-copy-producer
  7. 07viral-delivery-ownerdepends_on: viral-content-reviewer

Install handoff boundary

The OpenCorvus client owns the real scope choice when a later import is performed. This page only explains project and global behavior and does not submit an install itself.

The client requires an explicit scope

Project scopeApplies only inside the current project; the same package ID overrides a global installation.
User-global scopeAvailable to the current user, but never silently overrides a project installation.

The public page hands over one exact revision, or completes a signed bundle download. It never batch-installs or activates a team. The scope explanation describes client responsibility; it is not a web form that can be submitted.