This experiment presents two navigation views of the sandbox’s notes: a graph for relationships and an explorer for the folder tree. The local graph is configured for two hops with tags, dragging, zooming, and radial layout enabled; the global graph uses unrestricted depth and removes the fixture tag. Explorer folders start collapsed, folder clicks are configured as links, and saved state is enabled. The recorded evidence establishes component presence, not successful navigation or dragging.

Exact contiguous excerpt from /home/loca/dev/quartz-sandbox/sandbox/engine/quartz.config.yaml, lines 182–228:

  - source: "@quartz-community/explorer"
    enabled: true
    options:
      title: Sandbox files
      folderDefaultState: collapsed
      folderClickBehavior: link
      useSavedState: true
    order: 50
    layout:
      position: left
      priority: 50
  - source: "@quartz-community/graph"
    enabled: true
    options:
      localGraph:
        drag: true
        zoom: true
        depth: 2
        scale: 1.15
        repelForce: 0.6
        centerForce: 0.3
        linkDistance: 36
        fontSize: 0.6
        opacityScale: 1
        showTags: true
        removeTags: []
        focusOnHover: true
        enableRadial: true
      globalGraph:
        drag: true
        zoom: true
        depth: -1
        scale: 0.9
        repelForce: 0.5
        centerForce: 0.2
        linkDistance: 30
        fontSize: 0.6
        opacityScale: 1
        showTags: true
        removeTags:
          - fixture
        focusOnHover: true
        enableRadial: true
    order: 50
    layout:
      position: right
      priority: 10

The local and global configurations deliberately differ in depth, scale, force strengths, link distance, and tag filtering. The graph occupies the right layout position at priority 10; explorer occupies the left at priority 50. The companion source is /home/loca/dev/quartz-sandbox/sandbox/vault/experiments/graph-and-explorer.md, whose lines 14–21 describe the two views and their content-index backing. The values above are copied from the active sandbox configuration rather than that page’s illustrative configuration block.

What the rendered output proves

Live demonstration URL: https://quartz.loca.zone/experiments/graph-and-explorer.html.

The prior capture in /home/loca/dev/quartz-sandbox/evidence/2026-09-15-quartz-migration-f1fd35c3/sandbox-experiments.json classifies Graph and Explorer with proof_route: /experiments/graph-and-explorer.html and these literal proof_markers:

  • graph_container: 1
  • global_graph_container: 1
  • explorer_content: 1

The corresponding rendered_proof.routes entry records 49,961 DOM bytes, plus nav_files_container: 1, search_button: 1, search_container: 1, note_properties: 1, reading_stats: 1, reading_words: "215", and reading_minutes: "1".

These are historical observations from the prior receipt. The capture ran against a temporary static origin at http://127.0.0.1:51963; the receipt records Chrome exit 0 for all 22 captured routes, all_routes_raw_wikilinks: 0, and all_routes_internal_broken_class: 0.

The supporting artifacts entry records static/contentIndex.json with bytes: 70351 and entries: 43, available at https://quartz.loca.zone/static/contentIndex.json. It records includes_unlisted_demo: false and includes_encrypted_demo: true. That is evidence of an emitted data artifact, not evidence that graph nodes were dragged or the explorer tree was successfully traversed.

The counted graph and explorer containers do not establish populated node counts, graph dragging, zooming, hover focus, radial layout behavior, explorer folder navigation, or persistence across reloads. No interactive proof for those actions is present in the provided receipts. The configured options above show what the sandbox requests, not what an interaction test has established.

Safe for the shared engine?

Recorded assessment: safe_for_shared_engine: true.

Receipt reason, verbatim:

They are opt-in layout additions over existing content-index data and introduce no route or Markdown changes.

This is a recorded classification of the experiment, not permission to alter the shared installation. A safe_for_shared_engine: true verdict does NOT authorize a shared-engine change; report any requirement for such a change as a BLOCKER, not an action. This opt-in component assessment does not override the separate false verdict for global layout groups and page-type overrides.

Try it in the sandbox

After changing the isolated sandbox configuration or vault, use the existing wrapper:

cd /home/loca/dev/quartz-sandbox/sandbox && ./build.sh

The wrapper pins the isolated engine to commit 3dff48b5df6d84c9544a5ae19c8f2cbb01dc44e5, then takes the nonblocking sandbox/.build.lock; a competing wrapper build fails rather than waiting. It runs install-plugins before bootstrap-cli.mjs build. The default vault is passed as --directory /home/loca/dev/quartz-sandbox/sandbox/vault, and --output selects a new timestamped /home/loca/dev/quartz-sandbox/sandbox/dist-<timestamp> release. It checks that the release contains index.html, then atomically swaps sandbox/current. The origin observes the new release on its next request without a restart. This procedure follows sandbox/build.sh, lines 6–8, 28–47, and 72–98.

Recorded runtime invocation from sandbox-runtime.json, reference only:

PATH=/usr/bin:/bin PORT=51947 SANDBOX_ROOT=/home/loca/dev/quartz-sandbox/sandbox/current NODE_ENV=production /usr/bin/node /home/loca/dev/quartz-sandbox/sandbox/serve.mjs

The production service already owns port 51947. Do NOT start a second process or restart the service. The historical runtime receipt records without_restart: true and the unchanged pair server_pid_before: 2343441, server_pid_after: 2343441 during its hot-swap exercise; that earlier manual process is not the current service. No sandbox rebuild or service change was performed to author this documentation. A future manual exploration can try dragging and zooming the graph and following explorer links, but this page does not claim those interactions were tested.

index