Specification as an interactive graph. For visualizing complex projects.
In OakCore, the graph is the data model. You do not have to follow links one by one; you get the full context at a glance.
The graph as the foundation
Traceability, impact analysis, and AI features all work on the same connected model. This lets us use relationships intelligently and efficiently and detect contradictions. It is our foundation and enables us to build features on the next level.
Semantic graph model
Our template-based graph model combines semantics and configurability. Choose from built-in types such as requirement, risk, or component and create any sub-types your project needs.
Project-specific sub-types
HW requirement, SW interface, failure mode, or whatever your project needs. With configurable, structured attributes, defined status models, and your own color scheme. Capabilities inherit from the template.
Semantic traceability links
Links have a type and a meaning. The connection structure that standards such as ISO 26262, IEC 62304, or DO-178C require for safety cases and verification.
Bidirectional
From requirement to test and back. Both directions live in the graph and are visible immediately.
Attachments, graphics & external links
Artifacts can be enriched with documents, images, and references. Beyond better communication and clarity, this also strengthens the context that AI models can draw on.
Context & filtering
Navigate large graphs in seconds with intelligent filtering. Views can be saved and shared across the project.
Canvas & Explorer
Canvas for the overview, Explorer for context around a single artifact. Two modes, one data model.
Minimap
Orientation on large graphs. Jump quickly to where the work is happening.
Grouping
Bundle elements when the graph gets crowded. Create structure without losing content.
Semantic search
Finds content despite typos, different spellings, or inconsistent wording, because search understands meaning, not just exact strings.
Saved filter views
Save filter combinations as personal or shared views.
Rule-based model validation
The model stays consistent, not at review time, but while you create.
Configurable rules
Define project-specific validation rules for what is allowed in the graph and what is not.
Type validation for attributes
Every attribute has a defined type. Invalid values are caught immediately, not at export.
Link validation
Only semantically valid connections between sub-types are allowed. No "somehow linked".
Status state machine
Status transitions follow a defined model. Invalid state changes are blocked.