How it works
From document inputs to signed artifacts, in three pillars.
The engine reads the same materials your team would read by hand — filings, tenders, specs, contracts — and routes them through a probabilistic forecast layer with a human approval gate at the end. What ships back to your desk is one signed artifact, fully provenanced, against one named decision.
The engine reads what your team reads.
Tender packs at 2,000 pages. Cluster studies at 5,000. Image-embedded Excel and scanned PDF. The ingestion layer parses each source into a normalized schema and preserves pagination, table boundaries, and footnote anchors as first-class fields, so any later claim can be traced back to a specific page, table, and row.
- Multi-format parsing: PDF, XLSX, CSV, scanned-image OCR
- Footnote and cross-reference resolution preserved
- Bidirectional source links — claims trace to page + row
- No opaque-embedding-only storage; the source is always queryable
Distributions, not point estimates.
Athena's Lattice and Reservoir produce P10–P90 sensitivity bands for every revenue and yield assumption. Nexus's Sourcing scores every supplier against ICV, UFLPA, and code conformance. What lands on your IC desk is the distribution and the dominant drivers, not a single number to defend.
- P10–P90 sensitivity bands on every revenue layer
- Capacity, energy, ancillary, and contract overlays modelled jointly
- Compliance-scored supplier shortlists, not 200-page memos
- ICV, UFLPA, NFPA 855, IEC 62933 — gating filters, not commentary
Every artifact human-signed at the gate.
Nothing leaves the system without a senior-analyst or procurement-lead signature. Every external artifact — DD pack, IC memo, compliance brief, redline, award memo — is generated as a draft, flagged for review, and held until the signed event lands. Every claim in the artifact carries a provenance trail back to its source.
- Append-only audit log on every generation, review, approval
- Provenance trail from claim → page + table + row
- Reject routes back with structured feedback, not free-text drift
- Customer-VPC deployment default — buyer holds keys + logs
Three pillars. One engagement. One signed artifact.
Engagements run fixed-fee, four to six weeks, against a single named decision. Customer-VPC deployment by default — your keys, your logs, your audit trail.