Tools and Features

Catalyst Data: Feature-by-Feature Guide

Use every documented Catalyst Data feature with sample input and expected output.

ProductCatalyst DataVerified version1.11.0ComponentComparison Studio, Connectors, Datasets, Embeds, Entities, Evidence Ledger, Export Studio, Indicators, Institutional Access, Instruments, Observations, Persistent Workspaces, Public API, Quality Rules, Questions, Refresh Operations, Review and Revision, Saved Queries, Sources, Units and MethodsUpdatedJuly 17, 2026Reading time18 minutes
← Back to product guides

Catalyst Data · Technical Reference

Governed entities, indicators, sources, evidence, questions, instruments, datasets, observations, quality, review, query, export, API, access, connectors, and refresh.

Audience: product users, administrators, reviewers, and integrators.

Last verified version: 1.11.0

Reading time: 18–30 minutes

Status: Published support documentation.

Purpose

This is the complete documented feature inventory for Catalyst Data version 1.11.0. Every feature includes sample data, a seven-step use pattern, expected output, and a verification rule. Reverify this article whenever the product release changes.

Prerequisites

  • A clean demonstration workspace
  • The downloadable all-feature CSV or JSON
  • Current product release notes
  • Permission to use each tested feature
  • A reviewer familiar with the product

Sample data

This article uses a fictional Resilient Community Retrofit Program. The files contain one demonstration row for every documented feature, so each capability can be tested without private or production data.

Download CSV feature examples · Download JSON workspace example

Preview

# Feature Sample action Expected result Classification
1 Entities create the Community Center entity a stable entity ID synthetic-demo
2 Indicators define monthly electricity use with unit, method, and direction a reusable indicator definition synthetic-demo
3 Sources register utility data with publisher, URL, license, retrieval, and citation a provenance source record synthetic-demo
4 Evidence Ledger attach a bill and meter export to observations an evidence chain synthetic-demo
5 Questions state whether use fell after weather normalization a bounded analytical question synthetic-demo

The downloadable files include all 20 feature rows.

Feature-by-feature procedure

1. Entities

Purpose: Use Entities within the governed Catalyst Data workflow.

Sample action: create the Community Center entity.

Steps

  1. Open or create the synthetic retrofit workspace.
  2. Select or navigate to this feature.
  3. Enter the matching row from the CSV or JSON sample.
  4. Review required fields, sources, units, permissions, assumptions, and warnings.
  5. Run or save the feature operation.
  6. Compare the result with the expected result below.
  7. Add a review note and preserve the feature state.

Expected result: a stable entity ID.

Verification: The result must preserve the sample feature ID, product version, lifecycle state, provenance, and any domain-specific unit or classification. Failure must return an actionable error without destroying prior state.

2. Indicators

Purpose: Use Indicators within the governed Catalyst Data workflow.

Sample action: define monthly electricity use with unit, method, and direction.

Steps

  1. Open or create the synthetic retrofit workspace.
  2. Select or navigate to this feature.
  3. Enter the matching row from the CSV or JSON sample.
  4. Review required fields, sources, units, permissions, assumptions, and warnings.
  5. Run or save the feature operation.
  6. Compare the result with the expected result below.
  7. Add a review note and preserve the feature state.

Expected result: a reusable indicator definition.

Verification: The result must preserve the sample feature ID, product version, lifecycle state, provenance, and any domain-specific unit or classification. Failure must return an actionable error without destroying prior state.

3. Sources

Purpose: Use Sources within the governed Catalyst Data workflow.

Sample action: register utility data with publisher, URL, license, retrieval, and citation.

Steps

  1. Open or create the synthetic retrofit workspace.
  2. Select or navigate to this feature.
  3. Enter the matching row from the CSV or JSON sample.
  4. Review required fields, sources, units, permissions, assumptions, and warnings.
  5. Run or save the feature operation.
  6. Compare the result with the expected result below.
  7. Add a review note and preserve the feature state.

Expected result: a provenance source record.

Verification: The result must preserve the sample feature ID, product version, lifecycle state, provenance, and any domain-specific unit or classification. Failure must return an actionable error without destroying prior state.

4. Evidence Ledger

Purpose: Use Evidence Ledger within the governed Catalyst Data workflow.

Sample action: attach a bill and meter export to observations.

Steps

  1. Open or create the synthetic retrofit workspace.
  2. Select or navigate to this feature.
  3. Enter the matching row from the CSV or JSON sample.
  4. Review required fields, sources, units, permissions, assumptions, and warnings.
  5. Run or save the feature operation.
  6. Compare the result with the expected result below.
  7. Add a review note and preserve the feature state.

Expected result: an evidence chain.

Verification: The result must preserve the sample feature ID, product version, lifecycle state, provenance, and any domain-specific unit or classification. Failure must return an actionable error without destroying prior state.

5. Questions

Purpose: Use Questions within the governed Catalyst Data workflow.

Sample action: state whether use fell after weather normalization.

Steps

  1. Open or create the synthetic retrofit workspace.
  2. Select or navigate to this feature.
  3. Enter the matching row from the CSV or JSON sample.
  4. Review required fields, sources, units, permissions, assumptions, and warnings.
  5. Run or save the feature operation.
  6. Compare the result with the expected result below.
  7. Add a review note and preserve the feature state.

Expected result: a bounded analytical question.

Verification: The result must preserve the sample feature ID, product version, lifecycle state, provenance, and any domain-specific unit or classification. Failure must return an actionable error without destroying prior state.

6. Instruments

Purpose: Use Instruments within the governed Catalyst Data workflow.

Sample action: define a meter-reading or import instrument.

Steps

  1. Open or create the synthetic retrofit workspace.
  2. Select or navigate to this feature.
  3. Enter the matching row from the CSV or JSON sample.
  4. Review required fields, sources, units, permissions, assumptions, and warnings.
  5. Run or save the feature operation.
  6. Compare the result with the expected result below.
  7. Add a review note and preserve the feature state.

Expected result: a versioned collection instrument.

Verification: The result must preserve the sample feature ID, product version, lifecycle state, provenance, and any domain-specific unit or classification. Failure must return an actionable error without destroying prior state.

7. Datasets

Purpose: Use Datasets within the governed Catalyst Data workflow.

Sample action: create a monthly-energy dataset.

Steps

  1. Open or create the synthetic retrofit workspace.
  2. Select or navigate to this feature.
  3. Enter the matching row from the CSV or JSON sample.
  4. Review required fields, sources, units, permissions, assumptions, and warnings.
  5. Run or save the feature operation.
  6. Compare the result with the expected result below.
  7. Add a review note and preserve the feature state.

Expected result: a registered dataset.

Verification: The result must preserve the sample feature ID, product version, lifecycle state, provenance, and any domain-specific unit or classification. Failure must return an actionable error without destroying prior state.

8. Observations

Purpose: Use Observations within the governed Catalyst Data workflow.

Sample action: enter January through March kWh with time, source, and status.

Steps

  1. Open or create the synthetic retrofit workspace.
  2. Select or navigate to this feature.
  3. Enter the matching row from the CSV or JSON sample.
  4. Review required fields, sources, units, permissions, assumptions, and warnings.
  5. Run or save the feature operation.
  6. Compare the result with the expected result below.
  7. Add a review note and preserve the feature state.

Expected result: traceable observations.

Verification: The result must preserve the sample feature ID, product version, lifecycle state, provenance, and any domain-specific unit or classification. Failure must return an actionable error without destroying prior state.

9. Units and Methods

Purpose: Use Units and Methods within the governed Catalyst Data workflow.

Sample action: define kWh and the normalization method.

Steps

  1. Open or create the synthetic retrofit workspace.
  2. Select or navigate to this feature.
  3. Enter the matching row from the CSV or JSON sample.
  4. Review required fields, sources, units, permissions, assumptions, and warnings.
  5. Run or save the feature operation.
  6. Compare the result with the expected result below.
  7. Add a review note and preserve the feature state.

Expected result: explicit unit and method records.

Verification: The result must preserve the sample feature ID, product version, lifecycle state, provenance, and any domain-specific unit or classification. Failure must return an actionable error without destroying prior state.

10. Quality Rules

Purpose: Use Quality Rules within the governed Catalyst Data workflow.

Sample action: flag negative, duplicate, missing, or out-of-range values.

Steps

  1. Open or create the synthetic retrofit workspace.
  2. Select or navigate to this feature.
  3. Enter the matching row from the CSV or JSON sample.
  4. Review required fields, sources, units, permissions, assumptions, and warnings.
  5. Run or save the feature operation.
  6. Compare the result with the expected result below.
  7. Add a review note and preserve the feature state.

Expected result: quality findings.

Verification: The result must preserve the sample feature ID, product version, lifecycle state, provenance, and any domain-specific unit or classification. Failure must return an actionable error without destroying prior state.

11. Review and Revision

Purpose: Use Review and Revision within the governed Catalyst Data workflow.

Sample action: correct a duplicate while preserving history.

Steps

  1. Open or create the synthetic retrofit workspace.
  2. Select or navigate to this feature.
  3. Enter the matching row from the CSV or JSON sample.
  4. Review required fields, sources, units, permissions, assumptions, and warnings.
  5. Run or save the feature operation.
  6. Compare the result with the expected result below.
  7. Add a review note and preserve the feature state.

Expected result: a revision record.

Verification: The result must preserve the sample feature ID, product version, lifecycle state, provenance, and any domain-specific unit or classification. Failure must return an actionable error without destroying prior state.

12. Persistent Workspaces

Purpose: Use Persistent Workspaces within the governed Catalyst Data workflow.

Sample action: save datasets, views, queries, and notes.

Steps

  1. Open or create the synthetic retrofit workspace.
  2. Select or navigate to this feature.
  3. Enter the matching row from the CSV or JSON sample.
  4. Review required fields, sources, units, permissions, assumptions, and warnings.
  5. Run or save the feature operation.
  6. Compare the result with the expected result below.
  7. Add a review note and preserve the feature state.

Expected result: a reusable workspace.

Verification: The result must preserve the sample feature ID, product version, lifecycle state, provenance, and any domain-specific unit or classification. Failure must return an actionable error without destroying prior state.

13. Saved Queries

Purpose: Use Saved Queries within the governed Catalyst Data workflow.

Sample action: save a query for reviewed monthly observations.

Steps

  1. Open or create the synthetic retrofit workspace.
  2. Select or navigate to this feature.
  3. Enter the matching row from the CSV or JSON sample.
  4. Review required fields, sources, units, permissions, assumptions, and warnings.
  5. Run or save the feature operation.
  6. Compare the result with the expected result below.
  7. Add a review note and preserve the feature state.

Expected result: a versioned query.

Verification: The result must preserve the sample feature ID, product version, lifecycle state, provenance, and any domain-specific unit or classification. Failure must return an actionable error without destroying prior state.

14. Comparison Studio

Purpose: Use Comparison Studio within the governed Catalyst Data workflow.

Sample action: compare baseline and retrofit months.

Steps

  1. Open or create the synthetic retrofit workspace.
  2. Select or navigate to this feature.
  3. Enter the matching row from the CSV or JSON sample.
  4. Review required fields, sources, units, permissions, assumptions, and warnings.
  5. Run or save the feature operation.
  6. Compare the result with the expected result below.
  7. Add a review note and preserve the feature state.

Expected result: a normalized comparison.

Verification: The result must preserve the sample feature ID, product version, lifecycle state, provenance, and any domain-specific unit or classification. Failure must return an actionable error without destroying prior state.

15. Export Studio

Purpose: Use Export Studio within the governed Catalyst Data workflow.

Sample action: freeze the reviewed comparison into CSV, JSON, brief, and manifest.

Steps

  1. Open or create the synthetic retrofit workspace.
  2. Select or navigate to this feature.
  3. Enter the matching row from the CSV or JSON sample.
  4. Review required fields, sources, units, permissions, assumptions, and warnings.
  5. Run or save the feature operation.
  6. Compare the result with the expected result below.
  7. Add a review note and preserve the feature state.

Expected result: an integrity-protected export.

Verification: The result must preserve the sample feature ID, product version, lifecycle state, provenance, and any domain-specific unit or classification. Failure must return an actionable error without destroying prior state.

16. Public API

Purpose: Use Public API within the governed Catalyst Data workflow.

Sample action: return approved energy observations.

Steps

  1. Open or create the synthetic retrofit workspace.
  2. Select or navigate to this feature.
  3. Enter the matching row from the CSV or JSON sample.
  4. Review required fields, sources, units, permissions, assumptions, and warnings.
  5. Run or save the feature operation.
  6. Compare the result with the expected result below.
  7. Add a review note and preserve the feature state.

Expected result: scoped structured data.

Verification: The result must preserve the sample feature ID, product version, lifecycle state, provenance, and any domain-specific unit or classification. Failure must return an actionable error without destroying prior state.

17. Embeds

Purpose: Use Embeds within the governed Catalyst Data workflow.

Sample action: embed an approved energy trend table.

Steps

  1. Open or create the synthetic retrofit workspace.
  2. Select or navigate to this feature.
  3. Enter the matching row from the CSV or JSON sample.
  4. Review required fields, sources, units, permissions, assumptions, and warnings.
  5. Run or save the feature operation.
  6. Compare the result with the expected result below.
  7. Add a review note and preserve the feature state.

Expected result: a controlled visualization.

Verification: The result must preserve the sample feature ID, product version, lifecycle state, provenance, and any domain-specific unit or classification. Failure must return an actionable error without destroying prior state.

18. Institutional Access

Purpose: Use Institutional Access within the governed Catalyst Data workflow.

Sample action: give reviewers access without publication rights.

Steps

  1. Open or create the synthetic retrofit workspace.
  2. Select or navigate to this feature.
  3. Enter the matching row from the CSV or JSON sample.
  4. Review required fields, sources, units, permissions, assumptions, and warnings.
  5. Run or save the feature operation.
  6. Compare the result with the expected result below.
  7. Add a review note and preserve the feature state.

Expected result: role-aware permissions.

Verification: The result must preserve the sample feature ID, product version, lifecycle state, provenance, and any domain-specific unit or classification. Failure must return an actionable error without destroying prior state.

19. Connectors

Purpose: Use Connectors within the governed Catalyst Data workflow.

Sample action: retrieve a public utility or indicator feed.

Steps

  1. Open or create the synthetic retrofit workspace.
  2. Select or navigate to this feature.
  3. Enter the matching row from the CSV or JSON sample.
  4. Review required fields, sources, units, permissions, assumptions, and warnings.
  5. Run or save the feature operation.
  6. Compare the result with the expected result below.
  7. Add a review note and preserve the feature state.

Expected result: a logged connector run.

Verification: The result must preserve the sample feature ID, product version, lifecycle state, provenance, and any domain-specific unit or classification. Failure must return an actionable error without destroying prior state.

20. Refresh Operations

Purpose: Use Refresh Operations within the governed Catalyst Data workflow.

Sample action: refresh tariff data and reconcile exceptions.

Steps

  1. Open or create the synthetic retrofit workspace.
  2. Select or navigate to this feature.
  3. Enter the matching row from the CSV or JSON sample.
  4. Review required fields, sources, units, permissions, assumptions, and warnings.
  5. Run or save the feature operation.
  6. Compare the result with the expected result below.
  7. Add a review note and preserve the feature state.

Expected result: a refresh record and exception queue.

Verification: The result must preserve the sample feature ID, product version, lifecycle state, provenance, and any domain-specific unit or classification. Failure must return an actionable error without destroying prior state.

Expected output

  • a stable entity ID
  • a reusable indicator definition
  • a provenance source record
  • an evidence chain
  • a bounded analytical question
  • a versioned collection instrument
  • a registered dataset
  • traceable observations
  • explicit unit and method records
  • quality findings
  • a revision record
  • a reusable workspace
  • a versioned query
  • a normalized comparison
  • an integrity-protected export
  • scoped structured data
  • a controlled visualization
  • role-aware permissions
  • a logged connector run
  • a refresh record and exception queue

Whole-product verification

  • All 20 documented features are present or intentionally permission-restricted.
  • Every feature accepts its synthetic row or explains why it does not apply.
  • Errors preserve saved state and provide a recovery path.
  • Exports and handoffs retain provenance and version identity.
  • No private, confidential, or secret information appears in public output.

Responsible use

Governed data is not automatically true or fit for every purpose; preserve source rights, privacy, definitions, uncertainty, and review.

Scroll to Top