Chronicle is the historical intelligence and change tracking layer inside Nebulae. It helps teams monitor snapshots, trends, changes, and long-term performance across catalog health, asset coverage, Azure sync, and future platform workflows.
Chronicle gives Nebulae a memory. Instead of only seeing the current state of the system, teams can understand what changed, when it changed, and whether the platform is improving over time.
Track image coverage percentage over time and understand whether cleanup efforts are improving asset readiness.
Monitor active and inactive folder gaps across historical snapshots to identify persistent structural catalog issues.
Track Azure blob gaps, missing JPGs, missing 360° files, missing diagrams, and naming warnings over time.
Review how visual depth changes by brand, including parts with 360° assets and the number of supporting still images.
Capture point-in-time records of catalog health so teams can compare current performance against previous states.
Support print-friendly reporting so historical health summaries can be shared with stakeholders.
Chronicle currently has a strong foundation through catalog health analytics: image coverage charts, active folder gap charts, Azure blob gap charts, historical tables, and brand-level accordion drilldowns.
Chronicle gives Nebulae the ability to show movement over time. It can prove improvement, reveal drift, and create accountability around catalog health, asset readiness, and future operational workflows.
Chronicle can grow beyond catalog health into a broader historical layer for the entire Nebulae platform.
Track fitment additions, updates, deletes, and validation outcomes over time.
Review staged import batches, validation errors, approved rows, rejected rows, and committed changes.
Track generated ACES, PIES, combined ZIP, scheduled export runs, approvals, cancellations, and delivery outcomes.
Support audit trails for platform actions, module usage, company activity, and administrative changes.
Continue expanding snapshot analytics for folder gaps, image gaps, asset coverage, Azure sync, and technical health.
Compare VIO datasets and market opportunity views across quarters or future data releases.
Track how new inventory additions affect catalog stability and content readiness over time.
Future modules can analyze pricing fluctuations, MSRP snapshots, and market pricing behavior.
Chronicle gives Nebulae a historical accountability layer. It helps users show progress, identify drift, and understand how the platform changes over time.
Chronicle helps teams move beyond one-time reports by showing whether their catalog, assets, and operational workflows are actually improving.
Chronicle strengthens Nebulae by creating a reusable historical analytics layer that can expand across modules, tenants, imports, exports, and administrative activity.
Chronicle completes the first major platform story: manage the data, measure readiness, understand opportunity, and track change.
Catalog, application, attribute, import, and export workflows.
Catalog health, asset coverage, technical quality, and cloud sync readiness.
Market opportunity by vehicle, configuration, and territory.
Historical trends, snapshots, changes, and long-term platform performance.
Chronicle helps teams understand not just what the platform looks like today, but how the catalog, assets, and workflows are changing over time.