Reference

documents

Reference

Memory Layer (v0.3)

Memory Layer (v0.3) Purpose Scoped memory for Conversation + User per docs 02-system-architecture-prompt.md §8. Current Scope Domain: MemoryScope, MemoryInterface Infrastructure: WpMemoryStore → wp_teddy_memory Application: ChatMemoryComposer, RememberChatTurn Wired into legacy ChatService and agent…

Reference

Deploy Teddy MCP → blackbean.io.vn (OpenClaw)

Deploy Teddy MCP → blackbean.io.vn (OpenClaw) Hướng dẫn gắn OpenClaw với site live https://blackbean.io.vn qua MCP bridge (mcp-server/). Bridge chạy trên máy OpenClaw (stdio), không chạy trong PHP trên server. WordPress chỉ…

Reference

Observability

Observability Purpose Observability records what Teddy executed and how much AI usage each provider consumed, so admins can inspect risky actions and operating cost. Current Scope Tool audit records in wp_teddy_audit_log AI…

Reference

Onboarding

Onboarding Purpose First-run wizard so a new site owner can go from install → useful AI in ~5 minutes without reading the architecture docs. Flow (required steps) Back up website — detect…

Reference

Provider Adapter

Provider Adapter Purpose Teddy is provider-independent. Domain and Application code depend only on AiProviderInterface. Concrete vendors (OpenAI, Google, Anthropic, …) are wired through the WordPress AI Client adapters. Classes Role Path Domain…

Reference

Extension SDK (v0.5)

Extension SDK (v0.5) Purpose Public API for third-party plugins to extend Teddy without forking core. Entry points teddy() facade → src/SDK/TeddyFacade.php Global helpers → src/SDK/functions.php Hook: teddy_boot, teddy_register_extensions Registrars Gateway Registers ToolsGateway…

Reference

Security

Security Purpose Teddy treats AI actions as privileged automation. Every mutating tool must go through approval, capability checks, and audit logging before GA. Automated audit Service: src/Application/UseCase/SecurityAuditService.php Admin: Teddy → Security (requires…

Reference

Tool System

Tool System Purpose Every Teddy capability that reads or changes WordPress data must be a tool: a named, typed, capability-gated unit of work. The agent never calls raw WP APIs directly. Lifecycle…

Reference

Workflow Engine (v0.4 foundation)

Workflow Engine (v0.4 foundation) Purpose Resumable multi-step automation per docs 02-system-architecture-prompt.md §7. Current Scope Domain contracts: WorkflowStepInterface, WorkflowRunnerInterface, WorkflowRunStoreInterface Application: WorkflowRunner, WorkflowRegistry, StartWorkflow, GetWorkflowRun Infrastructure: WorkflowRunRepository, AsyncQueueDriver (Action Scheduler → WP-Cron fallback)…

Reference

OpenClaw onboarding for Teddy buyers

OpenClaw onboarding for Teddy buyers Package: openclaw/ (@teddy/openclaw) Customers who use OpenClaw but do not know MCP can connect with one command after installing Teddy on WordPress. Buyer flow Install / update…

Reference

Playbook: Comment triage

Playbook: Comment triage comment.list status=hold (and optionally spam). For each item: summarize author + excerpt for the human. To change status: call comment.set_status → receive preview + approval_token. Ask human on Zalo:…

Reference

Playbook: Daily briefing

Playbook: Daily briefing Call MCP teddy-live__teddy_site_briefing (or Copilot: site.briefing). If needs_attention is false → reply briefly or HEARTBEAT_OK. If true → summarize actionable[] for the human (Zalo / chat). Optional follow-ups: Pending…

Reference

Playbook: Publish / schedule a post

Playbook: Publish / schedule a post Draft via post.create status=draft (or update existing with post.update). Check gaps: featured image, excerpt, title length (content.gaps or manual). Optional: seo.meta.generate for the post. Publish now:…

Reference

Playbook: Weekly SEO

Playbook: Weekly SEO content.gaps with days_stale=90 — list posts needing refresh. media.find_missing_alt — images without alt text. For a target post: seo.article.audit then seo.meta.generate if needed. Schedule updates with post.update (post_date +…

Reference

Channels (multi-channel messaging)

Channels (multi-channel messaging) Teddy routes external messaging platforms through a thin adapter layer into the same public chat + RAG pipeline as the site widget. Architecture Facebook / future channels │ ▼…

Reference

06 — Features: Teddy

06 — Features: Teddy Tài liệu mô tả tính năng đã ship trong Teddy (plugin hiện tại). Không phải roadmap hay kiến trúc — nếu muốn biết “sắp có gì”, xem 04-roadmap-prompt.md.…

Reference

Agent Pipeline

Agent Pipeline Purpose The agent pipeline is the Clean Architecture path for Teddy admin copilot turns. It routes natural-language requests through domain tools with permission checks, validation, approval previews for dangerous actions,…

Reference

Channels — Phase 2 (later)

Channels — Phase 2 (later) Not shipped in Teddy 1.2. Same ChannelAdapterInterface contract. Facebook Page publish Tool / workflow step channel.publish (feed post) Permissions: pages_manage_posts (+ App Review) Keep separate from messaging…

Reference

Knowledge Layer (v0.3 foundation)

Knowledge Layer (v0.3 foundation) Purpose The knowledge layer retrieves relevant site content for prompt augmentation (RAG). It follows the Clean Architecture contracts in 02-system-architecture-prompt.md while reusing the existing embeddings stack through a…

Reference

MCP bridge (OpenClaw → Teddy)

MCP bridge (OpenClaw → Teddy) Package: mcp-server/ Exposes Teddy domain tools over the Model Context Protocol so OpenClaw (or any MCP client) can manage the WordPress site through the same ToolRegistry /…