Skip to content

Regulated teams

What it said on that date.

New versions take over. Old ones are kept and dated, never deleted.

01

The procedure moved, quietly.

A reviewer asks what the rule was on a date. The wiki only has today’s page.

No dated text

Old wording is gone. Who changed it is a guess.

Conflicts get blended

Two procedures disagree, and a tool picks one confident sentence.

Derived text leaks

A summary shows a line from a source the reader cannot open.

Before

Today’s page is the only page. A disagreement is hidden. A lesson shows more than the source allows.

After

You open the procedure as of a date. Both sides of a conflict stay visible. Derived text carries the same limit.

02

The loop for this team.

Bring the procedure in. Keep every version. Show conflicts. Derive nothing beyond the source.

Arrival is checked

Garbled scans are held back until fixed. Repeated passages count once.

Sources stay original

Sources are never rewritten. Every answer traces to its origin.

Anyone can correct

Anyone can correct what is wrong, and their edit wins. Unclear calls are checked first.

03

Date, text, and who changed it.

You can see what a procedure said on a date and who changed it.

Never deleted

New versions take over. Old ones are kept and dated, never deleted.

Who changed it

Each version carries the person and the date.

As it stood

You can open the line as it stood on a date, not only as it stands now.

One procedure · illustrative example
  1. 12 March

    Refunds are processed within 30 days.

    Changed by the support lead
  2. 3 January

    Refunds are processed within 14 days.

    Kept, dated, still readable

04

Contradictions stay surfaced.

When sources disagree, you see both sides and where each came from.

Both sides

One page says refunds take 14 days, three others say 30. Both remain.

Nothing blended

Nothing is blended into a confident wrong answer.

Grounded lessons

A generated lesson or quiz stays tied to the exact sources it came from.

05

Isolation, and where data sits.

Fully private, partly shared, or open. Shared SaaS, or hybrid cloud with your data plane inside your organization.

Three ways to share

Private spaces, partly shared patterns with confidential sources, or open across your organization.

Combined roles

Someone with several roles gets the combined access of all of them.

Shared SaaS or hybrid

Shared SaaS with region-pinned data residency, or hybrid cloud with your data plane inside your organization. The control plane is shared either way.

Shared SaaS or hybrid cloud

Shared SaaS

Cluesora cloud · region-pinned

  • Control plane — shared
  • Data plane — your content and the map

Hybrid cloud

Cluesora cloud

  • Control plane — shared, run by Cluesora

Inside your organization

  • Data plane — your content and the map
  • Encrypted in transit and at rest
  • Activity logged
  • SSO · SAML · OIDC · SCIM on Pro

06

Permissions all the way down.

Anything derived from a source carries that source’s permissions.

Lessons and answers

A summary, quiz, illustration, or Teammate answer never shows more than the source allows.

Agents wear your badge

An agent gets exactly the permissions of the person who connected it.

Encrypted and logged

Encrypted in transit and at rest. Activity is logged.

Sign-in

SSO, SAML, OIDC, and SCIM are standard.

07

What this team uses.

Corpus holds the dated procedure. Everything else inherits its limits.

Corpus

Versions, contradictions, owners, and the exact line on every answer.

Fathom

Lessons and interviews that stay tied to sources and permissions.

Teammate

Answers when asked, follows each person’s permissions, and does not monitor conversations.

08

What to measure.

Traceability, isolation, and honesty about what is not solved yet.

The date is open

Whether you can open what the procedure said on a date, and who changed it.

Conflict is visible

Whether disagreements stay in view.

Derived stays limited

Whether a lesson or answer shows only what the source allows.

Limits are named

Whether a control you need is written on the Security page, not assumed.

Questions people ask.

Can we see a procedure as of a past date?

Yes. New versions take over. Old ones are kept and dated, never deleted.

What if two approved pages disagree?

You see both sides and where each came from. Nothing is blended.

Can a generated lesson show a restricted line?

No. Anything derived carries the source’s permissions all the way down.

Can data stay inside our network?

Yes. With hybrid cloud your data plane stays inside your organization; the control plane is shared. The shared SaaS has region-pinned data residency.

Is every governance question solved?

No. Being production-ready does not mean that. We name the limits on the Security page.

Read the walls.

Isolation, permissions all the way down, hybrid or hosted, and the limits we name.