Human-centered context graph for organizations, products and AI agents

Decisions need context.
So do agents.

rygg makes your organization’s knowledge about its users explicit: one maintained graph for the whole organization, for product development and for AI agents.

Find your starting pointSee the use cases

Teams and agents have strength. rygg gives them support and direction.

Your organization knows a lot about its customers and users. That knowledge sits in people’s heads and in reports nobody opens again. Departments work with different pictures, product decisions rest on assumptions, and AI agents can read neither heads nor forgotten reports.

rygg is Swedish and Norwegian for backbone. It connects a managed ontology with your context of use and the evidence about it into a living knowledge graph, gathered in the field, validated against HCRD standards and continuously maintained.

The symbol shows the core: AI contributions, framed and verified by humans.
Three layers

One graph of what your organization knows

The graph is built in two steps. You license a managed ontology. Research, evaluation and evidence from your organization then become the context and evidence layers of the graph, and we keep them current.

  1. Step 1License the managed ontologyThe concepts and relations of the context of use and the method network, defined and maintained by us.
  2. Step 2Add research, evaluation and evidenceFrom your organization, step by step. The result is two maintained layers in your graph: context and evidence.
L1Step 1 · licensedOntology

Managed and deterministic. Defines which concepts exist and how they relate, from context of use to metric. Comes with our method network.

L2Step 2 · yours, maintainedContext

Your context of use: user groups, tasks, conditions, needs and requirements, gathered in the field or taken from what you already know.

L3Step 2 · yours, maintainedEvidence

What was tested, decided and measured: findings, decisions, metrics. Each with a status that shows what is evidence and what is assumption.

From context of use to metric

Every metric traces back to an observation

Every requirement traces back to an observed need, every solution to a requirement, every evaluation to a decision and every metric to a finding. Every node is a Markdown file in the Open Knowledge Format (OKF) v0.2, readable by people and agents.

  1. 01Context of useWho works on what, under which conditions, and where does the work break down?
    • Conditions
    • User groups
    • Tasks
    • Current scenarios
  2. 02User requirementsWhat do the user groups need?
    • Needs
    • User requirements
  3. 03SolutionWhich elements meet the requirements, and which decisions shape them?
    • Design solutions
    • Design decisions
  4. 04EvaluationHow is it tested, and what was confirmed or contradicted?
    • Evaluation measures
    • Evaluation findings
  5. 05MetricsHow does the organization see effectiveness, efficiency and satisfaction?
    • Metrics
Use cases

One graph, three uses

All use cases
01Human-centered Enterprise

A shared model of what the organization does, for whom and why, from apprentice to board.

Explore the 10 questions 02Human-centered Product Development

Activities and decisions in product development focused on outcomes for users, and through them on economic results.

Explore the 7 questions 03AI-augmented Engineering

Agents in engineering, documentation and service that ask the graph instead of making assumptions.

Explore the 6 questions
How rygg works

Every contribution shows where it comes from

People and agents work on the same graph. Every statement and every suggestion is backed by nodes from ontology, context and evidence. Approval stays with people. Teams decide on the same evidence, and agents ask instead of assuming.

How rygg works in detail
Suggested by agentday 1 · coverage agentLinked to sourcesREQ-114FMEAP-22day 1Reviewed · M. Bergday 2 · edited titleVerifiedday 2 · now part of the graphUsed in agent answer · REQ-120Used in agent answer · REQ-140
The life of one node, from suggestion to use. Sample data.
Offer

Start with evidence. Grow into a graph your organization can use.

See the offer
01EvidenceWhere the graph starts

Research and design to HCRD standards. Results are documented so they can become part of a graph.

Project02PilotTry rygg on your own context

Four to eight weeks, one slice of your organization, one product line or one agent task as a graph.

4 to 8 weeks03GraphYour context of use, maintained

A maintained domain model of your context of use, validated against HCRD standards with every release.

Subscription, 12 months minimum04Context Layerrygg in operation, measured by results

We run the graph as a knowledge layer for your agents and embed Research & Design Engineers in your teams.

Framework agreement, 12 months minimum