Firefly (cache coherence protocol)¶

A three-state write-update cache-coherence protocol that keeps shared cache copies and main memory current on broadcast writes.

Version: v1 · 2026-09-08 · History
Domain-specific #: 4544
Origin domain: computer architecture
Subdomain: computer architecture

Core Idea¶

Its valid-exclusive, shared and dirty meanings depend on snooping and bus behavior; write update consumes bandwidth differently from invalidate protocols and the name is DEC-specific. Caches snoop bus transactions, broadcast modified words to every shared copy and memory and use a shared-line response to transition blocks among exclusive, shared and sole-dirty states. The abstraction is therefore identified by a declared carrier, a transformation or constraint over that carrier, and an invariant that tells an analyst whether the named structure is genuinely present.

Scope of Application¶

Firefly (cache coherence protocol) belongs to computer architecture and is useful where the analyst can specify the typed computer architecture carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets, then evaluate the processors caches and memory, cache-block state machine, read and write events, bus transactions and shared signal, update destinations, memory freshness, transition table and coherence and bandwidth properties are explicit. The scope is broad within that domain but bounded by the need for the processors caches and memory, cache-block state machine, read and write events, bus transactions and shared signal, update destinations, memory freshness, transition table and coherence and bandwidth properties are explicit.

Clarity¶

The abstraction clarifies a crowded vocabulary by making the processors caches and memory, cache-block state machine, read and write events, bus transactions and shared signal, update destinations, memory freshness, transition table and coherence and bandwidth properties are explicit the center of the account. A claim should name the carrier, the governing operation or relation, the applicable assumptions, and the recognition test.

Manages Complexity¶

Without the abstraction, an analyst must reason directly over many local details: the carrier roles, admissibility assumptions, competing conventions, derived invariants, boundary cases, and proof or validation obligations specific to Firefly (cache coherence protocol). Firefly (cache coherence protocol) compresses them into the roles in the structural signature. That compression permits comparison across instances without erasing the variables that determine validity. It also exposes which details may be varied safely and which are constitutive.

Abstract Reasoning¶

Identify the carrier. State what the elements, states, objects, or observations are: the typed computer architecture carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets. Reject examples whose alleged carrier belongs to a different problem. 2. Lock the constitutive rule. Express the processors caches and memory, cache-block state machine, read and write events, bus transactions and shared signal, update destinations, memory freshness, transition table and coherence and bandwidth properties are explicit independently of one notation or implementation.

Knowledge Transfer¶

Knowledge transfers strongly among subfields of computer architecture because they reuse the typed computer architecture carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets, Caches snoop bus transactions, broadcast modified words to every shared copy and memory and use a shared-line response to transition blocks among exclusive, shared and sole-dirty states., and type the carrier, state every parameter and convention in the definition, test that the processors caches and memory, cache-block state machine, read and write events, bus transactions and shared signal, update destinations, memory freshness, transition table and coherence and bandwidth properties are explicit, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases.

Relationships to Other Abstractions¶

Current abstraction Firefly (cache coherence protocol) Domain-specific

Parents (1) — more general patterns this builds on

Firefly (cache coherence protocol) is a kind of Synchronization Prime

The proposed strict upward parent is prime:synchronization.

Neighborhood in Abstraction Space¶

Firefly (cache coherence protocol) sits in a crowded region of the domain-specific corpus (27^th percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.

Family — Memory Architecture & Parallel Computing (34 abstractions)

Nearest neighbors

Cache coherence — 0.93
CPU cache — 0.92
Cache hierarchy — 0.92
MERSI protocol — 0.91
Shared memory — 0.90

Computed from structural-signature embeddings · 2026-09-08