Re-check Result v6 — SyntropyData
SyntropyData {{ domain }}  ·  {{ dateLine }}  ·  {{ resultRef }}

Demonstration document — the fictional Alderfield Home store. No live store was inspected.

Re-check Result · included in your Fix Sprint {{ recheckNoLine }} ● Read-only — this document changes nothing on your store

Stage 3 of 4 — the proof · stage 1, the Audit, diagnosed · stage 2, your Review Pack, settled the scope and the changes were made — this document reports what a fresh read of your live store found afterwards. It closes the Fix Sprint; nothing further runs unless you choose Catalogue Health.

The result · what happened to this Fix Sprint's implementation scope

{{ headline }}

{{ headSub }}

{{ scopeMeaning }}

Reconciliation mismatch — this result is not closed

{{ mmLine }}

Read this result accordingly

{{ pendingBanner }}

{{ scopeN }} catalogue changes re-checked against your live store
{{ rg.n }} {{ rg.label }} {{ rg.meaning }} {{ rg.states }}

Every change re-checked sits in exactly one of those three.

{{ scopeCaption }}
{{ sg.t }}

{{ denomLine }}

Where the work stands
{{ closurePct }}{{ closurePctCap }}
{{ closureSub }}
Different from the intended value  ·  {{ changedN }} Store-wide records  ·  {{ storeSummary }} Source  ·  {{ auditRef }}{{ packRef }} Who made the changes  ·  {{ pathSummary }}

What your catalogue gained

{{ gainHead }}

{{ gainIntro }}

{{ gf.n }} {{ gf.label }} {{ gf.sub }}

{{ gainLine }}

What this Re-check found {{ actSubhead }}

Results that were not fully verified

{{ actCountLine }}

Organised by what the fresh read found, not by who does something next.

ResultWhat we observedWhat this means
Result{{ a.result }}{{ a.scope }} {{ a.field }} What we observed{{ a.observed }} What this means{{ a.means }} evidence ↓

Accounted apart, and claiming nothing either way: {{ accountedLine }} — these sit in the results above.

A later cycle reads the catalogue again from whatever state it is in then.

{{ copyMsg }}

{{ noActionsLine }}

You decided it · we applied it · we read it back

{{ decidedNote }}

{{ dr.photoAlt }} {{ dr.title }} {{ dr.sku }} {{ dr.field }} You told us “{{ dr.val }}” We applied that decision. → We read the live catalogue again. → {{ dr.outcomeLabel }}

Your store could not establish it · we researched it · it is live now

{{ researchNote }}

{{ rr.photoAlt }} {{ rr.title }} {{ rr.sku }} {{ rr.field }} Established from {{ rr.source }} — {{ rr.sourceClass }} — and matched to this exact product. → The correction was implemented. → Verified live. {{ rr.val }}
How the exact-product match was proved{{ rr.matchLine }}

How we checked every one of these

Four separate things, kept separate. Every result below can be opened to show its own four.

What we found when we audited your store How the answer was settled What changed What we found when we checked again

Every catalogue change we re-checked · grouped by what it means for you — every individual change stays reachable

One row is one intended catalogue change. Work that came out right is summarised so it never buries you; exceptions get the space. A compact row opens into the same card everywhere — identity, what the Audit found, how the answer was settled, what changed and the exact operations that carried it out, what this Re-check found when it read your store again, the evidence, and lineage back to your Audit and Review Pack.

{{ t.n }} {{ t.label }}

Find any change

searches every catalogue change in this Re-check — {{ finderScope }}
{{ finderSummary }}

No result matches this combination.

Nothing is hidden — every result is in this index. Loosen one filter or .

{{ row.title }} {{ row.title }}{{ row.sub }} {{ row.field }} Intended{{ row.intended }} Live{{ row.observed }} Live{{ row.liveNote }} {{ row.ocLabel }} {{ row.caret }}
{{ fPageLabel }} always the same order: outcome severity, then catalogue fact, then SKU
{{ grp.kicker }} {{ grp.countLine }}

{{ grp.label }}

{{ grp.intro }}

{{ sub.label }}

{{ sub.note }} {{ sub.n }}

{{ sub.repsLabel }}

{{ row.photoAlt }} {{ row.title }} {{ row.title }}{{ row.sub }} Intended{{ row.intended }} Live{{ row.observed }} Live{{ row.liveNote }} {{ row.ocLabel }} {{ row.caret }}

{{ sub.foot }}

{{ o.chip }} {{ o.title }} {{ o.line }} {{ o.n }}

None of these was an approved change in this Fix Sprint's implementation scope, so none of them enters the reconciliation below — and none counts as unresolved implementation, a failed check or a fake verification.

Catalogue opportunity remaining after this cycle

{{ remainingIntro }}

Beyond this Fix Sprint

What your catalogue still holds open

{{ beyondNote }}

{{ br.n }} {{ br.label }} {{ br.detail }}
Publishing limitations we hold

{{ bh.n }} {{ bh.label }}. {{ bh.detail }}

{{ completableLine }} See them in your Review Pack ↗

What we re-checked · the same records, the same surfaces, no new audit

{{ t.k }}
{{ t.n }}
{{ t.sub }}
This is not a new Audit. We re-checked exactly what this Fix Sprint set out to change — the same products, the same catalogue facts, in the same places we looked before. {{ incidentalLine }} It is recorded outside this Re-check and does not move any count above.

Afterwards

{{ healthHead }}

{{ healthIntro }}

What this does not do

{{ healthCaveat }}

{{ healthBody }}

Recommended Six-monthly
Includes 2 complete cycles over 12 months
First audit January 2027, if you subscribe

What each cycle includes, and what it does not

Each cycle repeats what you have just been through: a full-catalogue audit compared with your last verified state, the fix sprint it recommends, your review pack, implementation by whichever route you choose, and the re-check that reports what actually landed.

Each cycle includes the exact Audit plus the Fix Sprint work of the subscribed allowance — the allowance and its unit are stated in your subscription terms.

Allowance, renewal and scope — the exact terms

Each cycle includes the exact Audit plus the Fix Sprint work of the subscribed allowance, stated in your subscription terms. If a cycle’s audit finds more work than the allowance covers, the excess is priced exactly as a Fix Sprint is — you authorise it separately or defer it, and the included scope stays covered either way. The subscription never quietly widens to absorb it.

If your catalogue materially outgrows the subscribed scope we ask you to approve a revised plan before the next audit. There is no automatic surcharge, and we never quietly reduce what an audit covers.

Nothing runs in the background between cycles. This is the same service, on a schedule.