resonate-external-system-of-record-pattern-typescript

Coordinate cross-system writes using Write Last, Read First with durable execution.

6|Updated Jan 8, 2026

Search Tags:#typescript #durable-execution #system-of-record #external-system-of-record #idempotent-retries #distributed-pattern

Ready to run

npx skills add https://github.com/resonatehq/resonate-skills --skill resonate-external-system-of-record-pattern-typescript

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: resonate-external-system-of-record-pattern-typescript
Source: https://github.com/resonatehq/resonate-skills/tree/main/resonate-external-system-of-record-pattern-typescript
Command: npx skills add https://github.com/resonatehq/resonate-skills --skill resonate-external-system-of-record-pattern-typescript

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Solve cross-system data consistency without distributed transactions.

Core Features & Use Cases

Write Last, Read First principle to order operations between system of reference and system of record.
Durable execution with automatic recovery and idempotent retries to tolerate crashes and retries.
Clear guidance for recovery, rollback, and invariant checks across multi-system integrations.

Quick Start

Apply the Write Last, Read First pattern by staging writes to a reference system before committing to the system of record.

Frequently Asked Questions about resonate-external-system-of-record-pattern-typescript

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I maintain cross-system data consistency without distributed transactions?▼

To maintain cross-system data consistency without distributed transactions, stage writes to a reference system first, then commit to the system of record to enforce the Write Last, Read First principle.

What is the Write Last, Read First pattern for external systems of record?▼

The Write Last, Read First pattern orders operations by staging writes to a reference system before committing them to the system of record, ensuring system-wide consistency without transactions.

How do I handle crash recovery and idempotent retries during multi-system integrations?▼

Handle crash recovery and idempotent retries in multi-system integrations by using durable execution to automatically recover operations and tolerate crashes without duplicating writes to the system of record.

When should I use invariant checks with ctx.panic for external system conflicts?▼

Use invariant checks with ctx.panic for external system conflicts when coordinating writes between systems and you need to immediately halt execution upon detecting data consistency violations.

Does this durable execution pattern work with TypeScript integrations?▼

Yes, this durable execution pattern is implemented for TypeScript integrations, providing crash-recovery guarantees and idempotent retries for coordinating writes across external systems of record.

What are the limitations of coordinating writes without distributed transactions?▼

Coordinating writes without distributed transactions requires careful staging in a reference system and invariant checks to handle conflicts, meaning you rely on durable execution rather than ACID guarantees across systems.