Knowledge bases rot because nobody owns the gap between a resolved ticket and a published article. Dock closes that gap. The drafting agent reads recent ServiceNow incidents, drafts a candidate article into a Dock row, links back to the source ticket, and waits for the IT lead to approve before anything is written to Confluence or Notion.
Confluence, ServiceNow, and Notion remain the systems of record for the raw data. Dock is the system of record for what the agent interprets from that data. Each Dock row carries a pointer back to the upstream record (servicenow_incident_id, confluence_page_id, notion_page_id), the agent identity that drafted it, the reviewer, the decision, and the timestamp. The agent does not cache state. When it needs current ticket status or the latest Confluence revision, it re-fetches via fresh API reads.
The Dock surface: kb_drafts
| servicenow_incident_id | source_summary | draft_title | target_platform | confidence | reviewer | status |
|---|---|---|---|---|---|---|
| INC0042118 | 7 tickets in 14 days about VPN MFA loop on iOS 18.4 | Resolving VPN MFA loop after iOS 18.4 update | Confluence (IT Helpdesk) | 0.91 | priya.r@ | approved, published |
| INC0042377 | 4 tickets about Slack SSO failure for contractors | Contractor SSO: why Slack rejects @partner.com logins | Notion (Internal Ops wiki) | 0.78 | dan.k@ | needs revision |
| INC0042455 | Single P1 outage, postmortem pending | Okta IDP outage 2026-05-22 root cause | Confluence (Postmortems) | 0.62 | unassigned | blocked |
One worked workflow
The agent runs every weekday morning. It queries ServiceNow for incidents resolved in the last seven days and clusters them by symptom. For the VPN MFA loop, it found seven incidents pointing at the same iOS update, drafted an article into a Dock row, attached the seven servicenow_incident_id values as evidence, and tagged Priya as the on-call endpoint lead.
Priya opened the row, fixed one screenshot caption, and approved. Approval flipped the row status, which triggered a publish call to the Confluence IT Helpdesk space. The Confluence page now carries a footer link back to the Dock row, so anyone reading the article can trace which incidents produced it and who signed off. Publish is gated behind a two-key handshake because writing to a customer-facing space is irreversible; the dangerous ops contract lists the full set of write actions that demand the same gate.
Why it matters
The Consortium for Service Innovation describes Knowledge-Centered Service as turning "everyday interactions into structured insights that drive organizational learning," and argues that organizations must "move beyond managing content repositories and build intelligent content ecosystems" (Consortium for Service Innovation). Agent-drafted articles honor that principle without burning analyst time. The draft is free. The review is the work.
Every published article is traceable. An auditor or a new IT hire can click from the Confluence page to the Dock row, see which incidents seeded it and which lead approved publication. That trail is the same one we use for audit and compliance and for research workflows, and it is the reason knowledge does not rot quietly.
Confluence is positioned as "knowledge, all in one place" (Atlassian). Dock is where that knowledge gets drafted, reviewed, and held accountable before it lands there.
Read the Dock for IT operations overview to see how KB maintenance sits alongside incident response and change management.
FAQ
Q: Does the agent publish directly to Confluence or Notion? No. The draft lives in a Dock row until an IT lead approves, and the publish call is a two-key handshake.
Q: What if Confluence or ServiceNow data changes after the draft is written? The agent re-fetches on every run. The Dock row stores the draft and the pointers, never a cached snapshot.
Q: Who is accountable when an agent-drafted article is wrong? The reviewer named in the Dock row. The draft is the agent's, the publication is the human's, and both stay on the record.
Q: Can I use Dock for KB maintenance if my team is on Notion only, not Confluence?
Yes. The target_platform field drives the publish call, so the same workflow drafts into Notion with the same reviewer gate and backlink.
