Contextual Documentation
Documentation that lives where the work does.
Scribe keeps documents, notes and discussions attached to the resources they describe, such as a schedule, a script, a managed parameter or a compliance control, instead of in a wiki nobody opens. Edits build a working draft, readers see only the version you promote, and a document is flagged the moment the thing it describes changes. AI can draft and agents can read, under the same permissions as the people they act for.
Wikis drift from the systems they describe, so people stop trusting them. Scribe attaches documents, notes, and discussions to the resources they cover, flags a document the moment its resource changes, shows readers only the promoted version, and lets AI draft and agents read under the same permissions as people.
- Write notes and documents in Markdown with diagrams and attachments
- Anchor each doc to any governed resource, and capture a note from any page
- Keep a draft until you promote it, with visual diffs, rollback, and conflict-safe editing
- Get a staleness flag, routed to a steward, when an anchored resource changes after the doc was last promoted — and verify docs on a schedule
- Let AI draft, and agents read, under the same permissions
What you get
What Scribe gives your team.
Documents and notes in one model
Notes are personal until you publish; documents follow a draft-then-promote flow; a note that outgrows itself becomes a document without changing what readers see.
Anchored to what they describe
Every documentable resource carries a Docs & Notes tab and Add note and Discuss actions, and quick capture attaches a note to whatever page is open.
Draft until you promote
Write in Markdown with live preview, autosave, templates and pasted screenshots. Readers only ever see the explicitly promoted version.
Version history and visual diffs
Compare versions side by side, promote or revert any version, and get a clear diff if two people save over each other.
Staleness flags and verification
When an anchored resource changes after a document was promoted, its steward is told which subject moved. Mark documents Verified and put re-verification on a schedule.
AI drafts, agents read
Draft with the organization's own AI sources, and let agents search and read promoted documentation under the acting person's access. Personal notes stay invisible to agents.
How it works
- 1
Write beside the resource
Open the Docs & Notes tab on any documentable resource, or quick-capture a note from the app bar. Start from a template and write in Markdown with live preview, diagrams and pasted screenshots.
- 2
Draft, compare, promote
Edits accumulate as a working draft that only you see. Compare versions side by side, then promote one. An organization can require a change request before publishing.
- 3
Stay current with the resource
When an anchored resource changes after the last promotion, the document is flagged and its steward is told which subject moved. Stewards verify at the exact version, and re-verification can follow a schedule.
- 4
Review coverage
A console reports documentation coverage per resource type, stale documents, verified and review-due counts, most-read documents and searches that found nothing, per organization.
Ask AI about Scribe
Every Scribe page has an Ask AI button. It opens a chat that already has the page, its rows, and your selection. Try asking:
- Which documents on this page are flagged stale, and which resource changed under each?
- Which of these documents are verified, and which are due for re-verification?
- Which of the documents listed here are still drafts that readers cannot see yet?
How teams use it
- Attach a runbook to the script it describes and be told when the script changes.
- Capture a private note from any page and publish it only when it is ready.
- Verify critical procedures on a quarterly schedule and see which documents are overdue.
Frequently asked questions
See Scribe in action
Join the early-access list, or talk to our team about your environment.
Talk to us