Files move. Context does not.

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.
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.

One hardware identity. Every source, assumption, decision, and evidence object attached.
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
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 →§4.1.6 · §6.5 · §6.7.1 · §6.7.242.6 kg · Circular interface · Protoflight
RANDOM VIBRATIONCALCULATINGPublished MPE + approach scaling
RESOLVEDSINE BURST LOADSCALCULATINGMass band + interface + approach
RESOLVEDBURST FREQUENCYCALCULATINGEngineer-selected · blanket first-mode check
RESOLVEDLOW-LEVEL SINE0.1 g minimum · ≤3 oct/minBefore and after full-level test
RESOLVED{
"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.
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.
OPTICAL PAYLOAD MODULE ASSEMBLY
OPMA · CFG-B
REV 07 · INTERNAL REVIEWCustomer engineerFixture drawing Rev C attached to the campaign record.
13:08Lab reviewerSensor count and locations need confirmation before quote build.
Synthetic campaign used to demonstrate the workflow. No customer or completed lab review is claimed.
Open the lab workflow →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.
Optical Payload Module Assembly
- LIVE
Requirement BasisRPUG v10 · §4.1.6 / §6.7 7.87 GRMS · 12.5 g axial / 20.8 g lateral · PDF + JSON snapshot
- PRIVATE DEMO
Campaign recordCAMPAIGN-VIB-042 · CFG-B Customer + lab perspectives · ownership + blockers named
- NEXT
Evidence returnConfiguration-bound evidence Returned test evidence binds to the same identity.
- PLANNED · CUSTOMER APPROVES
Automated analysisDrafted analysis · explicit disposition Taldr drafts. The customer approves.
Qualification PassportEvidence-addressable · authority-explicit Approvals stay with customers and test institutions.
DESIGN STAGE