AI / ORGANIZATIONAL CONTEXT SHUGYO

Give AI a model of your organization.

General AI tools do not know your processes or how your business objects relate. Shugyo supplies that context through an ontology linked to your company data, then uses the model to answer operational questions.

AI assistant
Grounded
YOU
How many invoices are stuck in verification more than 5 days?
Context attached from ontology
Invoice Flow · verification Client SLA
23 invoices stuck — worth $182K
Traceable · invoices ⋈ flow_state · BigQuery
THE CONTEXT PROBLEM 01

AI needs your operating context.

A general assistant can retrieve text, but it cannot infer the definitions and relationships specific to your company. Without a shared model, it does not know:

  • What "project" means in your organization
  • How an invoice connects to a client
  • How your approval workflow runs
  • Where work gets stuck and why

Shugyo gives the AI an approved organization model.

AI without context

"I don't have access to your invoice data. Common causes include approval and payment delays."

General answer without company data
AI with structured context

"23 invoices worth $182K are past the 5-day verification SLA. Most are assigned to two reviewers."

Uses your approved model
CONTEXT AS INFRASTRUCTURE 02

Connectors do not supply a shared data model.

An agent with plugins searches each connected system when a question arrives. That can handle a lookup in one source. Questions across systems also need agreed object definitions and relationships.

A Agent with direct connectors
Agent + PLUGINS every question CRM Email Docs Tickets Sheets
The agent searches each tool for every question. Each source is searched separately, without typed links between systems. The retrieved context can vary between calls.
B Shugyo organization model
AI model APPROVED MODEL ONTOLOGY / DIGITAL TWIN CRM Email Docs Tickets Sheets
The ontology attaches the relevant definitions and relationships. The query can follow typed relationships across the dataset. Each query uses the same approved model.
ONTOLOGY 03
ORGANIZATION MODEL

Define the objects and relationships in your organization.

An ontology describes the objects in your company, their attributes, and the relationships between them.

What ontology contains
ElementDescriptionExample
Objects Things that exist Invoice, Client, Employee, Project
Attributes Properties of objects Amount, status, due date, owner
Relationships How objects connect Invoice belongs to Client
Flows How objects move Draft > Verified > Sent > Paid
Why ontology matters for AI
01

A business-shaped model

Start with leader context, business terms, relationships, and authority. When a structured warehouse path is useful, Shugyo can map BigQuery tables and typed JOINs into the approved ontology.

02

Injected into the AI prompt

A compact ontology snapshot goes into the agent's system prompt. It guides the SQL the agent writes and keeps queries within your approved model.

03

A common language

The ontology gives your data and the AI the same vocabulary. A question about "delayed invoices" uses your definition of an invoice and its due date.

04

Consistent answers

Each question uses the same approved model, so a metric keeps the same definition across answers.

DIGITAL TWIN / CURRENT COMPANY DATA 04

Query your organization as a model.

The ontology is the approved model of the business. The digital twin connects that model to useful evidence. In BigQuery deployments, entities can map to tables and relationships to typed JOINs that the AI can traverse.

  • Entities: records such as Invoice FV/2024/001 and Client "Company ABC," each backed by a table
  • Relationships: typed JOINs between entities, with cardinality
  • History: changes captured by dbt models and source audit columns

The twin records what happened in the source systems.

BELONGS_TO BELONGS_TO BELONGS_TO Client Company ABC Invoice FV/2024/001 Meeting 12.01 Email 15.01
AI CAPABILITIES 05

Ask operational questions in plain language.

Natural language queries

Ask a plain-language question about your connected data.

  • How many invoices are stuck in verification for more than 5 days?
  • Which clients have the longest onboarding time?
  • Where is delivery delayed but sales promised on-time?

Shugyo writes the query and returns the supporting records.

Anomaly detection

Flag process times and patterns that depart from an approved baseline.

  • A process taking longer than usual
  • Unusual patterns in approval workflows
  • Deviations from historical baselines

Alerts identify the process, baseline, and size of the deviation.

Trend analysis

Track how an approved metric changes over a selected period.

  • How has average invoice cycle time changed over two quarters?
  • Which clients' onboarding times are trending up?

The trend uses the same metric definition for each period.

Process recommendations

AI suggests process changes based on measured bottlenecks.

  • Identifies the steps causing the most delay
  • Quantifies the cost of inefficiencies
  • Recommends specific changes with projected impact

Review the evidence and projected impact before approving a change.

HOW IT WORKS 06

How Shugyo answers a question.

The ontology maps the terms in your question to the company model. Shugyo queries the corresponding data in the digital twin and returns the answer with its trace.

Each answer links back to source data.

Your question
Why are invoices slow? Ask in plain language without writing SQL.
Ontology
Understands the terms Uses your definitions of invoice and slow, including the object, SLA, and process flow.
Digital twin
Queries the actual data Traverses relationships and aggregates across the full dataset in BigQuery. invoices JOIN flow_state JOIN sla
Answer
Verification: 4.2 days avg The 2-day SLA is exceeded in verification, with links to the affected records.
ANSWER TRACE 07

Inspect the path behind each answer.

Shugyo exposes the evidence and calculation behind an answer. You can inspect:

  • Which data sources were used to reach the answer
  • What query was executed against the twin
  • How the calculation was performed
  • What assumptions the calculation used

Review the evidence and record your feedback.

Reasoning trace Answer #4291
01 Sources
invoices, flow_state, sla_policy 3 tables in BigQuery
02 Query
SELECT stage, AVG(days) ... GROUP BY stage
03 Calculation
Mean dwell time per stage, last 90 days
04 Assumptions
Business days; drafts excluded
RESPONSIBLE AI 08

Keep people in charge of decisions.

AI can propose an answer or a process change. A person reviews the source evidence and decides whether to act.

Source trace

Each conclusion links to its source data and query.

Human in the loop

A person must approve critical decisions proposed by the AI.

Inspectable logic

Ask why to inspect the logic behind a result.

Named decision owners

Named owners review AI-supported decisions and monitor their outcomes.

WHAT MAKES OUR AI DIFFERENT 09

Compare the context behind each answer.

Dimension General AI assistant Shugyo.ai
Context General model context Your approved organization model
Source Model training data Your connected company data
Reasoning Answer only Sources, query, calculation, assumptions
Interface Technical query tools Plain-language questions
System Separate point tools One organization model
SECURITY & PRIVACY 10

Your data stays yours.

You retain control of the company data used by the model.

01

Data ownership

You retain ownership of your data.

02

Model training

We do not use your data to train models.

03

Access control

Configure which users access which data. Role-based permissions.

04

Encryption

Data encrypted at rest and in transit.

05

Compliance

SOC 2 Type II in progress. AI Act ready.

REQUEST EARLY ACCESS

See whether Shugyo fits your organization.

Bring an operational question and the systems that hold the relevant data. We will show how Shugyo models the terms, runs the query, and exposes the supporting records.