Demos and examples use a fictional sample company, Alderwave Systems.
Company Knowledge

Your company’s memory, ready for every AI tool you use

Policies, procedures, decisions and know-how: approved, kept current, and kept after people leave. Use it on its own, with any AI assistant, or as part of your Delegenix outcomes.

Where company knowledge fits

It’s one of the five parts of your AI factory, and it works on its own too.

What your company knows

Policies, procedures, decisions, terminology and the know-how that lives in people’s heads.

e.g. collection policy, refund rules, release checklist

Used by every outcome

Outcome recipes apply your rules from here, so every result follows your current policy.

e.g. “no reminder while a dispute is open”

Works with any AI tool

ChatGPT, Claude, Gemini or your own assistants can use the same approved knowledge.

One source of truth instead of pasted documents

Or use your own

Already have a knowledge tool? Delegenix outcomes can use it instead.

No migration required

Why company knowledge changes the result

Without company knowledgeWith Company Knowledge
“5 invoices are overdue, $69,000 in total. Follow up with all of them.”“Route Meridian Fabrication’s $24,800 dispute to its owner instead of chasing. Reconcile Oakmere’s claimed transfer and wait for Harborpoint’s 21 Oct promise first. Use the approved reminder wording for the rest (POL-FIN-AR-04).”
“Offer the customer a refund.”“Standard window is 30 days; day 31–60 exceptions need a team lead’s approval (POL-CS-REFUND-03). Email draft routed for approval.”
“Fix the oldest issues first.”“Release 3.18.2 passed CI, but preview errors rose from 0.4% to 3.1%. Draft a rollback review for the on-call engineer (POL-ENG-INC-05).”

Knowledge ingestion isn’t knowledge governance

Approved sources only

You choose the documents; drafts stay out.

Named owners

Each document has an owner; answers cite the version.

Freshness

A changed policy is re-synced and re-tested.

Roles

With Full SaaS, roles decide who can use which knowledge. How roles work

What every piece of knowledge carries

FieldWhy it mattersExample
SourceEvery answer can point to where it came fromCollection policy, page 2
AuthorityApproved policy, documented practice or inferred: an inferred practice never silently becomes policyApproved policy
Version and effective dateThe rule that applied at the time is the one usedPOL-FIN-AR-04 v4, from 1 Oct 2026
Who can use itRoles decide access (Full SaaS)Finance and account owners
Last reviewedStale knowledge is flagged, not trustedReviewed 1 Oct 2026 by the finance lead

Capturing what people know

Much of how a company works lives in people’s heads. We capture it through short interviews and decision logs, your team approves it, and it stays when people move on. Knowledge that was never written down can’t be recovered, so we start with the processes that matter most.

Keeping it current: upload, replace, retire

1. Upload the approved version

The policy owner uploads the approved replacement.

2. We process and check it

Delegenix processes it, tracks the version and checks retrieval.

3. Retire the old one

A retired document stops being retrieved.

Your team approves the content; Delegenix runs the rest. One company memory serves every outcome and every AI tool you connect.

Start with the knowledge one outcome needs.

Hosted by us, or in your own cloud account.