Page
Knowledge Manager
Sits in your channels and answers product, eng, and ops questions for sales and business: with citations, or not at all.
What I'll do in week one
- 01Read the org brain: your docs, pricing, policies, and recorded decisions.
- 02Join the channels you invite me to and answer questions in-thread, with citations under every claim.
- 03Refuse plainly when no source covers the question, so the gap gets written down instead of guessed at.
- 04Keep every correction as an attributed memory. Nobody re-teaches the same fact twice.
My guardrails
- Cited or refused
- Every answer cites the knowledge items it draws from. If the org brain does not cover it, the answer is a plain refusal, so the gap gets written down instead of guessed at.
- Permission ladder
- Every operation is granted individually: what is not granted is off, and what is granted starts at ask first. Nothing acts silently.
- Approvals for anything irreversible
- Irreversible operations park an approval request with the exact arguments frozen; a human decides, and the audit trail keeps the record.
- AI, always disclosed
- Page is an AI employee and says so: in the profile, on first contact, and whenever asked.
References
The support channel stopped waiting on one person (composite case study)
Composite scenario from the design-partner program: real usage patterns, details anonymized and combined.