TATERpedia: The Living Wiki That Writes Itself

Security teams generate enormous amounts of institutional knowledge during compliance work — how a specific Conditional Access policy was configured and why, why a particular Exchange setting was accepted as a risk, what the audit team asked about MFA enforcement last quarter. That knowledge lives in email threads, Slack messages, and memory. TATERpedia gives it a permanent, searchable home.

What Makes TATERpedia Different

Most wikis require someone to decide to write an article. TATERpedia removes that activation energy barrier: the daily seed timer automatically creates stub articles for every active control, framework, and compliance zone in your organization. The stubs are minimal — a title, a summary placeholder, and a body skeleton — but they exist. Your team only needs to fill them in, not create them from scratch.

Every page in TATERpedia has a required summary field (20–600 characters) that surfaces in three places: the list card, the single-page view above the body, and the contextual panels embedded in control and policy detail views. A well-written summary means your team can answer "what is this?" in two sentences without reading the full article.

Structured Article Format

TATERpedia articles follow a consistent template:

• Summary — the 20–600 character hook, required on every page
• Body — free-form Markdown with section headings
• Tags — categorical labels for filtering and cross-linking
• Linked controls — direct references to TATER compliance controls
• Linked frameworks — mapping to CIS, SCUBA, DISA STIGs, or custom frameworks
• Linked policies — references to your organization's policy documents

Contextual Panels in Control and Policy Detail

The most valuable TATERpedia feature is not the wiki itself — it is where the wiki surfaces. Every control detail panel in TATER Security has a TATERpedia panel at the bottom. When a relevant article exists for that control, it appears inline with the summary and a "Read more" link. When no article exists, a "Create stub" button appears that seeds a basic article in one click. Auditors reviewing evidence for a control see the relevant institutional context without navigating to a separate tool.

Policy detail panels have the same treatment: a TATERpedia lookup by linked framework or policy topic surfaces any related articles. A published Information Security Policy links directly to the wiki articles that document how each of its requirements is implemented in your environment.

"TATERpedia turns audit prep from a scramble into a lookup. The answers were already written — they just needed a home."

Writing with AI Assistance

The TATER MCP server exposes five wiki tools: get_wiki_page, search_wiki, create_wiki_page, update_wiki_page, and validate_wiki_content. Claude, Microsoft 365 Copilot, or any MCP-capable AI agent can draft, expand, or validate TATERpedia articles as part of a compliance workflow. The MCP instructions mandate that agents call upsert_config_doc and update_wiki_page at the end of every work session — so every AI-assisted remediation leaves behind a documentation trail automatically.

Validator and Quality Gates

TATERpedia includes a built-in validator that checks articles before saving: required summary present and within character limits, linked controls resolve to real catalog entries, no broken framework references. Validation warnings appear in a themed modal with specific hints — not a generic error message — so authors can fix issues immediately rather than guessing.