Skip to main content
SPAIDER Space
Systems Engineering Agent

Meet SPOCK

Requirements, architecture, traceability, and technical reviews in one engineering workspace.

SPOCK helps systems-engineering teams structure technical baselines, connect evidence, identify gaps, and prepare human-led reviews.

SPOCK / SYSTEM MODELTrace state · 84%
Requirements128 items
SYS-014

Attitude knowledge

SYS-021

Safe-mode entry

IF-006

Power interface

VER-032

Thermal evidence

Architecture graphevidence connected
REQSYSIFSUBVER
Evidence96 sources
Conflicts03 flagged
Review2 pending
Core functions

What SPOCK does.

/ 01

Requirements engineering

Extract, classify, decompose, and organize stakeholder, system, subsystem, interface, and verification requirements.

/ 02

Traceability and evidence

Link requirements to source documents, architecture elements, design decisions, verification methods, and technical evidence.

/ 03

Architecture analysis

Represent system elements, interfaces, constraints, assumptions, and open decisions in a shared technical context.

/ 04

Review preparation

Assemble review inputs, unresolved items, evidence status, and change impact for engineer approval.

Technical workflow.

01

Ingest

Read requirements, standards, specifications, and program records.

02

Structure

Map content into the aerospace ontology and system hierarchy.

03

Trace

Connect requirements, design elements, interfaces, and evidence.

04

Analyze

Flag gaps, conflicts, weak evidence, and affected dependencies.

05

Review

Present findings and proposed updates for engineering approval.

Inputs and outputs

Connected to the technical record.

SPOCK is an engineering decision-support system. The responsible engineering team retains authority over requirements, architecture, verification, and program baselines.

Inputs
  • Requirements and specifications
  • Applicable standards
  • System architecture and interfaces
  • Design decisions and assumptions
  • Verification plans and evidence
Outputs
  • Structured requirements baseline
  • Traceability links and matrices
  • Gap and conflict register
  • Change-impact context
  • Technical review package
Trust Layer integration

Verification attached to the workflow.

Review the Trust Layer
T1

Source provenance for each extracted requirement and technical assertion.

T2

Contradiction screening across requirements, assumptions, interfaces, and memory.

T3

Confidence signals for extracted links and proposed classifications.

T4

Explicit engineer approval for baseline and review-state changes.

Discuss a SPOCK pilot.

Review your workflow, data, and integration requirements with the SPAIDER team.

Discuss a pilot