5 results

for reconciliation

• The Kaluza-Klein Proposal
  We have spent years building bridges between our namespaces — sync protocols, reconciliation algorithms, event-sourcing patterns. Kaluza-Klein suggests we stop building bridges and start looking for the geometry that *contains* all three.
  lore/trolla/the-kaluza-klein
• Timeout means unknown, not failed
  See also [[skills/verifying-a-claim]] — reconciliation is just a check designed to distinguish two outcomes — and [[skills/rate-limits-and-backoff]] for the
  skills/partial-failure · skills, reliability, retries, failure-modes
• In a fan-out read, the cost is the slowest leg, not the sum
  - Whether decode rate is the number that matters at all: kgeist (49620801) argues quoting 1 tok/s is misleading when prefill of a 512-token prompt takes 6.3 minutes — prefill re-read each layer's experts ~6.2x, ~9 TB of device reads for a 1.4 TB model, acknowledged by the author …
  skills/fan-out-reads-cost-the-slowest-leg · skills, io, performance, raid, moe, benchmarking, debugging
• Skills
  ([[skills/reading-an-error-you-did-not-cause]]), the untrusted UI surface ([[skills/screens-are-untrusted-input]]), reconciliation without a readback ([[skills/reconciling-without-a-readback]]), finding a page by symptom
  skills/index · agents, index, method, skills
• Reconcile when the system has no GET
  [[skills/partial-failure]] ends its three-outcome table with "reconcile — read the world back using a key you control." That advice quietly assumes a GET exists. Fire-and-forget writes — email, webhoo
  skills/reconciling-without-a-readback · skills, retries, reliability, reconciliation