Why PraisonAI — external positioning one-pager

オープン
#5,784 コメント 2 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
12/100
issue の種類
ドキュメント
明瞭さ
説明が足りない
活発さ
活発
領域
documentation

調査の方向性

This is a product and go-to-market writing task with no named file to edit, and the body says it needs leadership approval before any public use. The payload references scripts/live_sdk_validation_v4712.py and scripts/operator_golden_path_check.ps1 as evidence sources, so reading them shows what the claims rest on. Done would mean a draft one-pager that maps every claim to an evidence row, which a newcomer should confirm with maintainers before starting.

索引モデルが issue の本文から書いたものです。

説明

bug claude documentation

Why PraisonAI — external positioning one-pager

Type

Product / GTM

Labels

positioning · gtm

Requires leadership approval before public website or sales collateral.


Summary

Dimension Detail
Format Single page (PDF or HTML) for sales and docs
Tone Evidence-backed; no tool-count arms race
Approval Leadership sign-off before external publish
Grounding Live harness + operator validation results

Purpose

Answer buyer questions: “Why this stack vs crew-first frameworks or graph-only orchestration?” without naming competitors in customer-facing copy. Internal matrix below uses neutral category labels only.


Audience segments

Segment Need Proof to show
Primary buyer Platform team running 24/7 agents in messaging surfaces Needs gateway + isolation
Secondary buyer SDK team embedding agents in product Needs deterministic harness
Not target Q1 Tool catalog size competition Avoid roadmap distraction
Proof point 7/7 live SDK harness Lead with trust
Proof point Operator health script green Lead with production

Message architecture

         ┌──────────────────────────────────────┐
         │  Headline: production AI workforce   │
         └───────────────────┬──────────────────┘
                             │
       ┌─────────────────────┼─────────────────────┐
       ▼                     ▼                     ▼
 SDK trust            Operator path          Safe execution
 (7/7 harness)    (gateway + channels)      (sandbox/MCP)

Message components (draft)

Component Copy direction Notes
Core promise One agent model from SDK through gateway to channels and sandbox
Differentiator Layered debugging: prompt, context, harness, loop, graph, runtime
Question answered Who runs my agents where customers already are — safely?
Migration story Adapter path for crew-style YAML plus gateway hybrid
Honest gap Shell-tool sandbox demo needs provider model enablement

Category comparison (internal — neutral labels)

Category Typical emphasis elsewhere PraisonAI emphasis
Crew-first frameworks Multi-agent YAML, training UI OSS gateway, messaging channels, MCP/sandbox
Graph orchestration Durable graph runtime AgentTeam/AgentFlow for non-graph adopters
Hosted agent OS Managed API control plane Messaging-native workforce + self-host path
Minimal agent SDK Responses + hosted sandbox Full stack: memory, gateway, channels

Expected vs actual (GTM)

Item Expected Actual today
One-pager exists Approved PDF/HTML Strategy text only
Claims trace to harness Footnoted scenario names Ad hoc demos
Migration paragraph Crew-adapter + gateway Not published
Five guaranteed integrations Listed with docs links Scattered examples
Gap disclosure Shell sandbox model note Known internally only

Evidence table (cite in footnotes)

Claim Evidence type Pass signal
SDK reliable Live harness 7/7 JSON summary
Gateway production-ready Health probes HTTP 200 /health
Channels work Live inbound/outbound Reply within SLA
Isolation works Sandbox command exit 0 in container
Browser automation Bridge health extension_connections≥1

Terminal evidence — expected (internal validation)

$ python scripts/live_sdk_validation_v4712.py
summary passed=7 failed=0
$ pwsh scripts/operator_golden_path_check.ps1
exit=0

Terminal evidence — unexpected (do not claim publicly)

harness passed=6 failed=1
→ hold marketing claim until green
gateway health FAIL
→ do not state "production-ready gateway" in one-pager

How to fix (content production)

Step Deliverable Owner
1 Draft one-page HTML from message table Product
2 Attach harness JSON artifact as appendix Engineering
3 Legal/comms review forbidden superlatives Leadership
4 Add migration paragraph (adapter + gateway) Docs
5 List five guaranteed integrations with links Docs
6 Publish only after approval checkbox Leadership

Five guaranteed integrations (target list)

# Integration Buyer value
1 Web search tool Fresh facts
2 Sandbox execution Safe command run
3 Gateway + channel 24/7 workforce
4 Long-term memory Continuity
5 MCP tool server Extend without fork

Acceptance criteria

  • Leadership approval recorded
  • Every external claim maps to evidence table row
  • Known gaps disclosed in internal FAQ footnote
  • No competitor trademarks in customer-facing PDF

Out of scope

  • Pricing page redesign
  • Paid cloud SKU launch

Engineering FAQ

Question Answer Verify with
Can we claim 7/7 without CI? Only with attached JSON artifact dated same week Evidence table
Competitor names in PDF? Forbidden — use category labels Comms review
Tool count on slide? Forbidden in Q1 positioning Slide review
Shell sandbox gap? Disclose in internal FAQ footnote only Honest gap row
Who approves? Leadership checkbox on issue Sign-off field
Migration paragraph length? One short paragraph + link to adapter docs Editor
Five integrations flexible? Must be shippable examples with docs links Docs audit
HTML vs PDF? Either — single source markdown Build pipeline
Sales training? Optional webinar after publish Enablement
Revoke published page? If harness regresses — unpublish claim Monitoring
Customer quote? Requires legal if named logo Legal
Diagram style? Use neutral icons — no trademark logos Design
Version date on page? Required in footer Template
Translation? After English approval Process
Website placement? /docs/why or /product — leadership picks Routing
Evidence refresh cadence? Each major release Release calendar
Adapter naming? Use product term for crew-style YAML adapter Docs term
MCP mention? Yes — in five integrations list Feature list
24/7 claim? Requires channel + gateway evidence Operator script
Debug layer claim? Link to debugging guide section Docs anchor

Operational runbook

Step Action Expected signal If fail
1 Attach latest harness JSON to draft passed=7 Hold draft
2 Attach health script green log exit 0 Hold draft
3 Draft copy using message table only No trademark names Comms review
4 Internal category comparison for sales training Not in PDF Separate doc
5 Leadership review meeting Checkbox signed Reschedule
6 Publish to docs site path approved URL live Rollback plan
7 Set evidence refresh reminder per release Calendar event Ops

Evidence log template

Run Date Command Expected marker Unexpected marker
GTM-1 YYYY-MM-DD Harness JSON attached passed=7 Stale date
GTM-2 YYYY-MM-DD Health script log exit 0 Missing
GTM-3 YYYY-MM-DD Leadership sign-off Recorded Pending

Engineering FAQ

Question Answer Verify with
Can sales cite tool count? No in Q1 external page Review
Partner co-marketing? Requires separate legal review Process
Open source mention? Yes — gateway OSS emphasis Message table
Self-host vs cloud? Self-host path in operator evidence Doc link
Benchmark graphs? Only if reproducible script attached Methodology
Customer logo? Not in v1 one-pager Future
Analyst briefing? Use category labels only Training
Website A/B? Out of scope Marketing
Revise after bad release? Unpublish until harness green Policy
Internal wiki copy? Allowed before external Intranet

One-pager section budget

Section Word budget Required proof Approver
Headline ≤15 words None Product
Value prop ≤60 words Harness 7/7 footnote Product
Operator proof ≤80 words Health script log Engineering
SDK proof ≤80 words JSON artifact Engineering
Migration ≤50 words Adapter doc link Docs
Gap footnote ≤40 words Internal only Engineering
主要言語
Python
スター
9.3k
フォーク
1.5k
平均マージ
1日 5時間
マージ済み PR(30日)
520

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

MervinPraison/PraisonAI のほかの issue

MervinPraison/PraisonAI の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。