EN 
DE 
RU 
PT 
JA 
ES 
IT This controlled production article validates the repaired SGF Blog layout contract with real WordPress publishing. The body is rendered from Template_Blog.md, using the site-owned sgf-content-container classes instead of the old legacy table flow.
The previous SGF Blog route could publish a live URL while still producing a naked div and table structure. This sample proves the route can now target the fixed SGF slot contract before any content is generated.
Contract Markers Checked In This Sample
| Check | Expected result |
|---|---|
| Fence family | Mdfence modular machine safety fencing |
| Validation target | SGF Blog route slot contract |
| Required wrapper | sgf-content-container |
| Forbidden output | No inline CSS, body h1, legacy fixed-width tables, or free DOM |
Template before prose
The article body starts from the SGF template and then fills controlled slots. That prevents the model from drifting back into raw paragraphs, old tables, or copied inline styling.
CSS owned by the site
The visible styling is inherited from the existing Avada fusion-styles file. The post body only carries sgf-* class names and clean semantic content.
Route gate A Live URL is not enough. The acceptance gate requires the SGF root marker, required class markers, no forbidden output, browser evidence, and manual review.
Where this contract applies
- Robot cell and conveyor guarding where layouts change during commissioning
- Industrial aisle separation where visibility and controlled access matter
Frequently Asked Questions
No. The Theme Lock matrix now points SGF Blog to Template_Blog.md and the slot schema.
No. This sample still needs WP readback, visual evidence, and manual acceptance before it can be marked production_pass.
