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.

Request a demoSee 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 deterministic ontology, a network of methods and the experience gained from applying them into a living knowledge graph of the context of use, 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 context layers in the graph, and we keep them current.

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

Managed and deterministic. Defines which concepts exist and how they relate, from context of use to metric.

L2Step 2 · maintainedMethods

A network of methods for research and evaluation, linked to the ontology.

L3Step 2 · maintainedExperience

Evidence from applying the methods in your organization, project by project.

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.

10 questions the graph answers →02Human-centered Product Development

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

7 questions the graph answers →03AI-augmented Engineering

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

6 questions the graph answers →
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, methods and experience. Approval stays with people. Teams decide on the same evidence, and agents ask instead of assuming.

REQ-114 · Braking distance on wet roadsAgent · awaiting approvalCompleted
AI SUGGESTION · TC-31Create test case “Braking distance on wet roads”.
PROVENANCEREQ-114L1 OntologyFMEA chassisL2 MethodLessons P-22L3 Experience
TC-31 verified · M. Berg. The node is now part of the graph.

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