Skip to content

One engine. One lens on top of it. Nothing generic in between.

A horizontal platform that fits every industry fits none of them, and a vertical tool rebuilt for every industry is a maintenance problem pretending to be a product. IPAC shares the parts that have no reason to differ: ingestion, entities, evidence, audit, verification. It specializes only where space hardware genuinely is the difference.

Where the platform is shared, and where it is not.

Reading order is execution order. Everything outside the highlighted band is engine. Inside it, the lens brings the baseline that makes a hardware signal mean something and the shape of the decision at the end.

  1. 01

    Connectors and ingestion

    Government, commercial, and proprietary sources pulled on a managed schedule. Every run is recorded, including the ones that fail.

    scheduled · recorded · replayable

  2. 02

    Entity model

    Everything resolves to an entity: the serialized part, the lot, the approved vendor, the facility, the vehicle, the mission, and the relationships between them.

    parts · vendors · missions

  3. 03

    Signal threading

    Repeat observations about one condition fold into a single evolving thread carrying its own confidence and trend. Composite rules fire when separate weak signals converge on the same vendor or part inside a window.

    threading · correlation · trend

  4. Specialized for space and aerospace

  5. 04

    Scoring against a hardware baseline

    A lapsed NADCAP accreditation and an open Material Review Board item are not comparable facts. The lens brings the baseline that makes each of them mean something against a flight article.

    pedigree · qualification · nonconformance

  6. 05

    Decision synthesis

    One reconciled readiness state per tenant, and a decision that names the action, the confidence, and what it costs to carry the condition past the window.

    posture · recommendation · risk of inaction

    • Flight readiness
    • Part pedigree
    • Approved vendors
    • Nonconformance and MRB
    • Missions and windows

  8. Shared again below

  9. 06

    Evidence and audit

    The decision is bound to the records it cited, at the version it cited them. Review state, activity, and history are retained, never overwritten.

    versioned · reviewable · retained

  10. 07

    Verification

    Where a claim has to be checkable from outside, it is published at a token address that exposes that claim and nothing else. A part pedigree is the space case.

    public · single-claim · token-addressed

External signal is the cheap half.

Anyone can subscribe to a feed. What makes a recommendation specific to you is the join between that feed and the record only you hold: this serial number, this lot, this approved vendor, this window.

Public and regulatory
Range and space-weather feeds, launch-manifest windows, regulator actions, and denied-party lists from OFAC, BIS, DDTC, the UN and the EU.
pulled on a managed schedule
Industry and commercial
Accreditation and qualification registries, parts and counterfeit alerts, and vendor records joined against the same entity model as everything else.
joined, not stapled on
Your own quality record
Approved vendors, serialized parts and lots, nonconformances, inspections, missions, and the documents that evidence them. The half nobody else can see.
the differentiating half

Most hardware risk is legible before it is urgent.

The gap is rarely that a signal was missing. It is that the signals were individually unremarkable, arrived on different days, sat with different people, and nobody was holding them together against the window.

01Correlation across weak signals
A late delivery is noise. A quality escape is noise. Inside the same window against the same approved vendor, they are a qualification problem. IPAC carries named composite rules that fire on the combination, not the parts.
4 composite rules · 3 to 30 day windows
02Trajectory, not snapshot
Posture is scored on every run and kept. What matters is not today's number but its direction and rate of change across the last thirty, which is what turns a reading into a warning.
disruption probability · week-over-week delta
03Dated forward watch
Qualifications expire, calibrations come due, first articles get scheduled, windows open and close. IPAC holds the calendar of things that will become decisions and surfaces them while there is still room to act.
next material event · time to act
04Scenario simulation
Ask what happens if a vendor is disqualified, a lot is scrapped, or a qualification is suspended. IPAC walks the entity graph to the parts and missions actually downstream and returns a blast radius with a recovery window.
graph-backed · recovery window · stated basis
ipac / space-systems / predictions
TrajectoryRising+12 risk points week over week
46%
Disruption probability
118
Risk points
9
Active signals
2
Signal correlations
Disruption probability · last 15 snapshots21% to 46%

Signal correlations

  • Vendor Qualification Risk

    CRITICAL
    81%· Moderate7d windowquality + logistics

    A quality escape and two late deliveries from the same approved vendor inside one window, against parts on the critical path.

    Open a supplier corrective action and qualify a second source before the next build.

  • Schedule Compression Risk

    HIGH
    74%· Moderate14d windownonconformance + calibration

    An open Material Review Board item and a lapsing calibration on the acceptance test stand may compress the pre-window schedule.

    Sequence the MRB disposition ahead of the calibration recall, not after it.

What IPAC is watching next

  • Tessera Composites · NADCAP composites renewalin 21d
  • MSN-004 · rideshare window opensin 9d
  • NCR-2026-0148 · MRB disposition duein 18h

Neither correlation above would have raised an alert on its own.

Predictions surface. Representative interface, reference environment data.

These are scored heuristics over your own graph, not a forecasting model with a track record. The recovery windows are industry ranges and are labeled as such in the product. IPAC will tell you what is converging and how much room you have left against the window; it will not tell you what Tuesday holds.

The output is the decision, not the dashboard.

A chart tells you something moved. A decision names what to do, states how strongly the evidence supports it, and quantifies what waiting costs against the window. IPAC synthesizes one reconciled readiness state per tenant, so the product can never show “critical” in one panel and “no action required” in the next.

Recommended action
Specific and time-bound. Not a severity label.
Confidence
How strongly the underlying signals support it, as a number.
Risk of inaction
What doing nothing costs before the window closes.
Supporting records
The certs, inspections and nonconformances behind the call, counted and linked.
ipac / space-systems / command-center
Elevated risksynthesized 06:14

Three conditions stand between MV-1 and the window.

Build state is nominal; forward readiness is elevated. Pedigree gaps on installed thermal-protection tiles, one nonconformance still awaiting a Material Review Board disposition, and a composites vendor approaching qualification expiry are driving the posture.

3
Decisions requiring attention
6
Installed parts missing pedigree
2
Open nonconformances
9d
Until the window opens
CRITICAL93%· High

Close pedigree gaps on installed TPS tiles

Affected
6 serialized parts
Vendor
Tessera Composites
Mission
MSN-004
Why this matters

6 tiles already bonded to the aeroshell have a certificate of conformance on file but no material certification, so their pedigree chain is incomplete at the point it would be examined.

Recommended action

Request the missing material certifications from Tessera Composites and hold the flight-readiness review until the six chains close or the tiles are dispositioned.

Risk of inaction

A readiness review that cannot evidence material provenance for installed hardware, eight days before the window opens.

Review DecisionView Evidence7 supporting records

What changed · since yesterday

  • Installed parts missing a material cert+4worse
  • Nonconformances awaiting MRB−1better
  • Single-source parts on the critical path+2worse
  • Vendor qualifications expired0unchanged

What IPAC is watching next

  • Tessera Composites · NADCAP composites renewalin 21d
  • MSN-004 · rideshare window opensin 9d
  • NCR-2026-0148 · MRB disposition duein 18h

Command Center. Representative interface, reference environment data.

ipac / space-systems / decisions / DEC-2291 / basis

Basis · Close pedigree gaps on installed TPS tiles

DEC-2291 · 2026-08-20 06:14 UTC
Contributing factors
  • pedigree coverage gap
    critical
  • open nonconformance
    high
  • vendor qualification currency
    medium
  • range conditions across window
    low
Evidence cited
3 items · 1 unresolved gap · 100% integrity checked
  • Certificate of conformance · MV1-TPS-0142 SN 0007
    v2 · reviewed · superseded v1 retained
    77ff05b2…a5035dverified
  • FAI report AS9102 · TPS-LOT-2291
    v1 · reviewed
    5b20e7c4…9d0f31verified
  • Material certification · SN 0007 to SN 0012
    gap · requested from vendor 2026-08-14
    noneevidence gap
Retained activity
  • 06:14Decision synthesized · confidence 93%
  • 05:02Ingestion run completed · 4 sources · 0 failures
  • Aug 18Evidence review state set to reviewed · K. Alvarez
  • Aug 17Certificate of conformance v2 uploaded · digest recorded
Chain anchor
entry 4,182 · prev 4,181
9b3c17aef2d40c8e5a71b0d94f2c6e8813ab5d7f0c2e94a16b3d8f5027ce41ab

Append-only SHA-256 chain. Each entry chains to the previous, so a later alteration is detectable. Internal, not a public ledger.

Decision basis. Representative interface, reference environment data.

Defensible means it still holds up later.

Evidence in IPAC is versioned, not replaced. Superseding a certificate creates a new version and leaves the old one intact, along with the readiness call that relied on it. Review state, activity, and login history are retained alongside.

Every document is hashed with SHA-256 at upload and anchored in an append-only chain where each entry chains to the previous, so a later alteration is detectable. It is an internal chain, not a public ledger, and we describe it that way.

The security model

Deployed as a multi-tenant platform, isolated per tenant and per environment.

A tenant is the unit of reach: membership decides what a user can address at all, and entitlements are granted per tenant. Inside a tenant, demonstration and operating environments are separate worlds. Requests carry the environment they act in, and object storage is partitioned the same way.

Access is email and password with per-user TOTP two-factor, server-side sessions with fixed expiry, and scoped API keys for programmatic access. Single sign-on is not implemented, and IPAC is not an export-control enclave. Both are on the security page rather than left to be discovered in procurement.

Security architecture

The fastest way to evaluate IPAC is one real readiness call, end to end.

Bring a call your team made late, or nearly missed. We will walk it from the certs, inspections and signals that existed at the time to the record it would have left.

Request a working session