GIMS
A generalized information-management system. Describe your domain as a grammar and GIMS becomes the tracker for it: no bespoke build, no rigid off-the-shelf module.
The problem
Operational teams outgrow spreadsheets fast, but the alternatives are bad. A bespoke app is slow and expensive. Off-the-shelf systems (LIMS, ERP, ticketing tools) force your process into their model, and you spend months bending your work to fit software instead of the other way around.
The deeper waste: every domain reinvents the same wheel. A lab tracking samples, an HR team tracking onboarding, and a shop tracking repairs are all doing the same thing: records, attributes, actions, history, all behind completely different, incompatible tools.
What I built
GIMS treats an organization's information like language. You define your domain as a grammar, and the system tracks it:
- Nouns — the entities you track (a sample, a candidate, a work order).
- Adjectives — the attributes that describe them (status, owner, due date).
- Verbs — the actions and tests you run against them (analyze, approve, ship).
Because the model is data, not code, the same engine reconfigures to a new domain by editing a schema rather than shipping a new app. A live, no-account demo lets anyone build a working grammar-based tracker in the browser and watch it run.
How it works
A schema-driven core holds the grammar. Domains live as JSON schemas under
projects/, so a new use case is a configuration, not a fork. A
FastAPI backend (Python) serves the API and record store; a lightweight
JavaScript/HTML/CSS front end renders the data-entry and run views. A module system extends
behavior (verbs can do real work) without touching the core engine.
- Grammar engine: nouns / adjectives / verbs as first-class, composable primitives.
- JSON-schema domain definitions: configure, don't hard-code.
- FastAPI + Uvicorn service layer; browser front end with an interactive walkthrough.
- Example workflows shipped as reference projects so the model is legible, not abstract.
Try it & read it
The demo resets on tab close. No account, no install, no real data at risk.
Status & traction
GIMS has its first paying client, a paid engagement to build out the project, and is open source. It's early, and I'm actively taking it further: the honest picture is a working, deployed system with real paid validation, not a mature product at scale.
It's also the foundation piece of a larger system. See where it's going →