Go Distributed

Name: Go Distributed
Author: Dankosik

ASecurity

Use when cross-service consistency, replay, ordering, compensation, redrive, or reconciliation must survive process or owner boundaries.

7 stars

0 votes

0 copies

0 views

Added 9/24/2026

developmentgosql

Works with

terminal

Security Analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned 9/24/2026

$npx -y skills add Dankosik/go-service-template-rest --skill go-distributed --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Go Distributed?

Add the live security badge to your README — it updates automatically with every re-scan.

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/dankosik-go-distributed/badge)](https://www.skillsdirectory.com/skills/dankosik-go-distributed)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

Files

SKILL.md

---
name: go-distributed
description: "Use when cross-service consistency, replay, ordering, compensation, redrive, or reconciliation must survive process or owner boundaries."
metadata:
  invocation: model
  kind: method
---

# Go Distributed

A cross-service flow is defined by its **recovery**.

`flow contract -> durable steps -> partial failure -> ordering and duplicates -> compensation -> redrive -> reconciliation -> proof`

For a delegated Decision or Review, or when the active artifact requires its
result interface, load the
[shared specialist contract](../../contracts/specialist-contract.md).
Trace every accepted producer effect through terminal reconciliation. For
interacting effects, exhaustive recovery-path coverage, or a decision/review
handoff, record
`DurableStep{identity, authority, commit, duplicate, reorder, unknown,
compensate, redrive, reconcile, proof}` per step. A single local path can keep
its judgment and evidence in the code or existing task artifact. Replay duplicate
delivery, reordering, partial completion, process loss, redrive, and mixed
versions. Each step is idempotent under redelivery or has a named compensation;
ordering exists only where a key serializes it; reconciliation distinguishes
applied, unapplied, and unknown.

Read the mechanism present in this checkout before changing policy:
[PostgreSQL Transactional Outbox](../../../docs/postgres-transactional-outbox.md)
owns its transaction, fencing, ordering, retry, redrive, retention, and outcome
classification; [NATS JetStream](../../../docs/durable-messaging.md) owns its
publication identity, acknowledgements, and dead-letter transfer. An absent pack
is a selected profile, not a gap. Reuse the existing pack and reject a second
publication path without a distinct invariant.

For a **Decision**, first prove cross-service coordination is necessary and load
[compensation guidance](references/decision/pivot-compensation-and-forward-recovery.md)
only when another owner already performed an effect. For **Review**, replay each
affected step against its pack contract. Complete when every step has an
invariant, recovery or compensation, reconciliation action, and focused proof.

Load [reliable messaging](../../../docs/universal-disciplines/reliable-messaging/SKILL.md)
for broker guarantees and [distributed system
design](../../../docs/universal-disciplines/distributed-system-design/SKILL.md)
when multiple coordination mechanisms change topology.

Attribution

Dankosik

View source See grades on GitHub More from Dankosik →

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

--- name: go-distributed description: "Use when cross-service consistency, replay, ordering, compensation, redrive, or reconciliation must survive process or owner boundaries." metadata: invocation: model kind: method --- # Go Distributed A cross-service flow is defined by its **recovery**. `flow contract -> durable steps -> partial failure -> ordering and duplicates -> compensation -> redrive -> reconciliation -> proof` For a delegated Decision or Review, or when the active artifact requires its result interface, load the [shared specialist contract](../../contracts/specialist-contract.md). Trace every accepted producer effect through terminal reconciliation. For interacting effects, exhaustive recovery-path coverage, or a decision/review handoff, record `DurableStep{identity, authority, commit, duplicate, reorder, unknown, compensate, redrive, reconcile, proof}` per step. A single local path can keep its judgment and evidence in the code or existing task artifact. Replay duplicate delivery, reordering, partial completion, process loss, redrive, and mixed versions. Each step is idempotent under redelivery or has a named compensation; ordering exists only where a key serializes it; reconciliation distinguishes applied, unapplied, and unknown. Read the mechanism present in this checkout before changing policy: [PostgreSQL Transactional Outbox](../../../docs/postgres-transactional-outbox.md) owns its transaction, fencing, ordering, retry, redrive, retention, and outcome classification; [NATS JetStream](../../../docs/durable-messaging.md) owns its publication identity, acknowledgements, and dead-letter transfer. An absent pack is a selected profile, not a gap. Reuse the existing pack and reject a second publication path without a distinct invariant. For a **Decision**, first prove cross-service coordination is necessary and load [compensation guidance](references/decision/pivot-compensation-and-forward-recovery.md) only when another owner already performed an effect. For **Review**, replay each affected step against its pack contract. Complete when every step has an invariant, recovery or compensation, reconciliation action, and focused proof. Load [reliable messaging](../../../docs/universal-disciplines/reliable-messaging/SKILL.md) for broker guarantees and [distributed system design](../../../docs/universal-disciplines/distributed-system-design/SKILL.md) when multiple coordination mechanisms change topology.