No dated text
Old wording is gone. Who changed it is a guess.
Regulated teams
New versions take over. Old ones are kept and dated, never deleted.
01
A reviewer asks what the rule was on a date. The wiki only has today’s page.
Old wording is gone. Who changed it is a guess.
Two procedures disagree, and a tool picks one confident sentence.
A summary shows a line from a source the reader cannot open.
Today’s page is the only page. A disagreement is hidden. A lesson shows more than the source allows.
You open the procedure as of a date. Both sides of a conflict stay visible. Derived text carries the same limit.
02
Bring the procedure in. Keep every version. Show conflicts. Derive nothing beyond the source.
Garbled scans are held back until fixed. Repeated passages count once.
Sources are never rewritten. Every answer traces to its origin.
Anyone can correct what is wrong, and their edit wins. Unclear calls are checked first.
03
You can see what a procedure said on a date and who changed it.
New versions take over. Old ones are kept and dated, never deleted.
Each version carries the person and the date.
You can open the line as it stood on a date, not only as it stands now.
Refunds are processed within 30 days.
Changed by the support leadRefunds are processed within 14 days.
Kept, dated, still readable04
When sources disagree, you see both sides and where each came from.
One page says refunds take 14 days, three others say 30. Both remain.
Nothing is blended into a confident wrong answer.
A generated lesson or quiz stays tied to the exact sources it came from.
05
Fully private, partly shared, or open. Shared SaaS, or hybrid cloud with your data plane inside your organization.
Private spaces, partly shared patterns with confidential sources, or open across your organization.
Someone with several roles gets the combined access of all of them.
Shared SaaS with region-pinned data residency, or hybrid cloud with your data plane inside your organization. The control plane is shared either way.
06
Anything derived from a source carries that source’s permissions.
A summary, quiz, illustration, or Teammate answer never shows more than the source allows.
An agent gets exactly the permissions of the person who connected it.
Encrypted in transit and at rest. Activity is logged.
SSO, SAML, OIDC, and SCIM are standard.
07
Corpus holds the dated procedure. Everything else inherits its limits.
Versions, contradictions, owners, and the exact line on every answer.
Lessons and interviews that stay tied to sources and permissions.
Answers when asked, follows each person’s permissions, and does not monitor conversations.
08
Traceability, isolation, and honesty about what is not solved yet.
Whether you can open what the procedure said on a date, and who changed it.
Whether disagreements stay in view.
Whether a lesson or answer shows only what the source allows.
Whether a control you need is written on the Security page, not assumed.
Yes. New versions take over. Old ones are kept and dated, never deleted.
You see both sides and where each came from. Nothing is blended.
No. Anything derived carries the source’s permissions all the way down.
Yes. With hybrid cloud your data plane stays inside your organization; the control plane is shared. The shared SaaS has region-pinned data residency.
No. Being production-ready does not mean that. We name the limits on the Security page.