Start Here In 5 Minutes

This page is the smallest useful D-Zone loop. It should leave you with one concrete idea:

FCS is reusable component logic. PVC is the editable state for one configured instance. A useful HiStruct example links source, inputs, output, and validation.

Your 5-Minute Outcome

By the end, you should be able to point to:

Question	Minimum answer
Where is the source?	`main.fcs` or a small FCC/component folder.
What can change?	Parameters, PVC values, or a small source edit.
What proves it worked?	An expected value, report, scene, or validation note.
What should I inspect next?	A visual example, a syntax page, or a challenge.

If a page cannot answer those questions, treat it as draft material.

1. Read One Concept

HiStruct components split responsibility:

FCS describes reusable logic: geometry, formulas, reports, validation, and output.
PVC stores current user-editable values for one configured instance.
FLI or Booster evaluates the model.
HiScene carries visual output to the viewer.

That split is the core of the site. D-Zone is useful only when it helps that loop become runnable and inspectable.

2. Open The Smallest Proof

Start here:

explanation: Golden Example: Vertex
source: main.fcs
expected output: expected-output.txt

The source is deliberately tiny:

vertex {p} xyz 1 2 3

The proof is also tiny: evaluating p.X should return 1.

3. Validate Or Inspect

If FLI is available locally, run:

fli.exe site/content/gists/gist-100-vertex/main.fcs "p.X"

Expected result:

If FLI is not available yet, still inspect the three linked files. The habit matters: source, requested expression, expected output. Later examples use the same pattern with more geometry, reports, or scenes.

4. Move From Proof To Picture

Open Snow White Dining. It is intentionally more memorable than the vertex example:

multiple FCS files,
reusable gclass definitions,
placed gblock instances,
parameters for dimensions,
material layers,
embedded HiScene viewer output.

This is the first place where FCS starts feeling like a component system rather than a calculator.

5. Choose Your Next Track

Track	Go next	Why
Civil engineer	Rebar Lintel Challenge	See how a real engineering task becomes inputs, formulas, report, and picture.
Component author	FCS Essentials	Learn syntax, evaluation, functions, and common script structure.
Platform builder	FCC Component Structure	Understand folders, manifests, input pages, outputs, and deployment shape.
Agent	llms.txt and agent-index.json	Use crawl roots and rules instead of guessing the site structure.
Example miner	Gist-Based Documentation	Browse tested mini-projects by domain and extraction wave.

What Good Looks Like

A strong D-Zone page is not just explanatory. It should be operational:

it names the purpose,
links source files,
says what to change,
states expected output,
gives a validation route,
marks missing tooling or future Golem behavior honestly.

Use that standard when reading the site and when adding new examples.