Who writes and checks this

Attribution

One person maintains the rule files, the engines and the writing, and that person is not yet named here. Rather than publish a byline nobody can check, this page publishes the process instead, in enough detail that any figure on the site can be traced back to the document it came from and disproved if it is wrong. Corrections reach the same person, at info@bracketsight.com.

What verification means here

A rate, threshold, bracket, deadline or statutory term is never written into the code that uses it. It lives in a versioned rule file with the date it takes effect, the date it stops, and at least one citation carrying a URL and a lastVerified date. Verification means one specific thing: somebody fetched that URL, read the value off the document that came back, and recorded the date. Not that the value looks right, and not that a secondary source agrees.

The distinction between a primary and a secondary source is enforced rather than preferred. The statute, the regulation, the Federal Register notice, the IRS revenue procedure, the HHS guideline, the county assessor’s own page — those close a question. A legal-information site, a policy explainer or a news write-up may cross-check a value and may never close it; rows resting on one are marked [SECONDARY] and stay open. Three states’ contract statutes are in that state today, because their legislature websites refuse automated requests.

The rule exists because of something that happened during the pass. While checking the ACA applicable-percentage table, a summarising fetch layer reported the wrong revenue procedure number and returned a percentage table that did not exist in any document. The engine’s own table was already correct; accepting the summary would have replaced a right answer with an invented one. Every figure since has been read from extracted statute or PDF text rather than from anything that summarises it.

What the pass found

Each row below is one numeric constant or one encoded legal rule. “Corrected” means the source said something different from the code and the code was wrong. “Unresolved” means the source could not be reached or did not answer the question, and the value was left alone and recorded rather than guessed. A property section with 13 of 38 rows confirmed is not a section to act on without checking your own county, and the section says so on every page.

The unresolved rows are published in full rather than summarised. Each one names the value, the document that would settle it, and what is stopping that document being read — a login, an untranscribed statutory notice, a commercial licence, an agency that has not published the figure yet, or a genuine ambiguity in the rule. Every gap that has a location in the code also has a marker at that location, so the register and the code cannot drift apart without one of them being obviously wrong.

Who has reviewed it: nobody, yet

Each section’s editorial policy names the professional review it must pass before it can be described as finished. None of those reviews has happened. This is the table that says so in one place, and it stays on the site until the statuses change — dropping it to look more finished would be the single most dishonest thing this site could do.

Until a gate is met, the affected pages carry the warning and the figures are illustrative. If you hold one of those credentials and want to review a section, the address at the bottom of this page reaches the person who would act on it.

What the code guarantees, independently of who wrote it

No language model computes, adjusts, estimates or sanity-checks any number shown to a reader. That is not a policy, it is a property of the build: the five engines have zero dependencies and no network access, so there is nothing for a model call to be made through. Money is held in integer cents and rates in basis points, because floating-point drift across three hundred and sixty monthly iterations produces a wrong total at the end of a thirty-year simulation.

The engines carry 399 tests between them and the application another 69. Where an agency has published its own worked examples, those examples are encoded as tests, so the engine has to reproduce the government’s arithmetic before it can ship. Two tools refuse to answer rather than answer badly: contract generation is blocked for any state whose statutory notice has not been transcribed word for word, and a New Jersey assessment verdict is withheld when the ratio that governs the county is unavailable.

How a correction actually happens

Write to info@bracketsight.com with the figure and, ideally, the document that contradicts it. The report is checked against the primary source, not against the reporter’s confidence. If it holds, the rule file is edited, the lastVerified date moves, every page that depends on the value recomputes on the next build, and the change is written into that section’s changelog with the date and the source. If it does not hold, you get an answer saying which document was read and what it said.

Where each section's own record lives

• Student loans — its own methodology, dated sources, editorial policy and changelog, reachable from the footer of every page in the section.
• Paycheck — its own methodology, dated sources, editorial policy and changelog, reachable from the footer of every page in the section.
• Health cover — its own methodology, dated sources, editorial policy and changelog, reachable from the footer of every page in the section.
• Property tax — its own methodology, dated sources, editorial policy and changelog, reachable from the footer of every page in the section.
• Trades — its own methodology, dated sources, editorial policy and changelog, reachable from the footer of every page in the section.