Technical Reference
Catalyst Narrative Risk: Technical Reference and Integrations
Review the technical, data, lifecycle, validation, and integration contract for Catalyst Narrative Risk.
Catalyst Narrative Risk · Technical Reference
Claims, sources, evidence, narrative mapping, risk dimensions, scoring, uncertainty, cases, comparison, review, approval, governance, and handoffs.
Purpose
This reference summarizes the functional contract, record expectations, lifecycle, validation, export, compatibility, integration, privacy, and release-review requirements for Catalyst Narrative Risk.
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 | Case Workspace | create NR-RETROFIT-001 | a persistent narrative-risk case | synthetic-demo |
| 2 | Artifact Intake | register a public retrofit announcement with URL, date, version, and custody | a source-preserved communication artifact | synthetic-demo |
| 3 | Claim Decomposition | separate cost, emissions, comfort, and timeline claims | atomic claim records | synthetic-demo |
| 4 | Narrative Mapping | map frames, causal stories, heroes, harms, omissions, and implied action | a structured narrative map | synthetic-demo |
| 5 | Actor and Audience Context | record speaker, institution, intended audience, affected groups, and power context | actor and audience records | synthetic-demo |
The downloadable files include all 16 feature rows.
Technical contract
Canonical identity
| Field | Value |
|---|---|
| Product slug | narrative-risk |
| Product name | Catalyst Narrative Risk |
| Verified version | 1.5.0 |
| Content pack | 1.0.0 |
| Default article state | draft |
| Human review | required |
Functional surface
| Capability | Sample operation | Expected artifact |
|---|---|---|
| Case Workspace | create NR-RETROFIT-001 | a persistent narrative-risk case |
| Artifact Intake | register a public retrofit announcement with URL, date, version, and custody | a source-preserved communication artifact |
| Claim Decomposition | separate cost, emissions, comfort, and timeline claims | atomic claim records |
| Narrative Mapping | map frames, causal stories, heroes, harms, omissions, and implied action | a structured narrative map |
| Actor and Audience Context | record speaker, institution, intended audience, affected groups, and power context | actor and audience records |
| Source Ledger | preserve origin, retrieval, version, and custody | a source ledger |
| Evidence Ledger | link each claim to supporting, challenging, and contextual evidence | claim-evidence relationships |
| Risk Dimensions | assess accuracy, omission, uncertainty, harm, manipulation, governance, and reputation | dimension-level evidence and scores |
| Scoring Method | apply the canonical transparent scoring rubric | a method-versioned score and rationale |
| Uncertainty | record missing evidence, ambiguity, confidence, and reviewer disagreement | an uncertainty record |
| Counterevidence | add contractor-capacity and timeline challenges | a balanced evidence view |
| Comparison | compare draft and final announcements or two cases | a change and risk comparison |
| Review Workflow | request factual, harm, and governance review | a review trail |
| Approval | require authorized approval for an official assessment | an approval record and rationale |
| Governance Log | record method changes, overrides, conflicts, and score revisions | an auditable event log |
| Exports and Handoffs | send an approved risk summary to Decision Studio | a portable privacy-aware artifact |
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
- Product Support Platform
- Site Intelligence
- 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 automated accusation, profiling, or definitive judgments; preserve context, counterevidence, uncertainty, and human review.