Every ROI-* module answers one commercial question over the same collected truth.
Every capability beyond the core is a module. A module is a folder of SQL, a manifest and optional UI metadata. The backend discovers it, the database executes it, and the frontend renders it — without a line of core code changing.
Ship the core set, then add any lens your business needs. Each module reuses the same collected truth and the same price list.
Contract versus deployed cost per Oracle Database, edition and option.
rdb()Product-level mapping and coverage across the middleware estate.
rfmw()Resolve physical, virtual and clustered servers to effective Oracle processors.
os_multiplier()Appliance-specific licensing models and capacity-on-demand rules.
roi_db()Simulate deployments against compute, RAM, capacity and backup cost models.
sdb()Snapshot payback analysis that frames migrations and consolidations financially.
roi_db()Entitlement tracking with triggers that keep mappings coherent.
rdb() mode C“The Big Picture” dependency graph — a million-plus mappings of systems and software.
granular_tree()Virtual clusters and their relationship to licensing entitlement.
roi_os()Configurable thresholds and severity levels for compliance events.
add_alert()16,600+ Oracle product prices by region and currency, freely updatable.
roi_db()Time-series DB, FMW and OS metrics for how much work each system performs.
rwrt()A module is just a directory. SQL files run in order at load time; the manifest tells the platform what it provides and who may call it.
permissions (client, admin, super). Owner: ComplianceOne small JSON file declares identity, dependencies, entrypoints, permissions and UI placement.
{
"id": "ROI-CLOUD",
"name": "Cloud what-if",
"version": "0.4.0",
"requires": ["ROI-DB"],
"entrypoints": [
"sdb",
"sdb_calc_compute_estd",
"sdb_calc_ram_estd"
],
"tables": ["cloud_estimate"],
"permissions": ["client", "admin", "super"],
"ui": { "menu": "Cloud", "order": 40 }
}A named owner signs off the question, the data scope and the permissions before the module is admitted.
The module carries its own version. Upgrades are change-controlled and reversible — nothing ships straight to production.
Deploy per tenant with no core rewrite. Tenant isolation is enforced by sec_check() at call time.
The backend scans modules/*/module.json at boot and registers each module and its dependency graph.
SQL files run in order, idempotently. Tables, functions and views are versioned per module.
The frontend reads the menu manifest and calls the declared entrypoints through a generic dispatcher.
foreach (modules() as $m) {
$manifest = json_decode($m.'/module.json');
if (!satisfied($manifest->requires)) continue;
DB::statement("SET search_path TO {$schema}");
foreach (glob($m.'/sql/*.sql') as $f) {
DB::unprepared(file_get_contents($f));
}
registry()->register($manifest);
}// menu.yaml drives navigation
// call the function the module declared
$rows = DB::select(
"SELECT * FROM {$schema}.{$entrypoint}(?, ?, ?)",
[$mode, $tenant, $location]
);
return view('roi::table', compact('rows'));Every call passes through sec_check(). No function returns another tenant's rows, on any module.
Migrations are additive and reversible. Tenant data is never dropped without an explicit, logged decision.
Functions return a declared type, so reports and exports keep the same shape as internals evolve.
Each module ships SQL tests that run in CI. A lens cannot be promoted until its evidence passes.
Every function accepts and filters on the tenant identifier, and calls sec_check() before returning rows.
Files are numbered and safe to re-run; migrations never destroy tenant data silently.
Prefer composite types like trr so consumers get a stable, self-describing contract.
Each module ships assertions that run against a fixture schema in CI.
The same typed result becomes a business evidence pack and a reproducible technical load order.
Bring us the commercial question your business needs answered and we'll shape it into a governed, versioned module.
Start from the module template in the backend repository and have a new ROI-* view running in an afternoon.