Examples

Examples are the core of D-Zone. They are where the site proves that engineering knowledge can become source files, parameters, outputs, validation notes, and eventually guided Golem experiments.

Start With These

Example	Status	Use it for
Golden Example: Vertex	Checked tiny proof	Understand the smallest FCS source-to-output loop.
Snow White Dining	Visual seed example	See multi-file component reuse, placement, material layers, and HiScene output.
Rebar Lintel Challenge	Draft challenge	Convert a narrow civil-engineering task into parameters, formulas, report, and picture.

Tested Mini-Projects

The largest example inventory is the gist collection:

Gist-Based Documentation tracks 53 created and tested mini-projects.
Arithmetic starts the language-basics track.
Vertex starts the geometry track.
Portal Frame shows component placement and reusable profile logic.
CSG Union / Intersect covers boolean solids.
DXF Export points toward production output workflows.

Larger Source Collections

Collection	What to expect
Knowledge Base Examples	Full documentation index plus larger example projects such as warehouses, chairs, springs, and material scenes.
Material Visualization	Layer material patterns for examples that need to communicate visually.
HiStruct Code Quest	Learning path, platform patterns, quickstarts, gotchas, and agent guidance.

Example Standard

A public-ready example should include:

Required part	Why
Purpose	The reader must know what the example proves.
Source files	Agents and humans need exact files, not prose-only descriptions.
What to change	Parametric examples should invite one safe modification.
Expected output	A value, report, scene, or image makes the example falsifiable.
Validation route	FLI, viewer, test script, or an honest note that validation is not wired yet.
Future Golem prompt	Golem should have a concrete first action when that workflow arrives.

Draft examples are allowed. Hidden uncertainty is not.