Skip to main content
All projects
AI & Machine LearningProfessional Work

CrampasAI

An enterprise AI platform combining deterministic rules with generative AI for explainable business automation.

Role
Product Engineer
Focus
Python · FastAPI · OpenAI GPT
Status
Active
CrampasAI interface preview

Overview

CrampasAI is an enterprise AI platform for business automation. Its architecture combines deterministic rule processing with generative AI so workflows can use explicit business logic where predictability matters and model-based reasoning where inputs are less structured.

The problem

Business-critical workflows need consistent and explainable decisions, but many real-world inputs cannot be handled by fixed rules alone. A purely generative approach can be difficult to audit, while a rules-only system becomes rigid when requirements involve ambiguous language or contextual interpretation.

The solution

The platform separates deterministic decisions from generative processing. A rules engine handles cases governed by explicit business conditions, while generative AI supports inputs that require contextual reasoning. Feedback and prompt-management workflows provide a path for reviewing and improving model-assisted behavior.

System architecture

Requests are routed through the appropriate decision path, keeping deterministic business rules separate from generative reasoning and downstream feedback.

  1. 01Business request
  2. 02API layer
  3. 03Domain workflow
  4. 04Rules or generative path
  5. 05Decision output
  6. 06Feedback loop

Key capabilities

Hybrid decision processing

Combines explicit rule execution with generative AI instead of forcing every use case through one processing model.

Domain-oriented services

Uses domain boundaries to separate business responsibilities and support independent development across platform modules.

Asynchronous workflows

Background processing supports work that should not remain coupled to an interactive request lifecycle.

Deployment flexibility

Containerized services support enterprise deployment requirements, including environments where infrastructure must remain under organizational control.

Engineering decisions

Keep rules and generative reasoning distinct

Deterministic logic provides explicit behavior and an audit trail for known cases. Generative AI is reserved for inputs where fixed rules are insufficient, keeping its uncertainty visible rather than hiding it inside every decision.

Organize services around domain responsibilities

Domain-driven boundaries make ownership clearer and reduce coupling between business modules. Event-driven communication supports workflows that cross those boundaries without requiring every operation to execute synchronously.

Treat feedback as part of the product workflow

Model-assisted behavior needs review and iteration. Feedback loops and prompt-management processes provide operational inputs for improving the system over time.

Challenges & trade-offs

Predictability and flexibility

Rules are easier to explain but require maintenance as business conditions change. Generative models handle more variation but introduce uncertainty that must be managed explicitly.

Service boundaries

Separating domains supports team ownership and evolution, but distributed workflows add coordination, observability, and failure-handling requirements.

Enterprise deployment

Supporting different infrastructure environments increases delivery complexity and requires configuration to remain separate from application behavior.

Technology stack

  • Backend: Python, FastAPI
  • AI: OpenAI GPT, prompt-management and feedback workflows
  • Data and background work: PostgreSQL, Redis, Celery
  • Infrastructure: Docker, Kubernetes
  • Architecture: Domain-Driven Design, Event-Driven Architecture

Outcome

The platform establishes a hybrid foundation for enterprise automation where deterministic business logic and generative AI can be applied deliberately. The work demonstrates how AI functionality can be integrated into domain-oriented services while preserving operational and explainability considerations.

Project status

Private implementation. The public product is available online, while source code, deployment configuration, client workflows, and proprietary business rules remain private.