peptide-repo/prautoblogger
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(arch): link to cross-app engineering reference docs

Browse Source 
Adds a one-paragraph pointer at the top of ARCHITECTURE.md so any
engineer working in this single-app repo can find the cross-app
engineering reference material — Cloudflare AI Gateway routing,
OpenRouter account sharing, the interface pattern, image-generation
stack, social distributor choice — and the incident runbook for
cross-app failure modes (distributor down, LLM provider revoked,
budget burn runaway).

The referenced docs live in the CTO workspace at
`Peptide Repo CTO/docs/engineering/` as the canonical source. If
those docs need to be visible from app-only Cowork sessions later,
we'll mirror or move them to a shared mount.

No code changes. Pure docs.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
peptiderepo
2026-04-15 08:36:23 +07:00
parent 0bba5cbd82
commit 018a78000c
1 changed files with 2 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
ARCHITECTURE.md
View File

@@ -1,5 +1,7 @@
# PRAutoBlogger — Architecture
> **Cross-app context:** decisions that affect multiple plugins (Cloudflare AI Gateway routing, OpenRouter account sharing, the interface pattern, image-generation stack, social distributor choice) are recorded in `Peptide Repo CTO/docs/engineering/decisions/`. The incident runbook for cross-app failure modes is at `Peptide Repo CTO/docs/engineering/INCIDENT-RUNBOOK.md`. Engineer PRAutoBlogger should read both before making decisions that cross plugin boundaries.
PRAutoBlogger is a WordPress plugin that monitors social media (starting with Reddit) for recurring questions, complaints, and comparisons in a configured niche, uses LLM agents (via OpenRouter) to generate high-quality blog articles from those insights, runs them through a chief editor agent for quality review, and auto-publishes them on a configurable daily schedule. All collected data and generation metrics are stored for a self-improvement feedback loop.
---