The editorial team

Accountability without invented credentials. This page states who is responsible for the content, how it is produced, and what expertise is not being claimed.

Published by the Land Clearing Authority editorial team · Last revised 2026-07-29 · Editorial policy · Corrections

Who is accountable

Everything published here is attributed to the Land Clearing Authority editorial team, which is the accountable publisher for the whole site. That attribution appears on every substantive page alongside the date of its last recorded revision.

No individual bylines are published, and no named contributors are listed, because no individual has been attached to this content. The list of named contributors in the source configuration is empty, and it will stay empty until a real, identifiable person has reviewed a page and agreed to be named on it.

What is being claimed

That the decision framework on this site is internally consistent, and that the same published rules drive the tools, the submission form, and the routing — which is verifiable, because the rules are rendered on the pages that use them.
That every external authority cited is registered with the specific claim it supports, and that citing one outside that scope fails the build rather than passing quietly.
That no price figure, no statistic, and no research result is published unless it has a stated source or a published method behind it.
That the 95 library pages across 9 topic clusters each state what changes the answer, rather than presenting one answer as universal.

What is not being claimed

This matters more than the list above, because the gap between what a site implies and what it can support is where readers get misled.

No professional licence or certification. Nobody here is acting as a licensed surveyor, forester, engineer, arborist, or contractor, and nothing published is a professional opinion in any of those fields.
No determination about your property. Not its boundaries, not its wetland status, not whether a permit applies, not whether a tree is protected, not where your utilities run. Those are determinations made by qualified parties with access to your parcel.
No verification of any contractor. No licensing check, no insurance check, no rating, no endorsement, no directory of approved businesses.
No field measurement of prices or production rates. The research instruments are published; the observations have not been collected. That status is stated on every dataset page rather than hidden.

How a page is produced

A page is proposed only when it answers a decision a landowner actually has to make. A topic that cannot be written as a decision does not become a page.
It is drafted against a fixed structure that forces the parts of an answer: who it is for, what changes the answer, what drives the cost, what people get wrong, and what to ask. A draft that cannot fill those fields fails validation at build time.
Any external claim is attached to a registered source with a declared scope. An unregistered citation throws rather than rendering.
The build runs the claim scan, the similarity check, the thin-content floor, and the link graph across the whole site. None of these can be skipped for one page.
Publication is recorded as a dated revision entry, which is what the sitemap and the feed read from.

Review cadence

Every published page is re-read against its sources at least annually, and immediately whenever a cited authority changes a program or a document moves.

Questions about accountability

Why are there no named authors?

Because no individual has been attached to this content, and naming one who had not reviewed it would be a fabrication. The contributor list in the source configuration is empty and visible. When a real, identifiable reviewer is attached to a page, they will be named on it.

Is the content written by a person or generated?

It is published by the editorial team named above, which is the accountable entity regardless of the tools used to produce any given draft. What is verifiable is the process: the structural validation, the claim scanning, the source-scope enforcement, and the build gates all run on every page and are described on this site.

How do I report something that looks wrong?

Through the corrections process. Corrections are made in place and recorded in the revision log with the date and what changed, so a corrected page keeps its record rather than quietly becoming a different page.

Who reviews the reviewers?

Most of the review here is performed by code that runs on every build — the claim scan, the source cross-check, the similarity detector, the link graph. That is deliberate: a gate that runs automatically cannot be waived under deadline, which is the usual failure mode of a human review policy.