Light up only what you need. It grows with you.
Dimbo is a manifest-driven plug-in platform, not a monolith with side packages. Every module — a model, a router, a daemon, a screen — snaps into the same shared graph and the same knowledge store. Start with one workspace, add the next when you're ready. Because each module writes into the same picture, the second one roughly triples value: the join across domains is where the non-obvious value lives.
Every module does one job well, and feeds every other.
Modules are grouped into workspaces that match how a company is actually run. Each is discovered at boot from its own manifest and appears in the shell only if you switch it on. Here's the full estate.
The customer, the cash, the relationship.
Finance
Invoices and milestones, plus the marketing spend tied to each account, with an overdue-invoice scanner and milestone-payment tracking that turn slippage into an action before the money is late.
- Invoice
- Milestone
- cashflow_event
Support
Tickets and NPS with a health correlator that reads support load against usage, spotting both the churn signal and the upsell moment, and inferring tickets straight from inbound email.
- SupportTicket
- NPSScore
- HealthCorrelator
Everything that moves, and where it is.
Logistics
Shipments, warehouses, vehicles and inventory batches with a disruption scanner and a carbon-metric stream, so a delivery at risk surfaces while there's still time to reroute it.
- Shipment
- Warehouse
- InventoryBatch
- carbon_metric
ERP Connectors
Read-only bridges into the systems you already run: FatturaPA / SDI electronic-invoice XML lands as finance invoices, and VAT counterparties get resolved automatically, with anything unresolved safely quarantined. It reads your ERP; it never replaces it.
- FatturaPA / SDI
- VAT resolution
- quarantine
The floor, the machines, the work.
Project Management
Projects and issues, organized into cycles, anchor commitments and deadlines to the work that has to deliver them.
- Project
- Issue
- Cycle
IoT & Devices
Devices and places, plus the how-tos tied to each one, sit over a time-series metric store: machine state read as meaning, on the same picture as everything else.
- Device
- Place
- timeseries_metric
Incidents
Incidents, updates, runbooks, post-mortems, escalation policies and on-call shifts, with SLA-breach detection wired in.
- Incident
- Runbook
- OnCallShift
Maintenance
Work orders and preventive-maintenance schedules, backed by parts on hand, turn a predicted failure into a scheduled fix before it becomes a breakdown.
- WorkOrder
- PM schedule
- Part
Reference Data
Finite reference data done right: ATECO / NACE / NAICS industry codes, Italian legal forms, ISTAT subdivisions and postal codes, the backbone of clean entity resolution.
- ATECO / NACE
- legal forms
- ISTAT
Company KB
An Italian company knowledge base built from Wikidata bulk loaders and a cache resolver, with a promotion worker that turns a name in an email into a resolved, deduplicated entity.
- kb_companies_raw
- Wikidata
- resolver
Operator Console
The sysadmin-only control room: platform secrets and external-account credentials, plus bootstrap, with every key encrypted at rest and managed in one place.
- platform_secrets
- external_account
- bootstrap
Harvester
Knowledge harvesting, and the canonical reference for how a module is built: the pattern every new plug-in follows.
- ingestors
- logic
- api
The obligations, the contracts, the people.
Tax & Compliance
Tax filings, insurance, audits and permits: the administrative deadlines that carry the sharpest penalties, held in one place with the expiry dates watched for you.
- filings
- insurance
- permits
Governance
Corporate filings, board minutes, resolutions and the cap table — the record of who decided what, kept queryable in one searchable place.
- filings
- board minutes
- cap table
Legal
Contracts and SLAs, plus GDPR records, with a contract-expiry scanner and the penalty and delivery clauses parsed out, so a what-if can put a real euro figure on a decision.
- Contract
- SLA
- GDPRRecord
People & Skills
Skills and certifications, tracked against each assignment, support an availability query: who is qualified and free, and what's coming up for renewal. Processes, never individual performance metrics.
- Skill
- Certification
- Assignment
Reasoning that spans every workspace at once.
These modules don't belong to a workspace. They read across all of them. This is where the shared graph stops being storage and becomes judgment.
Correlation
Joins signals that live apart into one root cause: deterministic candidates checked by an LLM judge and confirmed by an adversarial verify pass, then surfaced with evidence legs grouped by pillar.
- CorrelationInsight
- graph traversal
- adversarial verify
Forecast
Four explainable forecasters — cash-90d, delivery-delay, churn-risk, machine-failure — built on percentiles and slopes, combined into a weighted score. No black-box ML.
- cash_90d
- delivery_delay
- machine_failure
What-If
A closed registry of three typed decision simulators — delivery-delay penalties, supplier shortfall, payment delay — with declared model boundaries. Never "simulate the whole company."
- delivery_delay
- supplier_shortfall
- payment_delay
Autonomy Ladder
Per-process trust: a capability earns autonomy only by measured track record. Promotion is always your decision; demotion is instant the moment a human disagrees.
- ProcessAutonomy
- track record
- undo window
Deadline Audit
The wedge — reads Commitment, Invoice and Contract records straight off the graph, buckets them per client, and writes a KnowledgeDoc back for every audit it runs.
- 30/60/90d buckets
- risk highlights
- KnowledgeDoc
The Assistant That Asks
Gap heuristics find what's missing: a client with traffic but no notes, a commitment with no owner, then turn each gap into a question in the operator's language.
- gap heuristics
- knowledge_question
- it / en
World Intelligence
Pillar four. RSS / GDELT collectors plus on-demand web search, mapped to your actual exposure: a supply shock or a regulatory shift raised as a risk alert tied to your own operations.
- RSS / GDELT
- WorldIntel briefs
- risk alerts
The substrate every module stands on.
Platform Core
The agent pipeline, the event bus, the shell, the capability registry, the spine the whole plug-in system snaps into.
- pipeline
- Kafka topics
- capabilities
Knowledge Store
Platform-native knowledge: every note and elaboration, plus every RAG source, held as a governed KnowledgeDoc, with zero-friction voice and photo capture straight from the floor.
- KnowledgeDoc
- RAG index
- voice / photo
MCP Tools
A server-side tool registry covering the semantic graph and time-series metrics, plus operations actions, exposing Dimbo's reasoning surfaces to agents through a standard protocol.
- neo4j_semantic
- timescale_metrics
- operations_actions
One module is a tool. Three are a nervous system.
Each module writes into the same graph and the same knowledge store. So a fact one module knows becomes context every other module can reason over. The insights that matter most are exactly the ones no single-domain tool can ever see, because they live in the join between domains.
Invoice 60 days overdue
The overdue-invoice scanner flags a customer whose payment has slipped past the contractual window.
Late-payment penalty clause
The same customer's framework contract carries a penalty clause, parsed and linked to the very same entity in the graph.
Shipment at risk
A delivery to that customer is already running late. The relationship is under pressure from two sides at once.
Three isolated facts. One correlated action. Correlation reads across the graph and ties them to a single customer; the Action Center then proposes one move, with the evidence, from three modules, attached.
Add finance alone and you catch the overdue invoice. Add legal and you know the penalty. Add logistics and you save the relationship. That's why the second module roughly triples value: the model counts none of the compounding beyond it, a conservative floor (Dimbo value model §5).
"We land with the audit. We grow with the graph."
Manifest-driven, plug-in native.
Every module is a manifest
A model, a router, a daemon, a screen, a capability, all declared in one manifest and picked up automatically. Nothing is hand-wired into the core, so nothing rots.
Light up only what you need
Run just finance and the audit, or the whole estate. Turn a workspace off for a services business, on for a factory: same platform, same intelligence.
Everything writes into the graph
Every module reads from and writes into the same deduplicated, provenance-stamped graph and knowledge store. That shared substrate is what makes the compounding real.
Start with one module. See it compound.
The Deadline Audit is the cheapest way in: a scan of your open commitments and overdue invoices, plus contracts about to expire, turned into hard 30/60/90-day cash figures. On your data, on your infrastructure, in 48 hours. Then add the next module when you're ready.