# SMR Orchestration

Canonical URL: https://smrorchestration.com/
Publication status: published
Deployment status: active
Version: 2.2.0
Last modified: 2026-08-17
Managed by: LJP Asset Group LLC
Publisher: https://ljpassetgroup.com/
Contact: support@ljpassetgroup.com

## Governing question

What sequencing dependencies should a program discussion make visible without claiming project authority?

## Direct answer

It can map handoffs and decision dependencies as a semantic program view, while leaving licensing, engineering, commissioning, procurement, construction, and operating decisions to the parties with actual authority.

## Why it matters

Advanced-reactor deployment involves distinct public, commercial, technical, and regulated tracks that should not be represented as one controllable workflow.

## Definition

A semantic framing for sequencing conversations across a small-modular-reactor program without performing or directing the work.


## Capability relationships

It is closest to Reactor OS because both concern coordination language, but neither has plant, project, regulatory, or commercial authority.

## Standards and authority context

NRC describes separate licensing processes for advanced reactors. LJP uses that public context to preserve the distinction between a semantic program map and regulatory action.
- Advanced Reactors — U.S. Nuclear Regulatory Commission, NRC Advanced Reactors: https://www.nrc.gov/reactors/new-reactors/advanced

## Package

SMR Orchestration is one peer Capability Namespace within Grid-to-Inference at https://gridtoinference.com/.

## Credibility boundary

Not licensing, NRC interaction, engineering, design authority, commissioning, construction, procurement, project control, reactor operation, or legal advice.

## Resources

- Namespace manifest: https://smrorchestration.com/namespace.json
- Public ontology: https://smrorchestration.com/ontology.jsonld
- Sitemap: https://smrorchestration.com/sitemap.xml