Patriot University (patriot.university) is a civic accountability journalism and education platform. Its readers are politically engaged, news-literate adults who are skeptical of institutional media, pressed for time, and motivated by civic action. They come for facts, connections, and accountability — not narrative entertainment.

This skill governs how PU editors structure every article, brief, tracker entry, or explainer using the PU Civic Accountability Format (CAF).

Why This Format Exists

Traditional news articles interweave fact and interpretation in ways that reward trust but punish verification. PU’s readers don’t grant trust — they verify. This format separates the verifiable from the interpretive at the structural level, so a skeptical reader can check our facts without wading through our analysis, and an action-oriented reader can find civic mechanisms without reading the full evidence chain.

The format enforces three things simultaneously:

• Scan-first legibility: a reader who only reads the headline and bold brief still gets

the essential story

• Transparency architecture: facts, analysis, and counter-perspectives are visibly

separated so readers can calibrate trust

• Progressive disclosure: content is layered so each depth is self-sufficient — from a

60-word bite to a full evidence chain with knowledge-graph connections

Readability Standards

PU content must be accessible to any engaged citizen, not just policy specialists or lawyers.

Section	Maximum Grade Level	Rationale
Headline	Grade 6	Must be instantly parseable
The Brief	Grade 8	Must function as a standalone for the widest audience
Why It Matters	Grade 10	Civic significance in accessible language
The Facts	Technical terms permitted	Define every term on first use; use parenthetical plain-language equivalents
Team’s Take	Grade 10	Analysis should be clear, not academic
The Counterfactual	Grade 10	Counter-arguments must be as accessible as the main argument

When content exceeds grade 12 (constitutional analysis, legal rulings, contract mechanisms), place a plain-language summary of 2-3 sentences at the top of that section before the technical content. This satisfies WCAG 3.1.5 (Reading Level) and serves PU’s mission: we explain constitutional law so any citizen can understand it, not just lawyers.

Testing: Run The Brief through Flesch-Kincaid before publication. Any score above grade 8 requires a rewrite.

---

Required Sections (in order)

1. HEADLINE

One declarative sentence. Not a question. Not a tease. The news.

“EPA Awarded $40M No-Bid Contract to Firm With Ties to Agency Director” NOT: “What You Need to Know About the EPA Contract Controversy”

Brevity is confidence. If the headline needs a colon or a semicolon, rewrite it.

---

2. THE BRIEF (~50 words max)

One short paragraph. Answers: What happened? Who did it? What is the concrete consequence? Written as if the reader will read nothing else. No throat-clearing, no “In a bombshell development…” — just the essential facts.

Format:

[Actor] [did/decided/ruled/awarded] [specific action] on [date], [consequence or significance
in one clause].

Readability gate: Grade 8 or below. If a non-specialist cannot understand The Brief without context, rewrite it.

---

3. WHY IT MATTERS

Two to four sentences. Explains the civic, legal, or democratic significance — not just the political significance. Answer: *Why should a citizen care about this beyond partisan interest?*

Keep this grounded. Do not editorialize. The significance should be self-evident from the facts.

---

4. THE FACTS

The core reporting. Bullet-formatted, attributed, dated. Every claim needs a source anchor (document, filing, official record, named source, or Patriot University knowledge base entry).

Format rules:

• Each bullet = one factual claim
• Lead the bullet with the most important word (not “The”, not “A”)
• Include dates, dollar amounts, proper names — specifics are credibility
• End each bullet with a source anchor in parentheses: (Source: FEC filing, 3/14/2025)

Do not mix analysis into The Facts section. If it requires interpretation — pattern recognition, inference, or editorial judgment — it belongs in Team’s Take.

Plain-language gate: When a bullet contains legal or technical terminology, include a parenthetical definition on first use:

- Impoundment (executive refusal to spend congressionally appropriated funds) of $4.2B in
  FEMA disaster relief confirmed by GAO letter. (Source: GAO-25-107391, 2/28/2025)

---

5. TEAM’S TAKE (labeled as such)

The editorial team’s analysis or argument — clearly flagged as interpretation. This is where pattern recognition, knowledge graph connections, and accountability framing live.

Opens with: “Team’s Take:” in bold.

This is where you connect the story to:

• Known entity relationships in the PU knowledge graph (donor → official → contractor)
• Historical patterns (prior no-bid contracts, prior rulings, prior affiliations)
• Systemic significance (what this means for the institution, not just the individual)

Be direct. Don’t hedge analysis with unnecessary qualifiers. Own the interpretation — and own the distinction between what is documented (The Facts) and what is inferred (here).

AI disclosure: If AI skills or agents contributed to the analysis, note this at the end of the section: (Analysis developed with AI assistance; reviewed by [editor name])

---

6. THE COUNTERFACTUAL (when applicable)

Presents the strongest legitimate counter-argument, alternative framing, or factual dispute — not a straw man.

Opens with: “The Counterfactual:” in bold.

Use this section when:

• There is a credible, good-faith alternative interpretation of the facts
• The subject or their representatives have issued a public response
• A relevant expert or official disputes a key claim

Do not use this section to “both-sides” documented wrongdoing. The bar is: *would a reasonable, informed person find this counter-argument worth considering?*

In articles invoking this skill, The Counterfactual replaces the “For Trump Supporters: Questions Worth Considering” section used in knowledgebase documents.

---

7. CONNECTIONS (Patriot University-specific)

This section is unique to PU and is the platform’s most valuable structural differentiator. It surfaces entity relationships from the PU knowledge base — the political communications personnel directory, the J6 tracker, the election deniers reference, the no-bid contracts tracker, and the court rulings tracker.

Opens with: “Connections:” in bold.

Format as brief relationship statements:

→ [Person A] → [Relationship type] → [Person/Org B] (Source: PU Knowledge Graph / [tracker name])
→ [Person A] also appears in: [tracker name], [entry date]

If no connections exist in the PU knowledge base, omit this section. Do not fabricate connections. AI-surfaced connections require human verification against primary sources before publication; mark as (AI-surfaced, human-verified) when applicable.

---

8. CIVIC ACTION (when applicable)

This section bridges information to civic participation. PU is the accountability platform that tells readers not just what happened, but what democratic mechanisms exist to respond.

Opens with: “Civic Action:” in bold.

Include only when concrete, non-partisan civic mechanisms exist. Never tell readers what to do — tell them what mechanisms exist:

• Contact information for relevant elected officials or oversight bodies
• Upcoming public hearings, comment periods, or elections where this issue is actionable
• Applicable oversight mechanisms (FOIA routes, inspector general offices, ethics complaint

processes, judicial review timelines)

• “How to verify this yourself” — replicable public-records steps any citizen can take

Gate: Omit this section when no concrete civic action path exists. Do not manufacture urgency or imply readers are obligated to act. The section is informational, not advocacy.

---

9. EVIDENCE TRAIL (optional)

Structured references for readers who want primary sources, knowledge graph context, or independent verification paths. This replaces a generic link dump with a provenance chain.

Format:

**Evidence Trail**
→ Primary source: [specific document, ruling, or filing with citation]
→ PU Knowledge Base: slug — [one-line context for why this KB entry matters here]
→ Related tracker: [tracker name] → [specific entry or entity]
→ Community cluster: [entity-graph cluster name] — [what the cluster reveals]
→ External verification: [link for independent reader verification]

Only include Patriot University knowledgebase content unless the editor has specifically requested web research or original external citations.

If no relevant knowledge base entries, trackers, or community clusters exist, include only the primary source and external verification lines.

---

Transparency Disclosure

PU uses AI skills and agents as part of its editorial workflow. Reader-facing transparency is mandatory — not optional.

AI Involvement	Required Disclosure
AI generated first draft of article	Footer: “Initial research and drafting assisted by AI; all facts independently verified by [editor name]”
Entity connections surfaced by AI	Inline in Connections section: (AI-surfaced, human-verified)
AI-generated analysis in Team’s Take	End of section: (Analysis developed with AI assistance; reviewed by [editor name])
AI Skills used for research	Editorial log notation (internal): list skill slugs used

Principle: Transparency about AI use is a trust asset, not a liability. Readers who discover AI involvement without disclosure lose trust. Readers told upfront that AI assists but humans verify gain confidence in the verification layer.

---

Content Type Variants

Different PU content types use subsets of the full framework:

Content Type	Sections Used	Target Length	Distinguishing Feature
Article	Full framework (all 9 sections as applicable)	400–800 words	Narrative thread, full editorial voice
Tracker Entry	Headline → Brief → Facts → Connections	150–300 words	Reference document, update-oriented, no editorial voice
Explainer / Backgrounder	Headline → Brief → Why It Matters → Facts (expanded, with subheadings) → Counterfactual → Evidence Trail	400–700 words	Background context, definitional, teaches mechanisms
Breaking Brief	Headline → Brief → Facts (partial) → Connections	100–200 words	Time-sensitive, mark [DEVELOPING — last updated: date/time], fill analysis later
Infographic / Whiteboard	Headline (as title) → Brief (as opening) → Facts (as labeled panels) → Connections (as diagram)	Visual format	Each panel = one factual bullet, labeled with the claim

---

Voice and Tone Standards

What PU voice is:

• Direct and declarative
• Specific over vague (names, dates, dollar amounts, titles)
• Grounded in documents and records
• Civic in framing (democratic stakes, not just partisan stakes)
• Confident in analysis when analysis is warranted
• Accessible without being patronizing

What PU voice is not:

• Outrage-performative (“shocking”, “explosive”, “bombshell”)
• Hedged to the point of meaninglessness (“some say”, “critics argue” without attribution)
• Passive-aggressive (“the official, who did not respond to requests for comment, has a

history of…”)

• Jargon-heavy without explanation
• Academic or legalistic without plain-language grounding

---

Accountability Journalism Principles

These govern editorial judgment when applying the framework:

1. Name the actor. Passive constructions that obscure who did what are not acceptable.

“Mistakes were made” → “Director Chen approved the no-bid contract.”

1. Document the pattern. A single incident is news. A pattern is accountability

journalism. Use the Connections section and PU trackers to establish pattern.

1. Show the mechanism. Don’t just say influence existed — show how the money moved,

the door revolved, the appointment was made.

1. Separate documented fact from inferred conclusion. The Facts section is for what

can be sourced. Team’s Take is for what it means.

1. Represent subjects fairly. Include official responses in The Counterfactual

when they exist. Accuracy requires giving subjects the opportunity to respond on record — not to protect them, but to protect the reporting.

1. Bridge to civic action. When democratic mechanisms exist for accountability or

oversight, surface them. Information without agency is incomplete journalism.

1. AI-assisted content requires human editorial sign-off. Flag any AI-drafted

content for editor review before publication. Entity connections from the PU knowledge graph must be verified against primary source documentation before publishing.

---

Quick Reference: Section Checklist

Section	Required	Max Length	Opens With	Grade Level
Headline	Always	1 sentence	Declarative verb	≤ 6
The Brief	Always	~50 words	Actor + action	≤ 8
Why It Matters	Always	2–4 sentences	Civic significance	≤ 10
The Facts	Always	Bullets, no limit	Specific noun	Technical OK (define terms)
Team’s Take	Usually	1–3 paragraphs	“Team’s Take:”	≤ 10
The Counterfactual	When applicable	1–2 paragraphs	“The Counterfactual:”	≤ 10
Connections	When KB entries exist	Relationship bullets	“Connections:”	N/A
Civic Action	When mechanisms exist	3–5 items	“Civic Action:”	≤ 8
Evidence Trail	Optional	3–5 structured refs	“Evidence Trail”	N/A

---

Sample Article Shell

# [HEADLINE — declarative, one sentence, grade 6 or below]

[THE BRIEF — 50 words max. Actor, action, consequence. Grade 8 or below.]

**Why It Matters**
[2–4 sentences on civic/democratic significance.]

**The Facts**
- [Specific claim, date, actor.] (Source: [citation])
- [Specific claim, date, dollar amount.] (Source: [citation])
- [Specific claim, named party.] (Source: [citation])

**Team's Take**
[Analysis, pattern recognition, knowledge graph synthesis. Owned interpretation.]
*(Analysis developed with AI assistance; reviewed by [editor name])*

**The Counterfactual**
[Strongest legitimate counter-argument or official response, if one exists.]

**Connections**
→ [Entity A] → [Relationship] → [Entity B] (Source: PU [tracker name])
→ [Entity A] also appears in: [tracker], [date]

**Civic Action**
→ Oversight body: [relevant IG, ethics office, or committee] — [how to file]
→ Public comment: [docket or hearing] — [deadline]
→ Verify yourself: [public records step any citizen can replicate]

**Evidence Trail**
→ Primary source: [document citation]
→ PU Knowledge Base: related-slug — [context]
→ Related tracker: [tracker name] → [entry]
→ External verification: [independent source link]

---

Editor Workflow

When using this skill to draft or review a PU article:

1. Identify content type (article / tracker entry / explainer / breaking brief /

infographic) and apply the appropriate section subset

1. Start with The Facts — get the sourced claims on the page before writing anything

else; analysis follows evidence, not the reverse

1. Write The Brief last — it’s the hardest sentence and easiest to write once you

know the full story

1. Test readability — run The Brief through Flesch-Kincaid; rewrite anything above

grade 8; check that technical terms in The Facts have parenthetical definitions

1. Run The Connections check — query the PU knowledge base for any entity relationships

before publishing; missed connections are missed accountability

1. Check for civic action paths — are there oversight mechanisms, public comment periods,

or verification steps a reader could take? If yes, add the Civic Action section

1. Apply the voice check — scan for outrage language, passive constructions, and

unsourced attributions; replace with specific named actors and documented claims

1. Flag AI involvement — note in editorial log any skills, agents, or AI team members

used; add reader-facing disclosure per the Transparency Disclosure table

1. Verify progressive disclosure — read only the Headline + Brief. Does it stand alone?

Read through Why It Matters. Still coherent without The Facts? Each layer must be self-sufficient.

---

Lineage

The PU Civic Accountability Format draws on two acknowledged influences:

• Semafor’s transparency architecture (2022): the principle of structurally separating

facts from analysis so readers can calibrate trust

• Axios Smart Brevity (2016): the discipline of scan-first formatting where every

sentence earns its space

PU extends these foundations with knowledge-graph integration, progressive disclosure for civic content, plain-language accessibility gates, civic action bridging, and AI transparency architecture — capabilities neither source format was designed to provide.