Compendium · Atoms · Reconciliation & Drift

Reconciliation & Drift

Items

of 1002 total

Atomic primitives in the reconciliation & drift family. Click any tile for the live render, the spec it was built from, and the code that fell out.

Featured 14 Atoms 762 Compositions 240

Drift Signals · 20

#201 go

2026-05-21 09:14 WATCH

SPEC-038 · auth/session.ttl

session TTL fell from 24h to 12h in prod

#202 go

DRIFT-072 / SPEC-038

Session TTL drifted from 24h spec to 12h prod after security review tightened the policy. Intent matched, spec lagged.

ACCEPTABLE-DRIFT

@governor · 2026-05-21

#203 go

DDL ON-TARGET

#204 go

// diff · SPEC-038 DRIFT

spec

24h

≠

prod

12h

#205 go

ad-hoc | CR-1142

Change request arrived outside the active spec on surface checkout.tax-rounding.

route → RE

#206 go

SMALL GAP

+ 1 criterion

Spec is fundamentally correct. Add the missing acceptance criterion and re-validate.

missing → rate-limit 10/min per identity

#207 go

MEDIUM GAP

update spec

Intent has materially moved. Update the spec, then re-validate against existing assurance.

route → SPEC-UPDATE

#208 go

LARGE GAP

spec + assurance + recompose

1. rewrite spec from current intent
2. rebuild assurance suite
3. recompose implementation

#209 de

DRIFT-072 ticket

root cause dependency upgrade narrowed default TTL

#210 go

// drift · 12 weeks TREND

min 3 max 12

11 this week

#211 go

classifier confidence MEDIUM

0% 50% 80% 78%

#212 go

// drift buckets · 30 days n=60

ACCEPTABLE
70%REGRESSION
18%UNKNOWN
12%

#213 go

trace · step 7 OFF-INTENT

Step 7 chose to expire sessions at 12h to reduce risk — but spec mandates 24h for UX.

#214 go

// codebase audit · auth/

Every handler silently rejects emails with leading dots. No spec mentions this rule. Six services have learned it by copy-paste.

UNWRITTEN CONVENTION

DETECTED

@governor · 2026-05-21

#215 go

integration surface

payments.stripe.webhook

risk HIGH

#216 go

// heatmap cell

SPEC-038

security

#217 de

routing decision · reconciliation engine

#218 go

// drift cause taxonomy

ENVDEPENDENCYINTENT-SHIFTREGRESSION

Each drift event is tagged with exactly one cause from this closed set.

#219 go

// drift cadence · last 30d

day 1 DRIFT-072 day 30

#220 go

// spec/prod parity · portfolio DRIFTING

84%

0% 70 90 100%

Change Routing · 20

#1041 go

// inbox · CR-2041

Field-team request: add a hard cap on weekend retries. No matching acceptance criterion in any active spec. Awaiting routing verdict.

OUT-OF-SPEC

REQUEST

CR-2041 · 2026-05-21

#1042 go

// triage · CR-2041 gap 42

SMALL 0–25 PLAN-AMEND
MEDIUM 26–60 SPEC-UPDATE
LARGE 61–100 RE

#1043 go

// routing decision

request CR-2041 · gap 78

#1044 de

// routing decision

request CR-2042 · in-spec

#1045 go

// routing decision

amends SPEC-038 · gap 42

#1046 de

CR-2041 change request

requested by @author Weekend retry storm flooded the queue; cap retries at 3/hour per tenant.

#1047 de

// inbox row

CR-2043 @author cap weekend retries gap 68 RE

#1048 go

CO paused pending RE

RE-0118 · spec-038 under reconciliation

composition will resume on verdict

#1049 de

// timeline · 2026-05-21 14:02

RE-0118 returned verdict: spec amendment merged, intent preserved. Composition queue resumes on next tick.

RESUME

COMPOSITION

RE-0118 · @governor

#1050 go

// routing tree · node 02

#1051 go

// impact heatmap cell

CR-2041

billing-api

#1052 de

// SPEC-038 amendment · from CR-2041

+1 AC

new acceptance criterion

Retries are capped at 3 per hour per tenant on weekend windows.

#1053 de

// SPEC-038 amendment · from CR-2042

+1 SECTION

new spec section

## Weekend Retry Policy

#1054 go

// router verdict · RE-0118

RECOMPOSE

REQUIRED

spec SPEC-038 artefacts 42 action discard + rebuild

#1055 de

// plan · PLAN-2026-W21

Small-gap fold: weekend retry cap incorporated as a task on the active plan. Spec untouched, ICS unchanged.

PLAN

AMENDED

+3 tasks · @author

#1056 go

CSG violation rule.csg-04

Routed change to SPEC-038 contradicts an active criterion in SPEC-019.

SPEC-038 vs SPEC-019

#1057 de

// batch BATCH-2026-W21 · 5 changes

progress 2 / 5 routed

#1058 go

CR-2044 two routes match

recommended

SPEC-UPDATE

fold into active spec

alternative

RELEASE REVIEW

ship as-is, no spec change

#1059 go

// CR-2041 · reassigned

@author → @governor

routed verdict requires governor sign-off

#1060 go

// change ledger · append-only

# 2026-05-21T14:02 CR-2041 @gatekeeper RE

Retroactive Speccing · 20

#1061 do

// src/billing/proration.ts

Prorate refunds to the nearest minute when a customer downgrades mid-cycle — recovered from three years of bug fixes and one handwritten comment on line 41.

INTENT

RECOVERED

@author · 2026-05-21

#1062 do

SPEC-114 PROVISIONAL

Refund Proration

Prorate refunds to the nearest minute when a downgrade occurs mid-billing-cycle.

#1063 do

// characterisation test LOCKED

refunds rounded to whole minute

billing/proration.ts

in downgrade @ 12:34:29 out refund credit = 25 min

#1064 do

SPEC-114 · meta

id: SPEC-114
status: implemented
review: pending
surface: billing/proration.ts

STATUS

IMPLEMENTED

@gatekeeper · 2026-05-21

#1065 go

// churn heatmap · 90d

billing/proration.ts

touches

#1066 do

#1067 do

// implicit convention 6 sites

All handlers strip leading dots from email addresses before lookup.

e.g. auth/login.ts:24

#1068 go

// spec coverage gap PORTFOLIO

37% un-specced

0% target ≤ 10% 100%

#1069 go

// brownfield migration Q3 TARGET 60%

DONE 48% IN-FLIGHT 17% UNTOUCHED 35%

#1070 do

// test → spec LIFT

TEST

it('refunds to whole minute', () => {
  expect(refund(29)).toBe(25)
})

SPEC

criterion Refund is rounded down to whole minutes.

#1071 do

// SPEC-114 · stub

---
id: SPEC-114
status: implemented
owner: @author
---

INTENT TODO
ACCEPTANCE TODO
FAILURE MODES TODO

#1072 go

// confusion hotspot

!! HOTSPOT auth/session.ts 9× REVERTED

Spec backfill is queued — intent here is contested across at least three teams.

#1073 go

// integration archaeology @governor

assumed: billing POSTs every refund to /audit/ledger

#1074 do

// backfill queue UNCLAIMED

#07

billing/proration.ts

churn 47 RISK MED

CLAIM

#1075 do

// author hand-off SPEC-114

FROM

@bot-scribe

@author

#1076 go

// audit trail rebuild 2841/4120

69% commits linked

2019 backfill cursor today

#1077 do

// PR → spec HARVEST

PR #2841

Round refunds to whole minutes

Customers complained that 28-second slivers got tossed. This change rounds DOWN to whole minutes during proration.

SPEC-114

intent Refund slivers are not discarded — round down to whole minutes.

#1078 go

SPEC-114 · billing/proration.ts

Recovered intent reviewed across three sessions, characterisation tests green, no contradictions surfaced. Cleared for stable.

PROVISIONAL

PROMOTED → STABLE

@governor · 2026-05-21

#1079 go

RE ON-PACE

#1080 go

// brownfield risk · cell

auth/session.ts

cross-cut

Convention Promotion · 20

#1081 do

// recurrence PROMOTE

4 specs

pattern: retry-with-jitter

SPEC-012
SPEC-038
SPEC-051
SPEC-077

#1082 do

Promotion

Candidate

CAND-014 · @author

#1083 do

// candidate · retry-with-jitter

writes conventions/retry.md

requires @governor approval

#1084 do

conventions/retry.md NEW

---
id: CONV-014
owner: @governor
scope: all-handlers
---

# Retry With Jitter

Rule: all outbound calls retry
with exponential backoff + 20% jitter.

#1085 do

// usage map

retry-jitter

S-12

S-23

S-38

S-44

S-51

S-65

S-77

4/7

#1086 go

// enforcement scope

scope all auth handlers
scope lib/http/*
scope this spec only

#1087 go

CCS PRECISE

#1088 do

Discovered 2026-05-21

all UUIDs are lowercase before persistence

callsites

files

#1089 do

// promotion cadence · 6 months

dec CONV-014 may

#1090 go

// adoption · CONV-014 69%

adopted 18

pending 6

exempt 2

#1091 go

CONV-007 · http-retry-naive

Retry 3 times with fixed 200ms delay. Superseded by jittered exponential backoff for outbound calls.

DEPRECATED

sunset 2026-06-30

→ CONV-014

#1092 go

Conflict SCOPE-OVERLAP

CONV-014

retry-jitter

scope: all-handlers

CONV-019

no-retry-payment

scope: pay/*

#1093 do

// extraction

3 specs → 1 convention · @governor signed

#1094 do

id name · scope status

CONV-014

retry-with-jitter

scope: all-handlers · @governor

active
CONV-019

no-retry-payment

scope: pay/* · @gatekeeper

review

#1095 go

// authority · CONV-014

G @governor owner
G @gatekeeper approver
A @author requester

#1096 go

impact WIDE

#1097 go

SPEC-038 ↔ CONV-014 DRIFTING

10 samples · adherence

80 today

#1098 go

Promotion checklist CAND-014

✓ pattern present in ≥3 specs
✓ precision score ≥ 70
✓ scope selector is concrete
… governor signature attached
× no conflict with active conv.

#1099 do

// version pin · SPEC-038

CONV-014

v1.3.0

latest v1.4.1 update available

pinned by @author · upgrade requires @governor

#1100 do

2026-05-21 14:02 DISCOVERY

@author proposed CAND-021

idempotency-key on all POST handlers — observed in 5 specs

Integration Archaeology · 5

#1436 go

Assumed surface undocumented

billing-svc identity-svc

surface · GET /v1/users/{id}/groups

#1437 do

Contract gap

GET /v1/users/{id}/groups

Observed

array<{id, name, role}>

Specced

— absent —

#1438 do

Implicit assumption LOAD-BEARING

“User IDs are stable for the lifetime of an account and are never re-issued.”

#1439 go

Trail row

#3 2026-05-22 09:41

callers retry on 5xx with no backoff — assumed idempotent.

surface · POST /v1/charges

#1440 do

Archaeology closed

promoted to spec

SPEC-204

identity user-id stability contract, between billing-svc and identity-svc

filed 2026-05-22 · @architect

— Full detail →

—

// source

Alpha · Honest about it

The framework is real.
The community is forming now.

DoCoDeGo is in Alpha. The framework is documented, the practices are battle-tested at small scale, and the next release is being shaped in public.

If it produces anything, it should produce engineers and teams who think more clearly about what they are building and why.

Two doors in

Join the Discord

Discord is where specs are debated, the framework gets sharper, and decisions land in writing. The conversation is the artefact.

Reconciliation & Drift

Refund Proration

The framework is real.The community is forming now.

The framework is real.
The community is forming now.