Applied AI

Company answers, with sources

Help employees find answers in the information they can access

The working day, reconsidered.

Useful answers sit across documents and operational records. Employees need a way to find them without exposing information outside their role.

Connecting the pieces.

Connect approved sources to a searchable knowledge index. Retrieve information using the employee’s permissions, then generate an answer linked to its sources.

Download design brief ↓
  1. 1Ask
  2. 2Find the source
  3. 3Answer

What is our delivery policy? Search checks Word documents, PDFs, database records, and the company wiki, then retrieves Delivery policy PDF, section 2. Standard orders ship within two business days after confirmation. The answer cites that source.

Only searches documents the employee can access.

Reference architecture

From company knowledge to a trusted answer

Two connected flows keep information current and answers scoped to each employee

Permission-aware by design
1

Prepare the knowledge

Runs when approved sources change

  1. Company sources

    Policies, team documents and approved business records

    Source owners control access
    Sync changes

  2. Prepare knowledge

    Extract text, split documents and retain ownership and source links

    Updates and deletions included
    Index with permissions

  3. Searchable knowledge

    Store passages, embeddings and document access rules together

    PostgreSQL + pgvector
Indexed knowledge feeds the permission check
2

Answer an employee’s question

Runs for every question

  1. Identify the employee

    Validate sign-in and resolve current team and role permissions

    Keycloak / company SSO
    Verified request

  2. Find permitted evidence

    Check source access before returning relevant passages

    Access checked on every request
    Allowed passages only

  3. Prepare a grounded draft

    Give the model the question and retrieved evidence to compose an answer

    Approved model endpoint
    Answer + citations

  4. Let people verify

    Show the answer with source links, or explain when evidence is missing

    Employee workspace
When access changes

Recheck permissions and invalidate stale access before serving evidence

When evidence is weak

Ask for clarification or return no answer instead of guessing

What operators can review

Permission decisions, retrieval traces and quality checks with agreed retention

Decisions that matter

Check access before retrieval

Carry source permissions into the index and apply access filters before any text reaches the model

Let people inspect the answer

Link claims to source passages so employees can check context and document freshness

Make uncertainty useful

When evidence is missing or conflicting, ask for clarification or say that the answer is unavailable

What we’d verify

  • Confirm a restricted document cannot appear in another role’s answer
  • Remove a source permission and verify retrieval respects the change
  • Ask an unsupported question and confirm the assistant does not invent an answer

Ready for handover

Code, configuration, operating notes, and knowledge transfer—agreed as part of the scope

See our delivery approach ↗

Bring us your version of the challenge.

We’ll look at the context, the people and the systems together.

Let’s talk