# Influences and Credit

Domain Context Modeling is a synthesis effort. It adapts useful ideas from existing disciplines into a practical context system for AI-forward product work.

The claim is not that these ideas are new. The claim is that product teams need a clearer way to combine them so humans and AI agents can share product meaning.

## Object-Oriented UX and ORCA

Object-Oriented UX, associated with Sophia Prater and the ORCA framework, is a major influence. OOUX provides a practical way for designers to model objects, relationships, calls to action, and attributes before designing screens.

Domain Context Modeling builds on that object-first instinct, but expands the concern toward:

- Larger domain boundaries
- Agent context
- Sources of truth
- AI action boundaries
- Cross-team semantic consistency

## Domain-Driven Design

Domain-Driven Design contributes several powerful ideas:

- Ubiquitous language
- Bounded contexts
- Subdomains
- Entities
- Value objects
- Aggregates
- Domain events
- Context maps
- Published language

Domain Context Modeling uses DDD selectively. The goal is not to make designers learn software architecture jargon. The goal is to borrow concepts that help teams clarify meaning, prevent drift, and make better product decisions.

## Information Architecture and Conceptual Modeling

Information architecture and conceptual modeling inform the way this framework treats product meaning as something that can be structured, named, related, and navigated.

Relevant concerns include:

- Mental models
- Object relationships
- Taxonomy
- Navigation structure
- Labeling systems
- Conceptual clarity

## Service Design

Service design contributes the habit of connecting visible experience to backstage actors, systems, policies, handoffs, and evidence.

This matters for agentic products because AI behavior often crosses the boundary between frontstage user interaction and backstage system action.

## Narrative And Scenario-Based Design

Narrative, scenarios, and story-centered product thinking influence Story Mode. A concrete multi-actor story can reveal motivation, stakes, objects, workflows, handoffs, failure points, and outcomes before a team knows how to model the domain abstractly.

Domain Context Modeling uses story as an entry path and stress test, not as decorative product lore. The story should improve the domain model, and the domain model should make the story more accurate.

## Design Systems

Design systems show how shared primitives can help teams scale consistency.

Domain Context Modeling applies a similar idea to meaning:

- Design systems organize interface consistency.
- Domain context systems organize meaning consistency.

The two should eventually connect. Components should know what concepts, states, permissions, and actions they represent.

## Context Engineering

Context engineering contributes the AI-native concern: what information should enter an AI model or agent's context, how should it be structured, and what should be omitted, retrieved, summarized, verified, or governed?

Domain Context Modeling treats domain concepts as reusable context infrastructure, not just documentation.

## Agent and Tool Schema Thinking

Agentic systems need structured access to tools, resources, instructions, and constraints. Protocols and schema-driven systems influence this framework's attention to:

- Tool descriptions
- Action boundaries
- Evidence requirements
- Source-of-truth rules
- Agent-readable context packets

## What This Is Not

Domain Context Modeling is not:

- A replacement for OOUX
- A replacement for DDD
- A full software architecture method
- A generic prompt engineering trick
- A design-system methodology
- A claim to have invented domain modeling

## What This Is

Domain Context Modeling is:

- A bridge between product meaning, UX architecture, and AI context
- A lightweight way to define domain concepts for humans and agents
- A practical artifact system for better specs, flows, IA, agent behavior, and implementation context
- A field guide that should be improved through real use
