Golem Links

Principle

D-Zone remains static. Golem makes selected examples interactive.

Every documented example should be able to grow a link like:

Try in Golem

The link should load:

• the example description,
• the FCS files,
• expected outputs,
• validation notes,
• optional viewer scene or report output.

Desired Flow

1. Developer reads a D-Zone example.
2. Developer clicks "Try in Golem".
3. Golem opens with the example already loaded.
4. Developer asks for a change.
5. Golem edits FCS, runs FLI, reads errors or outputs, and iterates.
6. If the example is visual, Golem links or embeds the viewer output.

Static Link Shape

Exact URL design is not final. Candidate:

https://golem.histruct.com/?example=content/gists/gist-100-vertex

or:

https://golem.histruct.com/examples/gist-100-vertex

Documentation Requirement

An example is Golem-ready when it has:

• meta.md
• main.fcs
• expected text output or expected scene
• a clear validation command
• no private client data, credentials, or sensitive internal paths

Viewer Relationship

The viewer should remain a tool. D-Zone documents the example. Golem runs the loop. The viewer displays HiScene or other visual outputs when useful.