Tools and Features

Sustainable Catalyst Platform Core: Feature-by-Feature Guide

Use every documented Sustainable Catalyst Platform Core feature with sample input and expected output.

ProductSustainable Catalyst Platform CoreVerified versioncurrentComponentArtifact Registry, Audit Events, Backup and Recovery, Compatibility, Configuration, Cross-Product Navigation, Embeds, Feature Flags, Governance Policies, Handoff Contracts, Identity and Access, Migration, Observability, Product Registry, Public API Keys, Rate Limits, Release Integrity, Secrets Boundaries, Service Health, Shared Taxonomies, Typed Schemas, Version RegistryUpdatedJuly 17, 2026Reading time18 minutes
← Back to product guides

Sustainable Catalyst Platform Core · Technical Reference

Shared product identity, versions, taxonomies, schemas, handoffs, artifacts, access, configuration, health, observability, audits, compatibility, migration, recovery, keys, limits, embeds, integrity, navigation, and governance.

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

Last verified version: current

Reading time: 18–30 minutes

Status: Published support documentation.

Purpose

This is the complete documented feature inventory for Sustainable Catalyst Platform Core version current. 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 Product Registry register canonical product ID, owner, route, and lifecycle a canonical product record synthetic-demo
2 Version Registry record installed, compatible, superseded, and retired versions a version compatibility record synthetic-demo
3 Shared Taxonomies reuse product, version, component, issue, release, topic, and artifact terms consistent cross-product context synthetic-demo
4 Typed Schemas validate a Decision Packet or calculation handoff a schema result synthetic-demo
5 Handoff Contracts send a Workbench artifact to Decision Studio with minimum fields and receipt a typed transfer and receipt synthetic-demo

The downloadable files include all 22 feature rows.

Feature-by-feature procedure

1. Product Registry

Purpose: Use Product Registry within the governed Sustainable Catalyst Platform Core workflow.

Sample action: register canonical product ID, owner, route, and lifecycle.

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 canonical product 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.

2. Version Registry

Purpose: Use Version Registry within the governed Sustainable Catalyst Platform Core workflow.

Sample action: record installed, compatible, superseded, and retired versions.

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 version compatibility 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.

3. Shared Taxonomies

Purpose: Use Shared Taxonomies within the governed Sustainable Catalyst Platform Core workflow.

Sample action: reuse product, version, component, issue, release, topic, and artifact terms.

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: consistent cross-product context.

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. Typed Schemas

Purpose: Use Typed Schemas within the governed Sustainable Catalyst Platform Core workflow.

Sample action: validate a Decision Packet or calculation handoff.

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 schema result.

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. Handoff Contracts

Purpose: Use Handoff Contracts within the governed Sustainable Catalyst Platform Core workflow.

Sample action: send a Workbench artifact to Decision Studio with minimum fields and receipt.

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 typed transfer and receipt.

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. Artifact Registry

Purpose: Use Artifact Registry within the governed Sustainable Catalyst Platform Core workflow.

Sample action: register a dataset, model, decision, document, or report.

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 discoverable artifact 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.

7. Identity and Access

Purpose: Use Identity and Access within the governed Sustainable Catalyst Platform Core workflow.

Sample action: grant an editor documentation rights without administrative control.

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 least-privilege assignment.

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. Configuration

Purpose: Use Configuration within the governed Sustainable Catalyst Platform Core workflow.

Sample action: set supported backend URLs and feature settings.

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 validated environment configuration.

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. Secrets Boundaries

Purpose: Use Secrets Boundaries within the governed Sustainable Catalyst Platform Core workflow.

Sample action: reference an environment variable instead of storing the key.

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 secret reference without secret value.

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. Service Health

Purpose: Use Service Health within the governed Sustainable Catalyst Platform Core workflow.

Sample action: check version, dependencies, readiness, and time.

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 health response.

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. Observability

Purpose: Use Observability within the governed Sustainable Catalyst Platform Core workflow.

Sample action: inspect logs, metrics, traces, and handoff failures.

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 operational diagnostic.

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. Audit Events

Purpose: Use Audit Events within the governed Sustainable Catalyst Platform Core workflow.

Sample action: record a taxonomy migration or permission change.

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 tamper-aware event.

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. Feature Flags

Purpose: Use Feature Flags within the governed Sustainable Catalyst Platform Core workflow.

Sample action: enable a new route for a bounded cohort and preserve rollback.

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 rollout state.

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. Compatibility

Purpose: Use Compatibility within the governed Sustainable Catalyst Platform Core workflow.

Sample action: test old and new artifact readers.

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 compatibility decision.

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. Migration

Purpose: Use Migration within the governed Sustainable Catalyst Platform Core workflow.

Sample action: move a v1 artifact to v2 with backup and receipt.

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 migration 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.

16. Backup and Recovery

Purpose: Use Backup and Recovery within the governed Sustainable Catalyst Platform Core workflow.

Sample action: create and test a shared-registry recovery point.

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 verified backup.

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. Public API Keys

Purpose: Use Public API Keys within the governed Sustainable Catalyst Platform Core workflow.

Sample action: issue a read-only scoped key.

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 revocable credential.

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. Rate Limits

Purpose: Use Rate Limits within the governed Sustainable Catalyst Platform Core workflow.

Sample action: define fair public usage and response behavior.

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 visible limit policy.

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. Embeds

Purpose: Use Embeds within the governed Sustainable Catalyst Platform Core workflow.

Sample action: serve a trusted versioned public component.

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 embed contract.

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. Release Integrity

Purpose: Use Release Integrity within the governed Sustainable Catalyst Platform Core workflow.

Sample action: verify package root, manifest, checksums, tests, and version identity.

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 release-integrity report.

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.

21. Cross-Product Navigation

Purpose: Use Cross-Product Navigation within the governed Sustainable Catalyst Platform Core workflow.

Sample action: preserve return paths and artifact context.

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: stable navigation.

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.

22. Governance Policies

Purpose: Use Governance Policies within the governed Sustainable Catalyst Platform Core workflow.

Sample action: enforce publication, privacy, retention, review, and automation boundaries.

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 cross-product policy decision.

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 canonical product record
  • a version compatibility record
  • consistent cross-product context
  • a schema result
  • a typed transfer and receipt
  • a discoverable artifact record
  • a least-privilege assignment
  • a validated environment configuration
  • a secret reference without secret value
  • a health response
  • an operational diagnostic
  • a tamper-aware event
  • a controlled rollout state
  • a compatibility decision
  • a migration record
  • a verified backup
  • a revocable credential
  • a visible limit policy
  • a bounded embed contract
  • a release-integrity report
  • stable navigation
  • a cross-product policy decision

Whole-product verification

  • All 22 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

Core changes can affect every product; use least privilege, backups, compatibility tests, secret rotation, staged rollout, and explicit approval.

Scroll to Top