Method
Editorial log
Every published page on this site, who reviewed it, when, and what the review changed.
Scaled content is penalised when it is published without review. Rather than assert that review happens, the record is kept here and the build will not publish a page whose review block is missing or dated before the page was written.
Some collections are checked automatically and the table says so rather than hiding it. Market pages carry no third-party figure — every publishable fact on one is a named authority, a section number, an institution or a link — so each is checked by retrieving the source and searching it, and the URL, the status, the hash and the matched passage are recorded. A field that cannot be established that way is dropped; a page whose required fields cannot be is not published. Practical guides are published under Siddharth Sharma's byline. The review log records the checks performed during production separately from author attribution; it does not treat an automated check as a person reading a piece.
| Page | Type | Reviewed by | Reviewed | What the review changed |
|---|---|---|---|---|
| How specialty trade contractors identify and secure residential projects in Seattle | Geography | Geo Verification Engine | 2026-08-22 | Verified by machine under ARCHITECTURE.md §2.2 rather than read by a person: every publishable fact on this page was checked against a source retrieved from app.leg.wa.gov, www.seattle.gov before it was written, and every proposed field that failed its check was dropped rather than published. The record — the URL, the HTTP status and the sha256 of each document read, and the passage each check matched — is at engine/geo/verifications/home-services/. |
| How ambulatory health care providers acquire patients in the Phoenix metro area | Geography | Geo Verification Engine | 2026-08-22 | Verified by machine under ARCHITECTURE.md §2.2 rather than read by a person: every publishable fact on this page was checked against a source retrieved from www.azleg.gov, www.mcmsonline.com before it was written, and every proposed field that failed its check was dropped rather than published. The record — the URL, the HTTP status and the sha256 of each document read, and the passage each check matched — is at engine/geo/verifications/healthcare/. |
| How industrial manufacturers secure new business in the Houston metro area | Geography | Geo Verification Engine | 2026-08-22 | Verified by machine under ARCHITECTURE.md §2.2 rather than read by a person: every publishable fact on this page was checked against a source retrieved from comptroller.texas.gov, www.tceq.texas.gov, www.hccs.edu before it was written, and every proposed field that failed its check was dropped rather than published. The record — the URL, the HTTP status and the sha256 of each document read, and the passage each check matched — is at engine/geo/verifications/manufacturing/. |
| Acquiring real estate clients through local property data and association networks | Geography | Geo Verification Engine | 2026-08-22 | Verified by machine under ARCHITECTURE.md §2.2 rather than read by a person: every publishable fact on this page was checked against a source retrieved from www.scstatehouse.gov, charlestonrealtors.com, www.charlestoncounty.gov before it was written, and every proposed field that failed its check was dropped rather than published. The record — the URL, the HTTP status and the sha256 of each document read, and the passage each check matched — is at engine/geo/verifications/real-estate/. |
| How brokers acquire clients through local property and disclosure data in Phoenix | Geography | Geo Verification Engine | 2026-08-22 | Verified by machine under ARCHITECTURE.md §2.2 rather than read by a person: every publishable fact on this page was checked against a source retrieved from www.azleg.gov, armls.com, mcassessor.maricopa.gov and others before it was written, and every proposed field that failed its check was dropped rather than published. The record — the URL, the HTTP status and the sha256 of each document read, and the passage each check matched — is at engine/geo/verifications/real-estate/. |
| How Seattle real estate brokers acquire clients through local data and disclosure | Geography | Geo Verification Engine | 2026-08-22 | Verified by machine under ARCHITECTURE.md §2.2 rather than read by a person: every publishable fact on this page was checked against a source retrieved from app.leg.wa.gov, apps.leg.wa.gov, www.seattle.gov before it was written, and every proposed field that failed its check was dropped rather than published. The record — the URL, the HTTP status and the sha256 of each document read, and the passage each check matched — is at engine/geo/verifications/real-estate/. |
| What does an employee actually cost, over and above the wage? | Benchmark | Siddharth Sharma | 2026-08-21 | First publication, drafted from the engine reconciliation recon-employer-labour-cost-load-2026-08-21. Three calls made in drafting and worth naming. The audited values are reproduced exactly as the engine holds them, so two of them carry no percent sign, because the publisher printed those two as table cells under a percent column heading and in no sentence anywhere. The sample column for the three statutory rates says that there is no sample rather than that none was stated, because a rate set in law is not an estimate and reporting it as an undisclosed sample would be the wrong criticism. The small-establishment row states the whole private-industry sample and says plainly that the release does not break it down by band. The two open editorial decisions the reconciliation records are left open and printed on the page rather than resolved. Updated the same day: two of those open questions had been settled by the time the day ended, and a page that goes on calling a settled question open is a page nobody can trust about the ones still open. The statutory-share question was decided — a floor is computable for a named payroll and is not publishable as a share — and the multiplier trail was walked to its origin, which is now its own page. Both entries say what changed rather than being deleted. Nothing else moved: no row, no value, no definition, no verdict. |
| Where the loaded-labour multiplier actually comes from | Provenance | Siddharth Sharma | 2026-08-21 | First publication, from a trail walked on the day. Four calls made in drafting. The terminal source is classed as practitioner rather than academic: the author is a senior lecturer and the document is on his university's server, but it is a monthly advice column and not a study, and the class is about what a document can structurally support rather than about where it is hosted. The origin's date is recorded as undated rather than guessed at from its copyright line, which begins decades before the tax figures inside the article. The point figure appears only inside the audited columns, never in the prose, because the site's number gate forbids an unsourced numeral in copy and is right to — this is a figure the page is examining, not one it asserts. And the vendor page that attributes the range to the statistical agency appears once, in the trail, for what it attributes the figure to; its own worked-example point figure is described in the prose rather than repeated as a fourth circulating row, so no publisher is counted twice. |
| What does one employee cost you in federal payroll tax? | Calculator | Siddharth Sharma | 2026-08-21 | First publication, built on the three IRS statutory rates the research engine audited for reconciliation recon-employer-labour-cost-load-2026-08-21 and recorded in the migration 0049_two_documents_were_read_to_the_bottom. Three calls worth naming. The three rates enter the sourced data appendix as §18.7 — the first rows in that file to come through the evidence layer rather than from a reading of a published report — and each fact's value carries the base its rate stops at, because a constant that mirrors the rate while losing the base computes a wrong number out of two correct-looking halves. The instrument cites the Social Security topic page, which is the largest component and carries two of the three rates; the federal unemployment topic page is named on the page and in the assumptions rather than in the source line. And the last step states a share of the entered wage, which no publisher states and this page does not claim any publisher states — it exists only because a wage was supplied, which is exactly the open editorial decision the benchmark page records and this page does not settle. |
| What is a law firm's intake conversion rate? | Benchmark | Siddharth Sharma | 2026-08-08 | First publication. Rewrote the short answer to lead with the absence of a usable benchmark rather than with the range, since the range is the misleading part. Added the unanswered-enquiry row after deciding it belonged in the table as a constraint rather than in the prose as an aside. |
| Where the five-minute rule actually comes from | Provenance | Siddharth Sharma | 2026-08-08 | First publication. Moved the attribution finding ahead of the drift table, since the misattribution is the more common error. Removed an asserted sample size for the earlier study and recorded it as an open question instead, because the figure could not be confirmed against the study itself. |
| Is a fast automated reply better than a slower human one? | Answer | Siddharth Sharma | 2026-08-06 | Reworked the opening after the first draft read as a defence of automation in general, which is not what the question asks and not a position this site holds. Added the closing paragraph putting the automated reply back in proportion — it is the cheapest and most copyable part of a response system, and a page that oversells it undermines the argument for the rest. |
| How fast should a practice reply to a patient enquiry? | Answer | Siddharth Sharma | 2026-08-06 | Rewrote the automation answer twice. The first version implied the systems described here satisfy a practice's privacy obligations, which is not something this business supplies and not something a marketing page should imply — it now states the boundary as a design constraint and sends the agreements to whoever advises the practice. Added the full-practice question, which is the most common real objection and the one where the honest answer is counterintuitive. |
| How much should a small business spend on marketing? | Answer | Siddharth Sharma | 2026-08-06 | Deleted a paragraph recommending a specific split between media and fees. No sourced figure supports one and it would have read as advice dressed up as a benchmark. Added the gross-versus-net question, which is the single most common way this band gets misapplied and produces a budget that cannot fund the work. |
| Is it cheaper to do marketing in-house or hire an agency? | Answer | Siddharth Sharma | 2026-08-06 | Added the fourth paragraph making the case for in-house. Without it the page was an argument for hiring me wearing a question's clothes, which is exactly the register this page type exists to avoid — and the conditions are specific enough that a reader can check whether they meet them. |
| Should you measure average response time? | Answer | Siddharth Sharma | 2026-08-06 | This page states the standard the research layer holds itself to, so it was reviewed against that page rather than on its own. Removed a worked example with invented response times — illustrating a percentile with made-up numbers on a site that requires sourced ones is the wrong trade even when nothing is claimed. The low-volume question was added after realising the whole argument assumes a sample size most readers do not have. |
| What does a legal lead actually cost? | Answer | Siddharth Sharma | 2026-08-06 | Cut a paragraph estimating how much of the lead cost is recoverable — there is no sourced figure for it and the estimate was doing persuasive work rather than informative work. Added the practice-area caveat to the FAQ after re-reading the opener as though it were a quote for a specific firm. |
| Which leads should you call first? | Answer | Siddharth Sharma | 2026-08-06 | The first draft read as an argument against lead scoring altogether, which is not the position and is not what the sourced figures support. Rewrote it as an argument about where qualification sits in the sequence, and added the structural exceptions — they are the part a reader can act on immediately. |
| Why did so many programmatic sites lose rankings? | Answer | Siddharth Sharma | 2026-08-06 | This page describes the rule this site's own build is gated on, so the first draft was closer to a description of our architecture than an answer to the question. Removed the internal references and kept only the parts a reader can apply to their own site. Added the self-test question, which is the most useful thing on the page and was originally buried in the third paragraph. |
| Why do home services clicks cost more than average? | Answer | Siddharth Sharma | 2026-08-06 | Removed a claim that missed calls in this industry are never recovered — some are, and the honest version is that they are recovered rarely enough not to plan around. Added the marketplace question, which is how a majority of smaller contractors actually buy leads and was missing from a page about click cost. |
| Why do manufacturing enquiries take so long to close? | Answer | Siddharth Sharma | 2026-08-06 | Cut a paragraph asserting a typical industrial sales cycle length. No figure in the sourced appendix supports one, and an invented range would have been the most quotable and least defensible line on the page. Replaced it with the mechanism that actually sets the timing — capital cycles and shutdown windows — which is checkable against any plant's own calendar. |
| Where Austin real estate leads are actually lost | Geography | Siddharth Sharma | 2026-08-06 | Every claim on this page was checked against a primary or association source before it was written, and one was wrong on the first pass: the MLS is Unlock MLS, not Unlocked MLS, and getting a market's own institution's name wrong is the single fastest way to lose a local reader. Dropped the association's own website from the resources list because it could not be confirmed to resolve — the association is named in prose instead, and only links that were verified are printed. Also cut a paragraph on median price and days on market: those figures are real and published monthly, but not by us and not in the sourced appendix, and a geo page that opens with a borrowed statistic is the pattern this layer exists to avoid. |
| Where patient enquiries are lost between the search and the chair | Industry | Siddharth Sharma | 2026-08-06 | Named HIPAA once, in the verifiableBy handle for the regulatory evidence point, where a statute is a stronger handle than a paraphrase of it. The framing is unchanged and deliberate: the regulation is the practice's operating constraint, never a credential or a service of ours, and the page still says outright that this is not a compliance service. Rewrote the privacy section after a first draft that read as an implied compliance claim — it now states plainly that this is not a compliance service and that vendor agreements are a separate matter. Moved insurance eligibility from a bottleneck mentioned in passing to the structural difference, because it sits upstream of everything else on the page. Dropped a patient-acquisition cost figure that could not be traced past a secondary synthesis. |
| Where home services enquiries are lost before the van is booked | Industry | Siddharth Sharma | 2026-08-06 | Cut a paragraph selling faster response as an unqualified good and replaced it with the capacity argument, which is the thing an operator in this trade would otherwise have corrected me on. Added the unaccepted-estimates section after realising the page described only the missed-call half of the loss. Removed a specific sales-cycle range for replacement work that could not be traced to a primary source. |
| Where legal enquiries are lost before the consultation | Industry | Siddharth Sharma | 2026-08-06 | Cut a paragraph implying this is a compliance service and replaced it with the narrower true statement about approved language per jurisdiction. Moved the conflict check from a bottleneck mentioned in passing to the structural constraint it actually is, and rewrote the response-window section around it. Removed a claim that legal is the slowest industry to respond — the sourced figure covers cost, not speed. |
What the build refuses to publish.
Four checks run before any page in this system is generated, and each one stops the build rather than producing a warning nobody reads.
A page must name, in writing, what is on it that could not appear unchanged on a sibling page — and no two pages may give the same answer. Independently of that, every page is reduced to a fingerprint with its own subject and place names masked out; if two fingerprints match, or come close, both pages are named and the build stops. That is the check that catches a page whose only distinguishing feature was the city in the heading.
A page must also carry at least two datapoints that are specific to its own subject rather than to its category, and if the same figure is claimed as specific on two different pages, it was specific to neither. Pages ship in cohorts with a size cap so indexation can be observed between them, and every page carries the review block that produces the table above.
All four are properties of the schema, not of anyone remembering. Reviewed by Siddharth Sharma, except the 7 market page(s) above, which are checked against their sources and carry the record of it.
GATES
A gate enforced by a person reading pages stops being enforced somewhere around page 60.