Search and Content Index

This experiment pairs a search interface with generated discovery files. Search is configured to prioritize title, then content, then tags, and to show previews; the content-index emitter produces a JSON index, a sitemap, and an RSS feed capped at 20 items without full HTML. The receipt confirms that the search containers and emitted files exist, but it does not record an actual search query or prove result ranking.

Exact excerpt from /home/loca/dev/quartz-sandbox/sandbox/engine/quartz.config.yaml, lines 229–243:

  - source: "@quartz-community/search"
    enabled: true
    options:
      enablePreview: true
      fieldPriority:
        - title
        - content
        - tags
    order: 50
    layout:
      position: left
      priority: 20
      group: toolbar
      groupOptions:
        grow: true

Exact content-index emitter block from the same real configuration, lines 140–149:

  - source: "@quartz-community/content-index"
    enabled: true
    options:
      enableSiteMap: true
      enableRSS: true
      rssLimit: 20
      rssFullHtml: false
      rssSlug: index
      includeEmptyFiles: true
    order: 50

The source page offers these example queries. This contiguous content excerpt is copied from /home/loca/dev/quartz-sandbox/sandbox/vault/experiments/search-and-content-index.md, lines 60–65; it is a suggested exploration, not an executed query log.

Search terms with useful signal:
 
- `isolation` appears on the home page and the canvas page.
- `KaTeX` appears on the math page.
- `sandbox-reading-stats` appears on the local-plugin page.
- `data-callout` appears on the callout page.

What the rendered output proves

Live demonstration URL: https://quartz.loca.zone/experiments/search-and-content-index.html.

The prior capture in /home/loca/dev/quartz-sandbox/evidence/2026-09-15-quartz-migration-f1fd35c3/sandbox-experiments.json classifies Search and content index with proof_route: /experiments/search-and-content-index.html and the literal proof_markers values search_button: 1 and search_container: 1.

The matching rendered_proof.routes entry records the title Search, RSS and Sitemap — Quartz Sandbox, 43,171 DOM bytes, and the additional markers graph_container: 1, global_graph_container: 1, explorer_content: 1, nav_files_container: 1, reading_stats: 1, reading_words: "256", and reading_minutes: "2". The homepage capture at https://quartz.loca.zone/ separately records field_priority: 1; the search experiment route’s marker set does not include that marker. The exact priority order is established by the config excerpt, not by treating a marker count as a ranking test.

The receipt’s artifacts entries record:

Output and live URL	Prior recorded counts	Prior visibility observations
static/contentIndex.json	bytes: 70351, entries: 43	includes_unlisted_demo: false, includes_encrypted_demo: true
static/encryptedContentIndex.json	bytes: 26, entries: 0	The receipt says the configured encrypted demo is listed (unlistWhenEncrypted:false), so no unlisted encrypted metadata is emitted into the shadow index.
sitemap.xml	bytes: 5416, urls: 43	includes_unlisted_demo: false, includes_encrypted_demo: true, includes_alias_redirect: false
index.xml	bytes: 5499, items: 20	includes_unlisted_demo: false, includes_encrypted_demo: false, includes_alias_redirect: false

The related visibility_checks record unlisted_demo_direct_route_exists: true, unlisted_demo_absent_from_content_index: true, unlisted_demo_absent_from_sitemap: true, and unlisted_demo_absent_from_rss: true. These describe discovery exclusion, not access control. The public index includes the encrypted demo’s entry; that must not be described as proof that its plaintext body was indexed. The receipt separately records encrypted_demo_static_plaintext_marker_present: false and encrypted_demo_chrome_plaintext_marker_present: false, which are checks for the designated marker rather than a comprehensive confidentiality audit.

All these numbers are prior receipt observations, not new measurements made while authoring this page. Its temporary static origin was http://127.0.0.1:51963, using emitted .html filenames; the capture reports Chrome exit 0 for all 22 routes, all_routes_raw_wikilinks: 0, and all_routes_internal_broken_class: 0. Search button/container presence and emitted artifact counts do not establish successful search queries, preview behavior, ranking, keyboard selection, graph dragging, or explorer navigation. No interactive proof for those actions is provided.

Safe for the shared engine?

Recorded assessment: safe_for_shared_engine: true.

Receipt reason, verbatim:

These are existing opt-in components and emitters with explicit size controls and the normal published-page source of truth.

This is a recorded assessment, not a deployment instruction. 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. In particular, the true search/content-index verdict does not authorize the separately classified global layout changes.

Try it in the sandbox

After editing the isolated sandbox sources or configuration, use its wrapper:

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

The wrapper pins the isolated engine to commit 3dff48b5df6d84c9544a5ae19c8f2cbb01dc44e5 and uses the nonblocking sandbox/.build.lock; another wrapper build causes an immediate failure rather than a wait. It runs install-plugins before bootstrap-cli.mjs build, passes --directory /home/loca/dev/quartz-sandbox/sandbox/vault, and sends --output to a fresh timestamped /home/loca/dev/quartz-sandbox/sandbox/dist-<timestamp> release. It checks index.html before atomically swapping sandbox/current. The origin sees the new release on the next request without restarting. These steps are recorded in 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 runtime receipt’s earlier hot-swap exercise records without_restart: true, with server_pid_before: 2343441 and server_pid_after: 2343441; those are historical manual-process observations, not the identity of today’s service. No sandbox rebuild or service change was performed to author this documentation. The example queries above are available for future manual exploration, without a claim that they have already passed.

index