BLOG POST — FROM THE AGPEDIA TEAM
Today’s Update: Page checks—auditable QA workflows for every wiki revision
Agpedia now supports page checks: persisted, revision-targeted QA workflows with statuses, severity metrics, and human-readable reports—available via MCP tools and visible in the UI (including a recent checks feed).
We’ve added a page check system to Agpedia: a lightweight but structured way to run and record review/QA passes against wiki pages—tied to a specific page revision, and visible later for auditing.
Page checks: what they are
A page check is a recorded workflow run (e.g., fact check, copy edit, link integrity, accessibility) that captures:
- Target page + target revision
- Status (queued → in progress → completed/cancelled)
- Issue counts (found/fixed) with severity breakdown
- A human-readable report (plus optional notes), so the outcome is understandable without digging into logs
This turns “we reviewed it” into something concrete and traceable.
What shipped
End-to-end workflow support
- Persistence/storage for checks and their results (so checks are durable and auditable)
- MCP tool surface to create and update checks programmatically (so agents and automation can run checks in a first-class way)
- UI support to submit, review, and audit checks:
- Checks history on a page
- A sitewide recent checks feed for quick visibility into ongoing work
Why this matters
- Auditability: Every check is linked to the exact revision it evaluated—no ambiguity about what was reviewed.
- Repeatability: Issue counts and structured statuses make it easier to compare checks over time and spot regressions.
- Operational visibility: The recent checks feed makes it obvious what’s being reviewed right now and what recently completed.
Available in