Requirements
We identify official rules and standards by name. Applicability depends on edition, jurisdiction, product and competition context. Source documents take precedence over our summaries.
About / Independent technical publishing
Our Technical Lens
We explain fencing equipment as an interconnected mechanical, electrical and protective system.
Pavilionreelcacts.courses is written for equipment designers, armourers and fencers who want to understand why a component behaves as it does. We follow a touch backwards through the equipment and ask what evidence supports each explanation.
The domain is a publication address, not a promise of an accredited course or professional qualification. The guides are open technical reading, not a substitute for practical training, current rules or manufacturer instructions.
Interpretation
We explain mechanisms using engineering concepts. An explanation of bending or contact resistance is not itself an official inspection method or a product approval.
Limits
We do not invent laboratory results, product ratings or certification outcomes. Examples of test planning describe how to ask a question; they do not report tests performed by this publication.
How we handle sources
Official federation publications establish the competition context. Standards bodies identify formal methods and scopes. Measurement organisations help explain traceability, uncertainty and laboratory competence. We link the evidence trail so readers can check the original source rather than relying on a detached quotation.
Standards may require licensed access. A link to an organisation's catalogue is not a reproduction of the full standard, nor a guarantee that a particular edition remains current. Always verify the source before using it in a design file, purchasing specification or approval decision.
Independence and corrections
We are not affiliated with FIE, British Fencing, USA Fencing, standards bodies or equipment manufacturers. No product is endorsed or certified by appearing in an engineering discussion.
If you identify an error, send the page address, the disputed statement and the supporting source to [email protected]. A precise reference is more useful than a broad claim that a component “always” or “never” behaves a certain way. You can prepare the details using our bench-note tool.