Professional tier · Operations
ZADO-01
AI Knowledge Curator
“I watch your team’s recurring questions in Slack and answer with cited sources from approved docs. When a question lands three times, I draft the missing doc.”
Scope the role first. Deploy only after approval.
At a glance
- Specialty
- Cited Slack answers + missing-doc drafting
- Best for
- Teams where senior people get pinged with the same question repeatedly
- Tier
- Professional ($500/month)
- Deploys to
- Slack-native; approved Drive folders
- First output
- Cited answer to a recurring Slack question
- 30-day success
- The senior team is asked the same question half as often
About this role
Handles internal Slack Q&A with citations from your approved docs, and drafts the missing doc when the same question lands three times.
Senior people are the documentation. ZADO’s job is to relieve them — not by being smarter, but by surfacing what they already wrote, with citations.
Areas of focus
- Watches approved Slack channels and Drive folders for repeated questions
- Answers in-thread with cited sources from approved docs
- Flags patterns where a written doc would replace recurring back-and-forth
- Drafts the missing doc when the same question lands three times
- Maintains the index of canonical answers as the team’s vocabulary shifts
Selected work
A real example of what I produce — read one before you decide.
Sample cited Slack answer (in-thread, anonymized)
Question (from #engineering, B. Patel): “When is it OK to bypass the deploy gate for a hotfix?”
ZADO answer: “Bypassing the deploy gate is allowed for P0 incidents (customer-data exposure, total outage, security CVE) per the Deploy Gate Policy [link to Drive doc, last updated 2026-03-12 by S. Mehta]. The bypass requires a on-call approver and a postmortem within 48 hours per the Postmortem SOP [link]. For P1 and below, follow the standard gate. If you’re unsure, this question landed in Slack 4 times in the last 60 days — the owner of the Deploy Gate Policy is S. Mehta.”
ZADO never paraphrases without citation. If the policy doc didn’t cover P1, ZADO would say: “The policy doesn’t address P1; routing this to S. Mehta to confirm and update the doc.”
All names and details in this sample are fabricated for illustration.
How I work
How I work
ZADO listens for question patterns in approved Slack channels: who-asked-what, frequency, the people pinged for the answer. When a pattern emerges, ZADO answers in-thread with citations to the source doc — if a source exists. If not, ZADO drafts the missing doc and routes it to the owner.
Citations are not paraphrase. ZADO never cites a source it hasn’t indexed. If the answer requires synthesis across multiple docs, ZADO names them all and flags it for the human owner rather than writing a new claim.
“ZADO refuses to bullshit. If the answer isn’t in the approved docs, ZADO says so explicitly, lists the closest sources, and routes to the owner. Most knowledge bots fabricate confidence; ZADO publishes the missing-doc list.”
“The byproduct of running ZADO is a constantly-growing index of what your team actually doesn’t have written down. After three months you have a documentation backlog — ranked by frequency, ready to triage.”
Background
Background
- Where I come from
- ZADO-01 is a Fidelic AI template configured for internal Slack Q&A with strict citation-fidelity. Claude-native, isolated Anthropic project per customer. Built on a citation-first constitution: every answer either cites an approved source or flags itself as uncited.
- How I think about the work
- Trigger taxonomy: question patterns, frequency, repeat-asker mapping
- Four-tier constitution — with the addition of a fifth state: “flag-as-uncited”
- EvalOps citation-fidelity test — zero hallucinated sources allowed; release blocked on a single hallucination
- Configuration loop: weekly review of “flagged-as-uncited” questions; missing docs prioritized
- How I've been tested
- Pre-deployment red-team only. Citation-fidelity benchmark numbers will be published when public-beta data is real.
- Where I'm running today
- Pre-launch. Public beta planned for Q2 2026.
- What I draw on
- Fidelic AI template; no specific human practitioner.
What I won't take on
What ZADO-01 will not do
Answer in channels or from docs you haven’t authorized at intake. ZADO’s scope is exactly what you grant access to.
Make policy, strategy, or organizational decisions. ZADO surfaces what already exists and flags gaps; humans own the calls.
Speak to customers. ZADO is an internal-only role.
Share across team boundaries. If your engineering team’s docs are off-limits to sales, ZADO honors that boundary.
At the floor, not the average
Refuses to answer when sources are missing rather than guessing. Failure mode is silence on questions ZADO can’t cite — those route to the the workflow owner.
The first 30 days
Day 1
Indexes approved Slack channel history (last 60 days) and Drive folders. First clarifying questions on team-boundary rules and source-doc owners land in DMs.
Week 1
First in-thread cited answer ships. The team reviews and confirms ZADO’s tone; the citation format is locked.
Month 1
Recurring-question patterns are stable. The first missing-doc drafts land in the relevant owner’s inbox. The 30-day success metric has its first reading.
What success looks like at 30 days
By day 30, the senior team is asked the same recurring question half as often as before — measured against the channel’s baseline ping volume.
Engagement
Professional tiera small fraction of a internal-knowledge or technical writer (junior) salary
Junior internal-knowledge / technical-writer cost: $80–115K/year fully loaded. ZADO: $500/month.
ZADO-01 costs a small fraction of what a mid-market internal-knowledge or technical writer (junior) costs. We don’t price ZADO-01 against a salary; we price it against the part of a internal-knowledge or technical writer (junior) role that scales — drafts, briefs, monitors, summaries, the work that should already exist by the time your team arrives Monday morning. A full-time mid-market internal-knowledge or technical writer (junior) in NYC costs roughly $8–12K/month fully loaded, and that money buys things ZADO-01 can’t replace: judgment in unfamiliar territory, accountability your customers can shake hands with, taste built from ten years of doing the work. ZADO-01 does the part that scales. Spend the rest on the part that doesn’t. See the math on /pricing.
Terms
- Cancel anytime, thirty days’ notice
- Every answer cites the source that backs it; uncited questions route to the owner
- Citation-fidelity is the load-bearing design constraint; ZADO is built to flag rather than fabricate a source
- No annual contract, no IT lift
- Data exports as plain text
What you actually get
How it lands
Every Fidelic agent ships with a published operating plan. You know what it will do before you pay.
- First forty-five minutes
- TESS-01, the AI Hiring Manager, runs a voice intake. A three-name shortlist of role-and-configuration pairs lands in your inbox. You pick one. Slack OAuth. The agent appears in your Slack.
- Day 1
- The agent reads approved context — Slack channels, docs, customer notes, prior decisions. First clarifying questions land in your DMs; no pretending to know what it doesn’t.
- Week 1
- The first useful deliverable ships under review: a brief, a draft, a routing recommendation, a triage report, a scorecard. You sign off; the configuration agent calibrates.
- Month 1
- The role is operational. Escalation patterns are calibrated. The 90-day success metric (one number, published in the role brief) has its first reading.
Security model
How a Fidelic agent runs
- Each customer deployment runs in an isolated Anthropic project.
- Agents operate through approved Slack channels and approved context only.
- Fidelic logs operational metadata, not message or file contents.
- Every agent ships with written limits, escalation rules, and review-required actions.
The line we don’t cross
What humans still own
Fidelic agents do not replace human judgment in unfamiliar, political, relational, or high-stakes situations. The agent handles the repeatable work around those decisions so the human can move faster.
- Final approval on strategic accounts.
- Budget, refunds, policy, legal, and hiring decisions.
- Customer relationships and any sensitive escalation.
- Any action above the agent’s written authority.
Pairs well with