NAU Public Service Academy · The Future of AI in Government & Public Services
How this was made
Yes, I built this with AI, used the way this session recommends using it: I direct the work, contribute my own research, review everything, and own the product. The AI drafted and checked inside a fixed path; I approved every step that mattered. The visual design language is my own, developed through my Cidi Labs design work in Canvas and my layout design in Canva. This page is the map.
The loop every piece went through
On a small screen, swipe the diagram sideways to see all of it.
What the loop produced
What ships, and what stays behind it
What the audience sees
- Seven pages: the intro, the walkthrough, the policy self-check, the takeaway hub, Keep Learning, the pipeline explainer, and this one.
- One staging folder that mirrors them exactly; publishing is a single manual upload I perform.
- A release log: each published version has a number and a dated entry.
What stands behind them
- A master source list: every citation has a full reference entry and a note naming the exact claim it supports.
- Audit reports: facts and figures, source fit, balance and neutrality, editorial tone, glossary coverage, accessibility, mobile rendering, and a simulated Q&A.
- Changelogs and a hand-off guide, so the whole project can be read, questioned, and reproduced.
- Supplied research PDFs.
The rules the loop runs under
A fact is cited only after the source text is fetched and read. Search-result summaries do not count; page numbers are recorded where they exist.
Sources are checked twice, by different eyes. The AI verifies before citing; I re-check the links and the claims myself, and my flags have set off full audits.
Every figure carries its link at the point of use and a reference entry in the master source list.
The tone standard is questions and sourced facts, not verdicts. New audience-facing text passes a written tone gate before it appears.
Errors are recorded, not erased. When review catches a mistake, the fix and the reason go into the changelog and the relevant audit.
Nothing ships without my review, and the AI never publishes. Publishing is a manual step I perform.
Can you reuse this?
Yes. You are welcome to reuse and adapt these pages, the policy self-check, and the walkthrough for your own office. A credit back to this project is appreciated, though not required. The copyright line below reserves formal rights; this note is the standing permission to reuse. The permission covers the material built here, not the third-party sources it cites, which keep their own terms.
On this session’s own spectrum, this workflow sits near Level 3: the AI drafts and checks inside a fixed path, and I hold the approval gates. The same design choice the walkthrough asks you to consider is the one that built it.