Technical Reference
Global Impact Catalyst: Technical Reference and Integrations
Review the technical, data, lifecycle, validation, and integration contract for Global Impact Catalyst.
Global Impact Catalyst · Technical Reference
Impact strategy, participation, theory of change, activities, outcomes, indicators, evidence, contribution, equity, safeguards, learning, monitoring, evaluation, reporting, and mapping.
Purpose
This reference summarizes the functional contract, record expectations, lifecycle, validation, export, compatibility, integration, privacy, and release-review requirements for Global Impact Catalyst.
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 | Impact Workspace | create GIC-RETROFIT-001 | a governed program-impact workspace | synthetic-demo |
| 2 | Problem and Context | describe energy burden, comfort inequity, affected groups, causes, and constraints | a contextual problem statement | synthetic-demo |
| 3 | Stakeholder Participation | record staff and community participation in framing and review | participation and consent records | synthetic-demo |
| 4 | Theory of Change | connect inputs, activities, outputs, outcomes, and assumptions | a reviewable causal pathway | synthetic-demo |
| 5 | Activities and Outputs | record control installation, envelope work, and staff training | activity and output records | synthetic-demo |
The downloadable files include all 18 feature rows.
Technical contract
Canonical identity
| Field | Value |
|---|---|
| Product slug | global-impact-catalyst |
| Product name | Global Impact Catalyst |
| Verified version | 1.5.0 |
| Content pack | 1.0.0 |
| Default article state | draft |
| Human review | required |
Functional surface
| Capability | Sample operation | Expected artifact |
|---|---|---|
| Impact Workspace | create GIC-RETROFIT-001 | a governed program-impact workspace |
| Problem and Context | describe energy burden, comfort inequity, affected groups, causes, and constraints | a contextual problem statement |
| Stakeholder Participation | record staff and community participation in framing and review | participation and consent records |
| Theory of Change | connect inputs, activities, outputs, outcomes, and assumptions | a reviewable causal pathway |
| Activities and Outputs | record control installation, envelope work, and staff training | activity and output records |
| Outcomes | define short-, medium-, and long-term energy and comfort changes | outcome definitions |
| Indicators | specify kWh, complaints, training, method, frequency, owner, and disaggregation | indicator records |
| Baselines and Targets | record baseline 45,000 kWh/month and a justified 36,000 target | baseline and target records |
| Evidence | link meter data, surveys, documents, and evaluation findings | evidence tied to outcomes |
| Contribution and Attribution | record weather, occupancy, and other influences | a contribution narrative with limits |
| Equity and Distribution | disaggregate comfort by room use and accessibility need | distributional findings |
| Risk and Safeguards | record disruption, exclusion, data, implementation, and reputation risks | risk and safeguard records |
| Learning Agenda | ask whether controls remain usable after six months | a prioritized learning plan |
| Monitoring | import routine monthly energy and comfort observations | a monitoring series |
| Evaluation | document an appropriate before/after or interrupted-time-series method | an evaluation plan and findings |
| Impact Reporting | publish a six-month brief with evidence and limits | a reviewable impact report |
| SDG and Framework Mapping | map relevant work to SDG 7 and 11 without implying certification | a contextual framework mapping |
| Decision Handoffs | attach approved outcome and risk records to Decision Studio | a typed impact handoff |
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
- Catalyst Data
- Decision Studio
- Knowledge Library
- Site Intelligence
- Catalyst Finance
- 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 impact washing, greenwashing, causal overclaim, token participation, and hidden distributional harm.