Archived role taxonomy
This record organizes the application labels attached to “Applications of Machine Cut Concrete Products.” It is a map of wording found in the archive, not proof that a named concrete product has a particular property or is appropriate for a project.
How the archive groups the subject
The source places its labels in three broad contexts: construction, landscape and outdoor design, and interior design and decoration. That grouping describes the old article’s editorial arrangement. It does not establish suitability, strength, stability, appearance, service life, or any other result.
- Construction vocabulary: blocks, walls, foundations, flooring, and cladding appear as named topics.
- Outdoor vocabulary: pavers and retaining walls are listed without a site record or material evidence.
- Interior vocabulary: countertops and tiles are mentioned without a verified finish, sample, or comparison.
Product words versus product evidence
A product word can identify what the previous text discussed, while product evidence would identify the exact item being described. For this page, the archive preserves the words “blocks,” “pavers,” “retaining walls,” “countertops,” and “tiles,” but it does not pair them with model references, drawings, samples, or test documentation. Readers should treat these terms as an index to the historical article rather than a current catalog.
What a later evidence review would need
A supported product account would need an exact identity, a dated source, the property or role being considered, and evidence that directly addresses that statement. None of those elements can be supplied by sector labels alone. The current archive also does not establish structural use, erosion control, decorative effect, customization, durability, or equivalence to another material.
Keeping those gaps visible prevents broad legacy language from being mistaken for a specification or recommendation. It also preserves a clear distinction between what the old page named and what the available record can actually support.
Reading this archive entry
Use this page as a bounded taxonomy of historical application language. Any present-day product description, project decision, or performance statement requires separate, item-specific documentation and is outside this article.
