Independent by design · no pay-to-rank placements  · How we evaluate tools →
Anclum Submit
C

CristianBarragan/Foundgine

Independent directory — not the official site. Details below come from the project's public repository.

Foundgine lets callers express intent while your application decides what's allowed, safe, and executed

6 ★ measured · checked 2026-11-19

Before you install: no copy-paste command · license Apache-2.0 · link reachable

First step: nothing runnable here yet - start from the repository: https://github.com/CristianBarragan/Foundgine

★ 6·updated 2026-11-16
View on GitHub ↗Link checked 2026-11-17 · HTTP 200 · opens the vendor's own site
Star count
6 ★ · CristianBarragan/Foundgine · read from the repository page · (checked 2026-11-19 20:00:48)
Source
read directly from its GitHub page · type: open-source project
Harvest history
first seen 2026-11-16 · last seen 2026-11-20 · seen 5× · listed by 2 sources
Score
score 203 · 6 ★ · 2 sources · repo
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: Open Source. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository CristianBarragan/Foundgine;first catalogued 2026-11-16;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.
README excerpt (English, untranslated) · Read the full README on GitHub →

# Foundgine

Excerpted from the repository README (abridged)

Foundgine gives AI agents and other callers a way to express what they want, while your application retains full control over how anything is executed. It introduces a single, application‑controlled semantic execution boundary that sits between:
caller intent,
your domain meaning,
your authorization rules,
and the actual operations performed on your data, APIs, GraphQL, MCP tools, or backend systems.
This boundary ensures that agents can propose actions, but only your application decides what is allowed, what is safe, and what is actually executed.
Go to website →
Where to read next
| I want to... | Go to |
| Run something now | Get started |
| Understand the idea and the boundary | docs/WHY-FOUNDGINE.md · docs/ARCHITECTURE.md |
| Browse every feature in plain language | Feature and capability wiki |
| Pick a database, ORM (EF Core / JPA) or search provider | Provider catalogue · ORM providers |
| Add GraphQL, Keycloak or Temporal | Extensions |
| Use Microsoft Agent Framework, LangChain4j or Spring Boot | Agent and framework integrations |
| Call a Foundgine server from TypeScript, Python or WebAssembly | Client SDKs · src/typescript · src/python · src/wasm |
| Check implementation and test coverage | Source coverage · Conformance and hardening |
# The problem
As applications expose more functionality to callers, you can end up with lots of individual tools/endpoints, each containing its own validation, authorization, query logic, and business rules.
Foundgine centralizes that responsibility into a semantic execution boundary. The caller expresses intent, while the application remains responsible for deciding what that intent means, what is allowed, and how it gets executed.
A complex application may have several ways to express an operation:
text
Application code
GraphQL
JSON
AI-generated intent
Without a common semantic execution layer, each surface tends to grow its own rules for:
what entities and fields exist;
which relationships can be traversed;
which filters are valid;
what the caller is authorized to access; and
how the request becomes database or service operations.
That produces duplicated semantics and inconsistent security boundaries.
## The idea
Retrieval can discover candidates and evidence, but retrieval is not authorization. The application owns identity and policy; providers execute the already-authorized artifact. Foundgine centralizes this responsibility.
## Get started
The fastest path is the Supply Chain sample pair:
Starter: the smallest realistic application boundary.
.NET — src/csharp/samples/Foundgine.SupplyChain: Build it step by step · Understand why it is structured this way
Java — src/java/samples/foundgine-supply-chain: Build it step by step · Understand why it is structured this way
Advanced: richer semantics, grounding, retrieval, authorization and adversarial testing.
.NET — src/csharp/samples/Foundgine.SupplyChain.Advanced: start at docs/00-Overview-And-Setup.md and follow 01–05.
Java — src/java/samples/foundgine-supply-chain-advanced: SupplyChain-Advanced-Tutorial.md.
Enterprise integration example (separate work-in-progress repository):
.NET/Java CRM, ERP, Temporal and Keycloak example — Foundgine-e2e-example: Tutorial. Check that repository's README for its current build and verification status; it is not a certified Foundgine sample.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[![Listed on Anclum](https://anclum.com/badge/listed.svg)](https://anclum.com/en/s/cristianbarragan-foundgine/)
Source
github · https://github.com/CristianBarragan/Foundgine
Browse by field
Open source
Traction
6 ★
Listed by
2 independent sources
added
today

More entries

All 1,875 →

Filed under

Every tag opens the full list for that filter. Counts are the live catalogue figures.

Browse all fields →

← Back to index