Worked Examples

Sustainable Catalyst Platform Core: End-to-End Sample Workflow

Complete an all-feature retrofit demonstration in Sustainable Catalyst Platform Core.

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 · How-to Guide

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 end-to-end workflow demonstrates every documented Sustainable Catalyst Platform Core capability through one fictional resilient-community-retrofit case. The objective is not to prove a real-world conclusion; it is to verify the complete product workflow with controlled data.

Prerequisites

  • The current product release
  • A new synthetic workspace
  • The all-feature CSV and JSON
  • No production or private information
  • Time to review every checkpoint

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.

Procedure

Scenario

A community center is assessing energy, comfort, financing, implementation, evidence, and monitoring needs. Use only the supplied fictional records.

  1. 1. Product Registry: register canonical product ID, owner, route, and lifecycle. Confirm a canonical product record.
  2. 2. Version Registry: record installed, compatible, superseded, and retired versions. Confirm a version compatibility record.
  3. 3. Shared Taxonomies: reuse product, version, component, issue, release, topic, and artifact terms. Confirm consistent cross-product context.
  4. 4. Typed Schemas: validate a Decision Packet or calculation handoff. Confirm a schema result.
  5. 5. Handoff Contracts: send a Workbench artifact to Decision Studio with minimum fields and receipt. Confirm a typed transfer and receipt.
  6. 6. Artifact Registry: register a dataset, model, decision, document, or report. Confirm a discoverable artifact record.
  7. 7. Identity and Access: grant an editor documentation rights without administrative control. Confirm a least-privilege assignment.
  8. 8. Configuration: set supported backend URLs and feature settings. Confirm a validated environment configuration.
  9. 9. Secrets Boundaries: reference an environment variable instead of storing the key. Confirm a secret reference without secret value.
  10. 10. Service Health: check version, dependencies, readiness, and time. Confirm a health response.
  11. 11. Observability: inspect logs, metrics, traces, and handoff failures. Confirm an operational diagnostic.
  12. 12. Audit Events: record a taxonomy migration or permission change. Confirm a tamper-aware event.
  13. 13. Feature Flags: enable a new route for a bounded cohort and preserve rollback. Confirm a controlled rollout state.
  14. 14. Compatibility: test old and new artifact readers. Confirm a compatibility decision.
  15. 15. Migration: move a v1 artifact to v2 with backup and receipt. Confirm a migration record.
  16. 16. Backup and Recovery: create and test a shared-registry recovery point. Confirm a verified backup.
  17. 17. Public API Keys: issue a read-only scoped key. Confirm a revocable credential.
  18. 18. Rate Limits: define fair public usage and response behavior. Confirm a visible limit policy.
  19. 19. Embeds: serve a trusted versioned public component. Confirm a bounded embed contract.
  20. 20. Release Integrity: verify package root, manifest, checksums, tests, and version identity. Confirm a release-integrity report.
  21. 21. Cross-Product Navigation: preserve return paths and artifact context. Confirm stable navigation.
  22. 22. Governance Policies: enforce publication, privacy, retention, review, and automation boundaries. Confirm a cross-product policy decision.

Save and review

  1. Save the final workspace under the sample workspace ID.
  2. Close and reopen it in a clean session.
  3. Compare every feature result with the sample expected_result field.
  4. Document unresolved differences and do not hide warnings.
  5. Export one complete artifact bundle.
  6. Send one supported handoff to an integration and verify its receipt.

Supported integrations

  • Every Sustainable Catalyst product
  • WordPress
  • FastAPI services
  • GitHub
  • Hosting and edge infrastructure

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
  • A complete saved workspace
  • A portable export
  • A validated cross-product handoff receipt

Verification

  • Every CSV feature row has a corresponding saved result.
  • The JSON workspace ID and product version are preserved.
  • The export can be inspected without temporary browser state.
  • The receiving product identifies source, destination, schema, artifact, and review state.
  • A human reviewer can reproduce or audit the demonstration.

Responsible use

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

Replace synthetic data only with information you are authorized to use, after reassessing licensing, privacy, uncertainty, and review obligations.

Scroll to Top