cogniworks
Architecture · Data Flows

Teams

AI Agent

Anchor

Anchor

Control Plane

Prism

Prism

Knowledge Graph

Foundry

Foundry

Documents

Mycel

Mycel

Platform Foundation

The shape of the system

Four products. One purpose.

What this isn't
  • •Not a wrapper around an LLM.
  • •Not a monitoring dashboard.
  • •Not a document summarizer.
  • •Not a dev framework.
What this is
  • •Prism — A typed knowledge graph that grounds AI decisions.
  • •Foundry — A staged document pipeline that produces verified, traceable outputs.
  • •Anchor — A control plane that holds the running system to its definition.
  • •Mycel — A platform substrate that refuses builds that violate invariants.

Correctness at the layer where correctness is possible.

Incidents

What each product prevents.

MycelMycel· Platform foundation
Without Mycel
  • •Invariants drift past review
  • •Later build fails on old ghost
With Mycel
  • •Enforced at build time
  • •Violation on first compile
AnchorAnchor· Control plane
Without Anchor
  • •Config drifts from docs
  • •On-call paged at 3am
  • •40 min to find root cause
With Anchor
  • •Live typed model of prod
  • •Drift caught at t+0
FoundryFoundry· Document pipeline
Without Foundry
  • •49-page doc → "summarize"
  • •Approved, ships
  • •Page 47 hits prod later
With Foundry
  • •Gated stage-by-stage
  • •Full provenance to source
PrismPrism· Knowledge graph
Without Prism
  • •AI writes claims logic
  • •IRDAI clause 14(3) missing
  • •Audit finds it later
With Prism
  • •Domain rules in the graph
  • •Enforced at generation
Worked example

What correctness looks like on a single claim.

Insurance is the hardest regulated domain we could find. Here's how four products cooperate to adjudicate one claim.

  1. 01
    Ahead of time
    Foundry ingests the policy

    49 pages of policy text → extraction → normalization → validation → typed clauses emitted into Prism. Every clause carries lineage back to the paragraph it came from.

  2. 02
    At decision time
    Prism grounds the answer

    The adjudicating model queries Prism: "does coverage apply to this event class under IRDAI 14(3)?" Prism resolves against the typed graph. The answer — and the clauses it relied on — come back together.

  3. 03
    Always
    Anchor operates the fleet

    The services running the adjudication loop. Live topology, live state. Drift caught at t+0, not at 3am.

  4. 04
    Before anything ships
    Mycel gates deploys

    No service running outside the platform's invariants. Same gate for human-written code and AI-generated code.

What's guaranteed
  • •Every decision traceable to a source clause.
  • •No adjudication runs without grounded rule lookup.
  • •No service running outside platform invariants.
  • •Drift caught at t+0, not after the alert.
The pairings

Adopt one. Add the other when it helps.

Knowledge pairing

Foundry + Prism

Foundry structures what was unstructured. Prism holds what must be true. Together: documents become typed knowledge that AI can query without guessing.

Both adopted: Foundry outputs flow into Prism as typed graph nodes.

Only Foundry: outputs stand alone as traced specifications.

Only Prism: nodes are authored directly or ingested from any upstream.

Infrastructure pairing

Mycel + Anchor

Mycel encodes invariants at build. Anchor holds the running system to them. Together: the platform stays consistent from source to traffic.

Both adopted: Anchor operates Mycel-based stacks with full topology awareness.

Only Mycel: platform stands without a control plane.

Only Anchor: watches any microservice estate — Mycel or not.

Start with the product that fits the problem you have today.

On-premise, air-gapped, or cloud. Each product sold standalone. Built for environments where correctness is not optional.

Get in touch