Technical Reference
Catalyst Canvas: Technical Reference and Integrations
Review the technical, data, lifecycle, validation, and integration contract for Catalyst Canvas.
Catalyst Canvas · Technical Reference
Problem framing, stakeholders, personas, journeys, evidence, assumptions, research, concepts, prototypes, tests, learning, review, and handoffs.
Purpose
This reference summarizes the functional contract, record expectations, lifecycle, validation, export, compatibility, integration, privacy, and release-review requirements for Catalyst Canvas.
Prerequisites
- Current release notes and repository documentation
- A test environment
- A backup and rollback plan
- Access to product health or package checks
- The synthetic all-feature sample
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 | Project Workspace | create CANVAS-RETROFIT-001 with owner and status | a persistent project | synthetic-demo |
| 2 | Challenge Frame | describe energy, comfort, users, desired change, and boundaries | a concise challenge statement | synthetic-demo |
| 3 | Stakeholder Map | map visitors, staff, facilities, funders, and contractors | a stakeholder network | synthetic-demo |
| 4 | Personas | create an evidence-bounded facilities-manager persona | a persona separating evidence from inference | synthetic-demo |
| 5 | Journey Map | map room booking, comfort complaints, and facilities response | a stage-based journey | synthetic-demo |
The downloadable files include all 18 feature rows.
Technical contract
Canonical identity
| Field | Value |
|---|---|
| Product slug | catalyst-canvas |
| Product name | Catalyst Canvas |
| Verified version | 2.0.0 |
| Content pack | 1.0.0 |
| Default article state | draft |
| Human review | required |
Functional surface
| Capability | Sample operation | Expected artifact |
|---|---|---|
| Project Workspace | create CANVAS-RETROFIT-001 with owner and status | a persistent project |
| Challenge Frame | describe energy, comfort, users, desired change, and boundaries | a concise challenge statement |
| Stakeholder Map | map visitors, staff, facilities, funders, and contractors | a stakeholder network |
| Personas | create an evidence-bounded facilities-manager persona | a persona separating evidence from inference |
| Journey Map | map room booking, comfort complaints, and facilities response | a stage-based journey |
| Point of View | synthesize user, need, and insight | a reviewable POV statement |
| How Might We | ask how to reduce energy without hiding comfort tradeoffs | bounded design questions |
| Evidence Ledger | add utility bills, observations, and interviews | source-linked evidence records |
| Assumption Ledger | record that staff will use a dashboard weekly | an assumption with risk and test |
| Research Plan | plan interviews, meter review, ethics, and outputs | a governed plan |
| Idea Generation | generate sensor, scheduling, controls, and training concepts | an idea set linked to needs |
| Concept Selection | score concepts on feasibility, impact, equity, and evidence | a transparent selection rationale |
| Prototype Plan | define a comfort-and-energy dashboard prototype | a bounded prototype specification |
| Test Plan | test whether staff can identify an overheating zone | a task script and success measures |
| Learning Log | record that users misread a comfort score | a chronological learning entry |
| Review Workflow | request research and accessibility review | a human review trail |
| Comparison | compare two dashboard concepts using aligned criteria | a side-by-side evidence view |
| Export and Handoffs | send the chosen concept to Decision Studio | a portable bundle and receipt |
Core record fields
- Stable record or artifact ID
- Product and schema version
- Created and updated time
- Owner or responsible role
- Lifecycle or review state
- Source and provenance
- Units, period, geography, classification, or audience where applicable
- Validation findings and uncertainty
- Privacy and publication boundary
- Export or handoff integrity metadata
Lifecycle
Use a human-controlled lifecycle such as draft → review → approved/published, with revise, superseded, archived, withdrawn, failed, and recovered states where appropriate. Automated analysis may recommend; it must not silently approve, publish, or create private cases.
Validation
- Required-field and type checks
- Identifier and relationship checks
- Unit, period, geography, method, and classification compatibility
- Product and schema compatibility
- Source, evidence, and provenance completeness
- Permission, privacy, and publication-boundary checks
- Deterministic checksum or fingerprint validation for portable artifacts
Integrations
- Decision Studio
- Knowledge Library
- Catalyst Data
- Research Lab
- Product Support Platform
- Platform Core
Send the minimum required fields through a typed contract. Preserve source product, destination, schema, artifact ID, review state, provenance, consent or privacy boundary, and receipt. Private Contact and Engagement records never belong in public support or research artifacts.
Release review
- Confirm interface, service, manifest, package, and schema versions.
- Validate the all-feature sample.
- Run product tests and integrity checks.
- Test one export and each supported handoff category.
- Document breaking changes and migration path.
- Update Last Verified Version before publishing this article.
Expected output
- A complete feature contract
- A validated synthetic export
- A compatibility decision
- A documented integration receipt
- A release-integrity report
Verification
- Product slug, version, schema, and IDs agree.
- Every documented feature maps to an actual interface, command, route, or record.
- The sample files produce the stated artifacts.
- Integrations preserve provenance and privacy.
- Migration, rollback, support, and release documentation are current.
Responsible use
Avoid fabricated personas, extractive research, sensitive-data collection without safeguards, and claims unsupported by evidence.