Every other part of VIPS works from what FORGE produces. If VIPS were a courtroom, FORGE would be the evidence room and the court reporter: it takes in the exhibits, locks them, and keeps the official record of every decision.
Every document is checked on the way in, fingerprinted, and locked in write-once storage before any analysis starts.
FORGE is the only part of VIPS that can issue Pass, Fail, or Inconclusive. It does that with fixed logic, not with an AI model's opinion.
Every determination is signed, linked to the one before it, and kept so that an outside party can verify it later.
The centerpiece of the VIPS v8.0 program: a unified evidence engine that transforms how procurement documents become defensible determinations.
Today, VIPS verifies rules against documents. FORGE makes the documents themselves first-class evidence. Every file that enters the platform passes through a zero-trust pipeline: validated, sealed, classified, and shredded into citable evidence objects before a single determination is made, with provenance tracked from first byte to final finding. The engine is running in production. Every PASS, FAIL, or INCONCLUSIVE it issues is signed, chained to the one before it, and reproducible end to end from the exact sealed bytes it was derived from.
Zero-trust upload with format and integrity validation.
Hashed into write-once storage. The record of record.
Document type and jurisdiction identified automatically.
Decomposed into discrete, addressable evidence objects.
Every determination bound to pinpoint evidence.
Reproducible findings with full provenance.
The shapes FORGE produces are versioned and frozen. A change is a new version with a recorded supersession, never a silent edit to what an auditor already relied on.
The rules governing when partial evidence may and may not support a conclusion are stated as mathematical propositions and checked by a proof assistant. The proof is rebuilt on every change and the build fails if it drifts.
Each determination is cryptographically signed and chained to the previous one for that customer, so the order and integrity of a determination history can be checked after the fact by someone who was not there when it was made.
When evidence is missing, conflicting, or requires human judgment, FORGE issues a sealed refusal that records why, at what severity, and what would resolve it. An honest refusal is a product, not a failure.
A sealed determination record can be independently verified against the evidence it cites and the rules it applied. The answer is verified, invalid, or unverified. There is nothing in between and there is no partial credit.
FORGE runs on versioned, frozen data contracts and machine-checked decision logic. Nothing issues before it is recorded. The ledger entry is written first. Those rules are properties of the system that can be independently checked, not claims on a slide. The build fails if the checked logic drifts from the logic that was proven.
An auditor, a protest reviewer, or a program office can trace any finding back to sealed source bytes and re-run the determination. Compliance stops being an assertion and becomes a reproducible result.
FORGE applies the same evidence standard to federal, state, and district rules alike. New jurisdictions plug into the engine as cited rulesets; the pipeline never changes.
The FORGE Engine is running in production inside the VIPS v8.0 program. Sealed intake, signed determinations, and independent verification of sealed records are live today. Cross-cloud verification is live: an exported record re-verifies in a separate trust domain that holds no credentials into our systems. Capability briefings on the v8.0 roadmap are available under NDA.
Straight answers, including what FORGE does not do.
When a document arrives, FORGE computes its fingerprint and stores the original in storage that cannot be overwritten or deleted for seven years. Later, anyone can recompute the fingerprint and confirm the document is the same one that was reviewed.
Intake checks that the file is a type FORGE can read and that it is not marked as controlled information. Seal fingerprints and locks it. Classify works out what kind of document it is and which jurisdiction applies. Shred breaks the text into individual requirements. Cite ties each requirement to the written rule and the exact passage. Determine issues Pass, Fail, or Inconclusive.
A running list of every decision. Each entry includes the fingerprint of the entry before it, like numbered pages in a bound notebook. If a page is removed or changed, the numbering breaks and the change is visible.
The core decision rules are written as mathematical statements and checked by a proof assistant, a program built to verify logic. One example: when a required fact is missing, the result must be Inconclusive and can never be Pass. That property is proven, not just tested.
What this does not mean: it does not prove that a document is genuine or that the facts in it are true. It proves the decision logic behaves the way we say it does.
Sealing detects any change made after a document enters VIPS. It does not, by itself, detect a document that was falsified before it was uploaded. VIPS also runs live registration and exclusion lookups against SAM.gov, and a person reviews every result.
Because a confident wrong answer is worse than no answer. When the evidence is missing or conflicting, FORGE issues a sealed refusal that states the reason and what would resolve it. We treat that refusal as a deliverable. It tells your reviewer exactly where to look.
Yes. A determination can be exported as a package and verified in a separate environment that has no access to our systems. See Independent verification.
The next generation of the engine is in development. Capability briefings on the roadmap are available under NDA. See status and roadmap.
Pilot engagements are open now: sixty days, fixed fee, one workflow. All initial conversations are under NDA.