HiStruct Code Quest

Code Quest is the builder track for D-Zone. Use it when you want to move from reading examples to authoring components that can be configured, evaluated, inspected, and debugged.

The target reader is not only a generic programmer. The strongest reader is a civil engineer, structural engineer, developer, or agent who needs domain knowledge to become executable.

What This Track Should Deliver

Outcome Evidence
Understand FCS syntax You can read and edit a small .fcs file without guessing every token.
Understand component packaging You can explain where source, manifests, input pages, reports, and assets belong in an FCC folder.
Understand the FCS/PVC split You can say whether a value belongs in reusable logic or instance state.
Validate work You can run FLI, inspect expected output, or identify what validation is still missing.
Avoid common mistakes You know the high-frequency syntax, geometry, and agent errors before they waste a day.

Start Here

Step Page Purpose
1 FCS Language Essentials Learn the expression model, bindings, lazy evaluation, functions, and script shape.
2 Geometry Primitives Move from values to vertices, curves, areas, volumes, layers, and coordinate systems.
3 Component Structure Learn how a script becomes a packaged HiStruct component.
4 Configurator Patterns Study gclass, gblock, distributions, conditional geometry, and parameter wiring.
5 All Gotchas Read the failure modes before writing larger examples.

If You Need A Specific Door

Need Go to
Run scripts locally FLI CLI Reference
Understand compute/runtime shape Booster Setup
Wire a component into the platform Architecture Overview and REST API Reference
Build parameter UI Parameter UI
Update components through APIs Component Edit API
Call external services REST Integration
Debug agent output Agent-Specific Mistakes
Look up terms Glossary

Rule For This Track

Every page should help a reader do one of three things:

  1. write valid FCS,
  2. package or configure a component,
  3. validate that the result behaves as claimed.

If a page only explains without source, output, or a next action, it should be improved.

Reference Bridges