A horizontal platform that fits every domain fits none of them, and a vertical tool rebuilt six times is six products to maintain. IPAC shares the parts that have no reason to differ: ingestion, entities, evidence, audit, verification. It specializes only where the domain genuinely is the difference.
Reading order is execution order. Everything outside the highlighted band is identical in every domain. Inside it, each operating model brings its own baseline and its own shape of decision.
Government, commercial, and proprietary sources pulled on a managed schedule. Every run is recorded, including the ones that fail.
scheduled · recorded · replayable
Everything resolves to an entity: supplier, asset, mandate, treaty, counterparty, and the relationships between them.
entities · relationships · geometry
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 entity inside a window.
threading · correlation · trend
Specialized per operating model
A 94% limit utilization and an expired HACCP certificate are not comparable facts. Each operating model brings the baseline that makes its own signals mean something.
per-model baselines
One reconciled operational state per tenant, and a decision that names the action, the confidence, and the cost of not acting.
posture · recommendation · risk of inaction
Shared again below
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
Where a claim has to be checkable from outside, it is published at a token address that exposes that claim and nothing else.
public · single-claim · token-addressed
Anyone can subscribe to a feed. What makes a recommendation specific to you is the join between that feed and the operating record only you hold: this supplier, this lot, this mandate, this line.
The gap is rarely that a signal was missing. It is that the signals were individually unremarkable, arrived on different days, and nobody was holding them together.
Signal correlations
Supply Chain Disruption Risk
CRITICALWeather event affecting facility operations combined with transportation delays.
Activate contingency suppliers and notify downstream customers.
Margin Pressure Risk
HIGHCommodity price movement combined with logistics disruption may compress margins.
Review contract pricing terms and hedge exposure.
What IPAC is watching next
Neither correlation above would have raised an alert on its own.
Predictions surface. Representative interface, demonstration 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; it will not tell you what Tuesday holds.
A chart tells you something moved. A decision names what to do, states how strongly the evidence supports it, and quantifies what waiting costs. IPAC synthesizes one reconciled state per tenant, so the product can never show “critical” in one panel and “no action required” in the next.
Three conditions require attention.
Current operations are stable; forward risk is elevated. Supplier certification failure, concentration exposure at a single processor, and shipments held at customs are driving the posture.
Resolve supplier certification failure
3 suppliers lack valid certification evidence on file, creating a material compliance and continuity exposure.
Temporarily restrict new orders from uncertified suppliers while updated evidence is collected.
Potential compliance failure, shipment hold, and customer assurance risk.
What changed · since yesterday
What IPAC is watching next
Command Center. Representative interface, demonstration data.
Basis · Resolve supplier certification failure
DEC-1184 · 2026-08-20 06:14 UTCAppend-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, demonstration data.
Evidence in IPAC is versioned, not replaced. Superseding a document creates a new version and leaves the old one intact, along with the decision 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.
A tenant is the unit of reach: membership decides what a user can address at all, and module 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 optional TOTP two-factor, server-side sessions with fixed expiry, and scoped API keys for programmatic access. Single sign-on is not implemented. We say so on the security page instead of leaving it to be discovered in procurement.
Security architectureBring a call your team made late, or nearly missed. We will walk it from the signals that existed at the time to the record it would have left.