What’s new
Everything newly published here, dated and newest first. This carries our own releases rather than a digest of the trade press — a site that republishes other people’s news is a secondary source competing with its own inputs.
Where the hardwood installed in Toronto actually comes from
The forest, the mill and the paperwork behind a Toronto floor, reconstructed from primary documents only — Ontario’s own forest inventory and silvicultural guides, the manufacturers’ own disclosures, and the federal legality instruments. The longest section in it is the one listing what we looked for and could not source, published in full so that nobody has to take the rest on trust. It also records the single most consequential supply fact in this market: white ash is the only one of the six species used here being cut faster than it grows.
The two grading systems behind every hardwood floor
A hardwood board is graded twice, by two different bodies, under two opposite logics: the NHLA grades lumber on how much clear material it will yield, and the NWFA/NOFMA standard grades finished flooring on appearance alone — stating outright that all grades are equally strong and serviceable in any application. Almost every quote in this market names neither. This paper publishes both rulebooks side by side, with the six questions that turn a grade into something a customer can hold a supplier to.
Five species dossiers — case studies of the material, not of a client
Red oak, hard maple, white ash, hickory and black walnut, each with its published hardness, its Ontario range and status, its standing inventory, its growth against its harvest, and the flooring grades it is actually sold in. Every figure traces to a government or standards-body document named in the paper behind it. They were written instead of five more client case studies on purpose: the five already published are real jobs with measured readings, and five invented ones would have passed every check in this repository, because the checks test consistency and not truth.
Two new plotted figures: Ontario standing volume, and the NHLA yield ladder
Ontario’s hardwood growing stock by species, and what each NHLA lumber grade requires a board to yield in clear cuttings. Both are drawn from figures that appear verbatim in the paper section each one cites — the guard that checks this refuses any plotted number that is not already published in its source, which is what stops a chart from quietly becoming its own evidence.
Every technical paper now carries its sources, and the PDF is generated from the page
Papers can now carry a register of the primary documents behind them — the issuing organisation, the exact title, the organisation’s own URL, and the date a human opened it. Those references are also emitted as machine-readable citations, which is the field an answer engine reads to decide whether a document is grounded or merely asserted. Separately, the LaTeX source each PDF is exported from is now generated from the same manifest the page renders from, so the download can no longer drift away from what the site says.
Every question about this company, answered in one paragraph each
Who we are, how long we have worked, whether we subcontract, where we go, what it costs, and how the work is judged — stated in the words those questions are actually asked, one self-contained paragraph each, on a single page. Every figure on it is read from the same source the rest of the site renders from, so there is nowhere on that page to type a number that could drift from the truth. It is also carried in the machine-readable editions, because the first thing anything reading this site has to settle is who it belongs to.
The logo is now an image on the internet, and every diagram is findable
The brand mark was embedded in the page as encoded text rather than published as a file, which meant it had no address — nothing could crawl it, index it, link to it or share it, and image search had no way to know the logo existed. It is now a file at a permanent URL, with a description attached, and the same mark at full resolution is what search engines read as the company’s logo. The sitemap also declares every technical diagram, because an image reached only by JavaScript is one a search engine is told about or does not find.
The logo fix, actually applied this time
The previous release corrected where the organisation’s logo URL came from, and the code that builds the schema was ignoring it — hardcoding the old path one line below the field that read the setting correctly. Every check in the repository passed. The production check, which fetches the logo the live page actually declares rather than reading the source, failed on its first run. That is what it is for.
The logo in our structured data now exists
The organisation’s logo and image had pointed at two URLs that returned 404 — one file sitting in a directory this host does not serve, the other never created at all. Those are the fields a search engine reads to attach a brand mark to a knowledge panel, and every structured-data validator passed the markup, because a validator checks that a URL is well formed and never checks that it resolves. Both are now derived from imported files, so a missing one stops the build. Every article also carries an image, which is what makes it eligible for a rich result at all.
Five guides for the questions people actually type
Cost, choosing a contractor, white oak, dustless refinishing, and the pattern floors — herringbone, chevron and parquet. Each is written the way the question is asked, answers it in the first paragraph, and cites the paper section behind every technical claim. The cost guide publishes the three service bands as a table rather than a starting-from number, and says plainly which variables move a phone range into a fixed written price.
Sixteen Toronto neighbourhoods, each with its own page
Rosedale, Forest Hill, Yorkville, Leaside, The Annex, High Park, Riverdale, Leslieville, The Beaches, Lawrence Park, Cabbagetown, Swansea, Davisville Village, midtown, King West and Liberty Village. Each carries the housing stock and the technical constraint specific to it — heritage wear layer in Cabbagetown, slab moisture and elevator windows in King West, lakeside humidity in the Beaches. They are neighbourhoods, not municipalities, and the entity graph says so: only real cities appear as City nodes in the organisation’s service area.
The estimate request is harder to abuse and impossible to lose
A hidden field catches automated submissions, a rate limit absorbs floods, and an acknowledgement email now goes to the customer within seconds of submitting. The order of those checks is the part that matters: the request is validated and written to a durable log before anything is allowed to reject it, so a rate limit can inconvenience a real customer but can never erase one. A public estimate endpoint at /api/estimate returns the same published bands to any tool or agent that asks.
The machine-readable corpus now answers local and commercial questions
Until now /llms-full.txt carried the technical material only — papers, guides, glossary. An agent asked who refinishes hardwood in Etobicoke found no service, no price and no area in the one file built for agents to read. Services and all sixteen service areas are now in the corpus and each has its own .md edition, so a single fetch answers what the work is, what it costs and where it is done. The knowledge API carries the same, with URLs. The corpus went from 70 KB to 115 KB, none of it new claims.
Every service area has its own page, not the same page sixteen times
Fifteen of the sixteen service-area pages rendered one generic paragraph with a place name substituted in. Each now carries the housing stock, the neighbourhoods and the technical constraint that are actually specific to it — slab moisture downtown and in Mississauga’s towers, remaining wear layer in East York, heated assemblies in Vaughan, lakeside humidity in Pickering and Ajax. The organisation’s coverage is now derived from the same list the pages are built from, so the entity graph cannot claim an area with no page or omit one that has a page. Homepage and service titles lead with what the work is rather than with the brand.
One page per service, each with its price band and the paper behind it
Installation, refinishing, dust-free sanding, restoration, stairs and inlays now have their own URLs. Each carries the published price band as a full band rather than a starting-from number, the framework pillars the work is scored against, the paper sections that establish the technique, and the decision guides that say when the service is the wrong one. No figure on any of them is new — every one was already published elsewhere on this site. The organisation’s structured data had been identifying these six services by URLs that did not exist; now they resolve.
Every document, as clean Markdown, at its own URL
Append .md to any paper, guide or glossary URL and you get the document itself — headings, tables and ordered protocols intact, with its canonical URL and citation line attached. The whole corpus is also served in one file at /llms-full.txt. Both are generated from the same source as the pages, so neither can drift from what the site says, and neither summarises anything: an agent quoting us should be quoting the sentence we published, not a paraphrase of it.
The NWFA installation guidelines, edition verified
The standards register carried this entry for a year without naming an edition, because the association’s landing page does not list one and this register does not assert what it has not read. The document itself has now been read at source: Wood Flooring Installation Guidelines, Revised © 2025, published by the National Wood Flooring Association. The entry names the edition, links the document rather than the homepage, and the register shows an Edition row wherever an edition has actually been confirmed — and no row where it has not.
A visual library — 136 images, indexed and linked
Every diagram and photograph on this site in one place: 28 technical cross-sections, each a link to the page that explains it, plus the twelve floors and twelve machines. The photographs rotate with a staggered Ken Burns push in four alternating variants, paused while off-screen. The diagrams do not move — a frame scaling under a cross-section makes it harder to read, not more alive.
28 technical diagrams across the framework, guides and glossary
Cross-sections of the three substrate assemblies, the four failure modes, the expansion gap, acclimation and the machine sequence. Flat vector, one palette, and no text baked into any image — every label stays in the HTML where a screen reader can read it and a crawler can index it. Each diagram is trimmed to its own content, so it carries its true aspect ratio rather than sitting in an empty 16:9 box.
What moves a hardwood quote — three commodity inputs, live
Forestry, energy and USD/CAD, pulled hourly from the Bank of Canada, with the mechanism behind each and why it is volatile. Published so a price change can be evaluated rather than suspected. A source that cannot be reached shows as missing rather than as the last cached number.
A standards register, with the date we last checked each entry
The external documents this trade answers to — ASTM concrete moisture and floor-preparation methods, NWFA guidelines — each mapped to the framework criteria that depend on it, linked to the issuing body, and stamped with a verification date the build warns about when it goes stale.
Two numbered figures, each with the table it was built from
Indoor relative humidity against the band hardwood needs, and Janka hardness across the five species used across the GTA. Every plotted value is checked against its source paper at build time, so a figure cannot drift from the document it claims to visualise. Free to reuse under CC BY 4.0.
The whole corpus is now available as JSON
Every paper with full section text, all 27 framework criteria with their sources, every guide and every glossary term — CORS-open, no key, CC BY 4.0. Generated from the same manifests the pages render from, so it cannot describe a page that does not exist.
A 32-term glossary, one addressable page per term
Acclimation, cupping, crowning, telegraphing, overwood, moisture differential and the rest — each with a canonical definition, DefinedTerm schema, and a link to the paper section it comes from.
The Ecowoods Well-Installed Framework v1.0
Six pillars and 27 binary criteria for judging a hardwood installation, published under CC BY with permanent criterion ids. Written to be used on any contractor in the GTA, including us. The self-assessment scores a quote in the browser and sends nothing anywhere.
Three decision guides and three reference installations
Solid versus engineered, installation method by substrate, and how to evaluate a quote — plus three scenarios specified end to end: condominium over slab, radiant heat main floor, and refinishing an existing floor.
The Craft — the four machines and the order they run in
Belt sander, edger, planetary and buffer: what each one does that the others cannot, and why a skipped step in the sequence is a liability that stays invisible until handover day.
Climate Mastery and The Intelligent Homeowner’s Decision Framework
Why hardwood succeeds or fails in Toronto — moisture, acclimation, substrate and method — and how to choose a floor that performs rather than one that photographs well. Published in full as HTML, not gated.
Outside this site
What we watch, and when we last checked
The bodies and documents this work answers to are tracked separately, with the date each entry was last verified against the issuing body’s own page. Every entry is inside its review interval.