Space-hardware test article mounted to a vibration fixture
Qualification infrastructure for space hardware

Proof that travels
with the hardware.

Taldr is building one controlled qualification record—from source requirements and test intent to returned evidence and institutional acceptance.

Public toolFalcon 9 vibration basisBrowser-local inputsPDF + JSON record
The proof gap

The test is physical.
The proof is fragmented.

Requirements arrive in a user's guide. Intent lives in a deck. Inputs hide in spreadsheets. Evidence returns as raw files. Every handoff reconstructs the same decision.

Overhead view of a vibration-test floor
Today

Files move. Context does not.

MANUAL EVIDENCE WORK.csv export → channel parsing → plots → limit checks → reportEngineers rebuild the evidence before anyone can evaluate it.
With Taldr

One hardware identity. Every source, assumption, decision, and evidence object attached.

TALDR / CONTROLLED RECORDT-RB-00247 · REV 07

Optical Payload Module Assembly

Falcon 9 · RPUG v10 · Protoflight · Configuration CFG-B

Requirement basis
Source-versioned
§4.1.6 · §6.7
Declared assumptions
3 owned
2 customer · 1 lab
Open action
Sensor count
Owner named
Record integrity
PDF + JSON
Same snapshot
Automated analysis
Planned
Taldr drafts · customer approves
Live public tool

Turn the user's guide into a basis you can defend.

Build your Falcon 9 vibration-test Requirement Basis from the public RPUG.

Build your test basis →
Live Requirement BasisPublic sample · source-locked RPUG logic
REQUIREMENT BASIS / T-RB-00247
LOADING SOURCE-BACKED BASIS…
HARDWARE BASIS

42.6 kg · Circular interface · Protoflight

REV 07 · SOURCE LOCKED
01

RANDOM VIBRATIONCALCULATINGPublished MPE + approach scaling

RESOLVED
02

SINE BURST LOADSCALCULATINGMass band + interface + approach

RESOLVED
03

BURST FREQUENCYCALCULATINGEngineer-selected · blanket first-mode check

RESOLVED
04

LOW-LEVEL SINE0.1 g minimum · ≤3 oct/minBefore and after full-level test

RESOLVED
SOURCEVersioned locators
DECISIONSInputs + constraints
RECORDPDF + JSON parity
BUILD THIS BASIS WITH YOUR HARDWARE →
HUMAN RECORD · PDFVibration Requirement BasisT-RB-00247 · REV 07
MACHINE RECORD · JSON
{
  "schema": "taldr.requirement-basis.v1",
  "record_id": "T-RB-00247",
  "source": "RPUG v10",
  "configuration": "CFG-B",
  "grms": 7.87
}

The homepage shows the decision record. The live tool holds the plots, inputs, derivations, and controlled PDF/JSON export.

Shared campaign record

One campaign.
Every perspective.

Customer intent, hardware configuration, open items, and lab dispositions stay on one versioned campaign record. The perspective changes; ownership and authority do not.

CAMPAIGN / CAMPAIGN-VIB-042

OPTICAL PAYLOAD MODULE ASSEMBLY

OPMA · CFG-B

REV 07 · INTERNAL REVIEW
Requirement basisFalcon 9 · RPUG v10Resolved
Test campaignRandom + Burst + LLSS3 modules
Fixture / interfaceCustomer fixture · Rev CDrawing attached
InstrumentationAccelerometer count openOwner · customer
12:42

Customer engineerFixture drawing Rev C attached to the campaign record.

13:08

Lab reviewerSensor count and locations need confirmation before quote build.

SAME RECORD · SAME CONFIGURATION · PERSPECTIVE CHANGES ONLYCUSTOMER AUTHORINGLAB RETAINS QUOTE + TEST AUTHORITY

Synthetic campaign used to demonstrate the workflow. No customer or completed lab review is claimed.

Open the lab workflow →
One controlled identity

Qualification should compound.

Requirements, campaign state, returned evidence, and externally owned approvals should accumulate on the hardware identity instead of resetting at every handoff.

Design-stage synthetic example. Customers and test institutions own every approval; Taldr preserves provenance.

QUALIFICATION IDENTITY
OPMA-0042 · CFG-B
Hardware identity

Optical Payload Module Assembly

Falcon 9 · RPUG v10
  1. Requirement BasisRPUG v10 · §4.1.6 / §6.7

    7.87 GRMS · 12.5 g axial / 20.8 g lateral · PDF + JSON snapshot

    LIVE
  2. Campaign recordCAMPAIGN-VIB-042 · CFG-B

    Customer + lab perspectives · ownership + blockers named

    PRIVATE DEMO
  3. Evidence returnConfiguration-bound evidence

    Returned test evidence binds to the same identity.

    NEXT
  4. Automated analysisDrafted analysis · explicit disposition

    Taldr drafts. The customer approves.

    PLANNED · CUSTOMER APPROVES
  5. Qualification PassportEvidence-addressable · authority-explicit

    Approvals stay with customers and test institutions.

    DESIGN STAGETaldr evidence-control record stamp
Configuration-boundSource-versionedEvidence-addressableAuthority-explicit

Build the first
controlled record.

Build your test basisFor test labs