cogniworks
FoundryFoundry · Document Pipelines

Documents become structured knowledge.

Not summaries. Not document AI.

What Foundry does:

Staged pipelines: normalize → structure → validate → enrich.
Every stage produces, audits, gates, fixes.
Output is a traced specification — never a summary.
foundry · requirements_processingstage 3/8
S1Normalizemap
S2Groupfanout
S3Enrichmap
S4Validatemap
S5Synthesizereduce
produce → audit → gate → fix247 items

Gated, not generated

No stage advances without meeting explicit criteria. Quality is never assumed.

Structure preserved

Single-pass LLMs compress. Foundry transforms — each stage audited before the next.

Every claim traceable

Every output carries its lineage. Nothing anonymous. Nothing unverifiable.

The problem

You asked for specifications. You got summaries.

Single-pass LLMs compress. They lose edge cases, contradictions, the precision that made the document worth having.

Foundry transforms, stage by stage.

PAGF loop

Every stage meets the bar — or fixes itself.

Produce. Audit. Gate. Fix. No stage advances on unverified output. What reaches the end passed.

Stage primitives

Four types. Any pipeline.

mapOne input → one output.
fanoutOne input → N outputs.
flatmapN inputs → M outputs.
reduceN inputs → one output.