OrgForge: A Multi-Agent Simulation Framework for Verifiable Synthetic Corporate Corpora
Organizations: Independent Researcher
Abstract
Building and evaluating enterprise AI systems requires synthetic organizational corpora that are internally consistent, temporally structured, and cross-artifact traceable. Existing corpora either carry legal constraints or inherit hallucination artifacts from the generating LLMs, silently corrupting results when timestamps or facts contradict across documents and reinforcing those errors during training. We present OrgForge, an open-source multi-agent simulation framework that enforces a strict physics-cognition boundary: a deterministic Python engine maintains a SimEvent ground-truth bus while LLMs generate only surface prose. OrgForge simulates the organizational processes that produce documents, not the documents themselves. Engineers leave mid-sprint, triggering incident handoffs and CRM ownership lapses. Knowledge gaps emerge when under-documented systems break and recover through organic documentation and incident resolution. Customer emails fire only when simulation state warrants contact; silence is verifiable ground truth. A live CRM state machine extends the physics-cognition boundary to the customer boundary, producing cross-system causal cascades spanning engineering incidents, support escalation, deal risk flagging, and SLA-adjusted invoices. The framework generates fifteen interleaved artifact categories traceable to a shared immutable event log. Four graph-dynamic subsystems govern organizational behavior independently of any LLM. An embedding-based ticket assignment system using the Hungarian algorithm makes the simulation domain-agnostic. An empirical evaluation across ten incidents demonstrates a 0.46 absolute improvement in prose-to-ground-truth fidelity over chained LLM baselines, and isolates a consistent hallucination failure mode in which chaining propagates fabricated facts faithfully across documents without correcting them.
Figures & tables
| Category | Artifacts | SimEvent types |
|---|---|---|
| Internal coordination | ||
| Slack | Dept channels, DMs, digital-hq, random | async_question , 1on1 , org_collision , watercooler_chat |
| JIRA | Tickets + per-comment files | ticket_progress , jira_ticket_created |
| GitHub | PRs with review comments | pr_review |
| Confluence | Genesis, postmortems, design docs, ad-hoc | confluence_created |
| Zoom | Timestamped meeting transcripts (.md) | design_discussion |
| Artifact type | Count |
| Slack threads | 3,158 |
| Email (all) | 552 |
| Confluence pages | 474 |
| JIRA tickets | 328 |
| Zoom transcripts | 193 |
| Pull requests | 53 |
| Parameter | Detail | Value |
| Organizational scale | ||
| Employees | Active at Day 0 | 41 |
| Vendor sources | Seeded at genesis | 7 |
| Customer accounts | Seeded at genesis | 8 |
| Lifecycle events | ||
| Departures (in-simulation) | Days 1–60 | 4 |
| Metric | OrgForge | Chained | Parallel |
|---|---|---|---|
| Entity agreement | |||
| Prose-SimEvent fidelity | |||
| Incidents evaluated | 10 | 10 | 10 |
| Artifacts per incident (mean sd) |
| Artifact type | (composite) | |||
|---|---|---|---|---|
| JIRA ticket | ||||
| Pull request | ||||
| Confluence page | ||||
| Mean |
| Evaluation Surface | Representative Query | SimEvent bus | CRM cascade | Email signals | Knowledge recovery | Departure cascade | Graph dynamics | Voice cards |
|---|---|---|---|---|---|---|---|---|
| Longitudinal narrative reconstruction | “Trace the ownership history of the TitanDB domain from Day 0 to Day 18.” | ✓ | ✓ | ✓ | ✓ | |||
| Cross-system causal cascade | “Why does the Acme Corp invoice include a $200 SLA credit?” | ✓ | ✓ | ✓ | ||||
| Verified absence reasoning | “Which customers were affected by the Day 8 incident but never contacted support?” | ✓ | ✓ | |||||
| Actor-scoped epistemic reasoning | “Could Morgan have known the Acme deal was at risk on Day 14 at 14:00?” | ✓ | ✓ | ✓ | ||||
| Multi-department strategic synthesis | “Synthesize the Acme relationship from Engineering, Sales, and Support perspectives.” | ✓ | ✓ | ✓ | ||||
| Process compliance auditing | “Were all PRs in sprint 3 reviewed before merge?” | ✓ | ✓ |
Synthetic Data Generation for Language Models
Synthetic data generation for language models creates artificial text, tasks, and interaction traces to train or evaluate models.
See all 293 papers