Evidence-Backed Content Agent
Agent coordinates research artifacts and checks. It does not decide what gets published.
Evidence-backed content agent is reference architecture used by this project. It separates opportunity, brief, evidence, draft, verification, and pull request.
Architecture article explains why stages exist. Runnable workflow defines execution steps and stop conditions.
Inputs
- Approved content brief
- Evidence map
- Editorial policy
- Source policy
- Voice rules
- Existing content manifest
Outputs
- Markdown content
- Metadata record
- Evidence links
- Internal-link updates
- Validation result
- Focused pull request
Permissions
Agent may read public sources, edit branch files, run validation, and open pull request. It may not merge, deploy, weaken branch protection, or publish directly.
Stop conditions
Agent stops when request duplicates existing intent, core conclusion lacks evidence, comparison has no consistent test, or contributor conflict is unknown.
Evidence state
Reference architecture is documented and encoded in repository skill. Production quality benchmark has not been run yet.