Nu-Logos
Contact

Technology Clear roles for each technology, connected from requirements to verification.

Nu-Logos does not blend system models, semantics, relationship graphs, data models, connectors, and AI into one black box. Each has a defined role, because results are only trustworthy when you know which part produced them.

Components and their roles

These components do not substitute for one another. The model defines structure, the ontology defines meaning, the graph follows relationships, and the data model and provenance records keep each value in context. We are currently validating this architecture in a limited-scope proof of concept (PoC).

MBSE · SysML v2

Model-Based Systems Engineering

Defines requirements, functions, and system and component allocation as models, and establishes the traceability between them.

Ontology

Shared semantics

Gives engineering objects, properties, and relationships a common meaning, so different tools read the same object as the same thing.

Knowledge Graph

Relationship traversal

Explores the relationships between objects. When a design parameter changes, it finds the paths the impact can travel across the graph.

Engineering Data Model

Values with context

Stores each design value with its unit, source, version, status, and evidence, so no number floats free of its context.

Connector

Tool integration

Connects existing engineering tools and analysis codes to the Nu-Logos information model. It generates the inputs a tool needs and imports the results.

AI · LLM

Large language models

Assists with extracting candidate requirements, exploring impact, and drafting documents. Engineers make the final decisions.

Provenance and Evidence

Lineage records

Records the lineage of each result: which inputs, model, code, and version produced it, and who reviewed and approved it.

AI assists engineering work. Engineers remain responsible for engineering decisions. We draw a clear line between what AI does and what engineers decide.

Where AI helps

  • Suggests candidate requirements found in technical documents.
  • Helps explore the scope a design change may affect.
  • Assists with drafting evidence documents and reports.

What AI does not do

  • Judge licensing compliance
  • Make final safety determinations
  • Confirm or approve design values

AI suggestions enter the baseline only after an engineer has reviewed them.

Every result keeps its lineage

Every analysis result has the inputs, model, code, and version that produced it, and the people who reviewed and approved it. Nu-Logos records these links as a single chain, so the same question never sends you back to reconstruct everything from scratch.

A lineage record linking input, model, code, version, result, review, and approval in sequence.
Input
Model
Code
Version
Result
Review
Approval

Grounded in public standards

Our information model and terminology reference international standards and ontologies published by research institutions.

ISO/IEC/IEEE 29148

Requirements engineering

Criteria for how requirements are written and verified

OMG SysML v2

Systems modeling language

A way to express requirements, functions, and structure in one model

W3C PROV

Data provenance model

A way to express lineage between inputs, processes, and results

INL DIAMOND

Nuclear data ontology

A nuclear data integration ontology published by Idaho National Laboratory (INL)

We are looking for engineering workflows to validate together.

We welcome inquiries about pilot projects, technology partnerships, and anything else by email.

Email us contact@nu-logos.com