{"compiledCode":"\"use strict\";Object.defineProperty(exports, \"__esModule\", {value: true}); function _interopRequireDefault(obj) { return obj && obj.__esModule ? obj : { default: obj }; }var _react = require('react'); var _react2 = _interopRequireDefault(_react);\n function ReadingPage(){return _react2.default.createElement('main', { className: \"site-reading\",}, _react2.default.createElement('p', { className: \"eyebrow\",}, \"StumbleBees\"), _react2.default.createElement('div', { dangerouslySetInnerHTML: {__html:\"<h1>Gone</h1>\\n<p>Browse the live <a href=\\\"/directory\\\">directory</a>, try <a href=\\\"/stumble\\\">Stumble</a>, or <a href=\\\"/directory/submit\\\">suggest a business</a>. All submissions require editorial review. The reference material below describes the published standard; it is not evidence that an individual business has been checked. No public dataset export or automated check log is offered.</p>\\n<p>This reference defines how a confirmed closure would be recorded. No business tombstone or closure outcome is supplied.</p>\\n<h2>Current state</h2>\\n<h3>Tombstones published: 0</h3>\\n<p>This page is the complete tombstone procedure. No live tombstone row is represented here; a row exists only when it carries the required checks, dates, and human confirmation described below.</p>\\n<h2>Why we keep them</h2>\\n<p>Almost every listing site deletes. The listing simply stops appearing and the record of it having existed goes with it, which means nobody can tell whether the site is maintained or whether the business is still out there somewhere.</p>\\n<p>A tombstone answers a real question — did this close? — that is otherwise very hard to answer about a small business. It is also the honest accounting: if we told you something existed, and it no longer does, that is a thing we said and should be able to point at.</p>\\n<p>A maintained register must preserve removals as tombstones. Any entry-to-tombstone ratio is publishable only from actual dated rows; this page makes no ratio claim.</p>\\n<h2>What has to happen before a tombstone appears</h2>\\n<ol>\\n<li>A check returns unreachable.</li>\\n<li>At least fourteen days pass.</li>\\n<li>A second check returns unreachable.</li>\\n<li>A named person confirms it independently, looking for the things a script cannot see — a move, a rebrand, a sale, a pause.</li>\\n<li>Only then is the entry moved, with the date of its final check.</li>\\n</ol>\\n<p>The threshold is deliberately slow. Declaring a working business closed is the most damaging error this site can make, and it costs the operator in a way a missing entry never does.</p>\\n<h2>What a tombstone contains — and what it never will</h2>\\n<table>\\n<thead>\\n<tr>\\n<th>We publish</th>\\n<th>We do not publish</th>\\n</tr>\\n</thead>\\n<tbody>\\n<tr>\\n<td>The date it was last seen alive.</td>\\n<td>Any reason for the closure, unless the owner published one themselves.</td>\\n</tr>\\n<tr>\\n<td>The date of the first failed check.</td>\\n<td>Any speculation about difficulty, debt, dispute or conduct.</td>\\n</tr>\\n<tr>\\n<td>The date closure was confirmed.</td>\\n<td>Any characterisation of the business or the people who ran it.</td>\\n</tr>\\n<tr>\\n<td>What we observed — plainly, factually.</td>\\n<td>Anything that reads as a judgement, an obituary or a warning.</td>\\n</tr>\\n<tr>\\n<td>What the business was, in our own words.</td>\\n<td>Any personal detail about the owner, including a home address.</td>\\n</tr>\\n<tr>\\n<td>A successor, only if one is publicly stated.</td>\\n<td>A guessed successor, or a competitor presented as an alternative.</td>\\n</tr>\\n</tbody>\\n</table>\\n<h2>The four states we distinguish</h2>\\n<ul>\\n<li>Closed for good — the only case that produces a tombstone.</li>\\n<li>Moved or rebranded — the entry is re-reviewed and rewritten, not tombstoned.</li>\\n<li>Paused or seasonal — the entry is flagged, not removed. See <a href=\\\"/blog/is-it-open-problem\\\">the is-it-open problem</a>.</li>\\n<li>Sold — reviewed against <a href=\\\"/entry-bar\\\">the entry bar</a> again, since independence may have changed.</li>\\n</ul>\\n<h2>If we got it wrong</h2>\\n<p>Marking a trading business as closed is the most damaging error this site can make. <a href=\\\"/corrections\\\">The corrections procedure</a> sets out how a mistaken tombstone is recorded and corrected, with the error noted rather than hidden.</p>\\n<p>If you would rather the tombstone simply came off the site entirely, <a href=\\\"/delist\\\">the removal procedure</a> does that, no reason required.</p>\\n<h2>Questions about tombstones</h2>\\n<h3>Is a tombstone a criticism of the business?</h3>\\n<p>No, and the wording is chosen carefully to make sure it cannot be read as one. Businesses close for every reason imaginable, most of them nobody's fault, and none of them ours to speculate about.</p>\\n<h3>Why won't you say why a business closed?</h3>\\n<p>Because we almost never know, and a guess about someone's livelihood is not a thing to publish. If the owner has said publicly why, we can quote them with attribution. Otherwise the page says what we observed and stops.</p>\\n<h3>Someone I know has closed. Can I tell you?</h3>\\n<p>Use <a href=\\\"/contact\\\">Contact</a> to send a report. A closure is recorded only after the checks in <a href=\\\"/method\\\">the method</a> — two failed checks at least fourteen days apart, then a person confirming it — so a report would start that sequence, not replace it.</p>\\n<h3>Do tombstones stay forever?</h3>\\n<p>They stay unless the operator asks us to remove one, which we do free and without asking why. There is no archival argument that outweighs someone wanting their closed business off a stranger's website.</p>\\n<h3>What if a business reopens?</h3>\\n<p>It goes back through <a href=\\\"/entry-bar\\\">the entry bar</a> as a new review, because ownership, focus or independence may have changed. The tombstone is removed rather than left standing alongside the live entry.</p>\\n<h3>Do search engines index these pages?</h3>\\n<p>Yes. 'Did this close?' is a genuine question people ask and a tombstone is a useful answer to it. That is different from the stumble surface, which is deliberately kept out of search.</p>\\n<hr />\\n<p>Counts on this page come from the register. See <a href=\\\"/method\\\">the method</a> for the failure sequence and <a href=\\\"/corrections\\\">corrections</a> to report an error.</p>\\n\"},}), _react2.default.createElement('style', null, \".site-reading{max-width:1100px;margin:auto;padding:clamp(24px,5vw,64px) clamp(18px,4vw,40px);color:var(--c1biijfl-runtime-text,inherit);line-height:1.75;overflow-wrap:anywhere}.site-reading h1,.site-reading h2,.site-reading h3{font-family:var(--c1biijfl-font-heading,Georgia,serif);line-height:1.16}.site-reading h1{font-size:clamp(36px,6vw,64px);letter-spacing:-.035em}.site-reading h2{font-size:clamp(26px,4vw,34px);margin-top:2em}.site-reading p,.site-reading li{max-width:820px}.site-reading a{color:var(--c1biijfl-runtime-accent,inherit);text-underline-offset:4px}.site-reading a:focus-visible,.site-reading button:focus-visible{outline:3px solid currentColor;outline-offset:4px}.site-reading table{border-collapse:collapse;width:100%;display:block;overflow-x:auto}.site-reading th,.site-reading td{padding:14px;border:1px solid var(--c1biijfl-runtime-border,#b7b7ab);text-align:left;min-width:140px}.site-reading .live-discovery{padding:clamp(20px,4vw,40px);border:1px solid var(--c1biijfl-runtime-border,#b7b7ab);background:var(--c1biijfl-runtime-panel,transparent);border-radius:16px;margin-block:24px 40px}.site-reading .live-discovery h2{margin-top:0}.site-reading button{font:inherit;cursor:pointer;min-height:48px;padding:12px 22px;background:var(--c1biijfl-runtime-action-bg,#2d6545);color:var(--c1biijfl-runtime-action-fg,#fff);border:0;border-radius:8px}.site-reading blockquote{margin-left:0;border-left:3px solid currentColor;padding-left:22px}.site-reading .eyebrow{text-transform:uppercase;letter-spacing:.14em;font-size:12px;font-weight:700}\"));} exports.default = ReadingPage;"}