Technical Reference
Decision Studio: Technical Reference and Integrations
Review the technical, data, lifecycle, validation, and integration contract for Decision Studio.
Decision Studio · Technical Reference
Auditable decision packets, evidence, scenarios, tradeoffs, risk, briefing, publication, monitoring, and reassessment.
Purpose
This reference summarizes the functional contract, record expectations, lifecycle, validation, export, compatibility, integration, privacy, and release-review requirements for Decision Studio.
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 | Decision Packet | create DS-RETROFIT-001 for a community-center retrofit choice | a versioned packet containing all decision artifacts | synthetic-demo |
| 2 | Problem Framing | define the decision, scope, objectives, constraints, stakeholders, and deadline | a bounded decision statement | synthetic-demo |
| 3 | Evidence Ledger | add utility bills and an engineering assessment with relevance and confidence | traceable evidence records | synthetic-demo |
| 4 | Scenario Studio | compare no action, controls-only, and whole-building retrofit | a scenario table with aligned measures | synthetic-demo |
| 5 | Impact Records | record cost, emissions, comfort, disruption, and equity effects | structured impact entries | synthetic-demo |
The downloadable files include all 16 feature rows.
Technical contract
Canonical identity
| Field | Value |
|---|---|
| Product slug | decision-studio |
| Product name | Decision Studio |
| Verified version | 2.0.0 |
| Content pack | 1.0.0 |
| Default article state | draft |
| Human review | required |
Functional surface
| Capability | Sample operation | Expected artifact |
|---|---|---|
| Decision Packet | create DS-RETROFIT-001 for a community-center retrofit choice | a versioned packet containing all decision artifacts |
| Problem Framing | define the decision, scope, objectives, constraints, stakeholders, and deadline | a bounded decision statement |
| Evidence Ledger | add utility bills and an engineering assessment with relevance and confidence | traceable evidence records |
| Scenario Studio | compare no action, controls-only, and whole-building retrofit | a scenario table with aligned measures |
| Impact Records | record cost, emissions, comfort, disruption, and equity effects | structured impact entries |
| Claim Review | review the claim that the project pays back in five years | a supported, contested, or unresolved claim state |
| Finance Tradeoffs | compare capital, operating, lifecycle, and uncertainty considerations | a transparent tradeoff record |
| Risk and Recovery | record contractor delay, budget overrun, rollback, and recovery | a risk register with owners and mitigations |
| Assumption Register | record 3% annual tariff growth with source and confidence | a versioned assumption |
| Workbench Handoffs | request lifecycle-cost and emissions calculations | a returned calculation artifact and receipt |
| Readiness Review | check evidence, privacy, unresolved issues, and approval requirements | an advisory readiness report |
| Briefing Studio | assemble a board briefing from reviewed packet sections | an executive brief |
| Publication Studio | prepare a redacted public decision summary | a controlled publication artifact |
| Outcomes Monitoring | track six months of post-retrofit energy and comfort data | outcome records and variance explanations |
| Reassessment | reopen the decision after grant or outcome changes | a new review cycle preserving history |
| API and Embeds | expose an approved public packet summary | a scoped privacy-aware JSON or embed |
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
- Workbench
- Catalyst Finance
- Catalyst Data
- Site Intelligence
- Knowledge Library
- Narrative Risk
- 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
The product organizes evidence and reasoning; accountable decision owners, due process, experts, and institutional approvals remain necessary.