Demos/Helix MCP Knowledge/Use case

Fictional · Reproducible · Knowledge only

A source-grounded answer.

Find the section. Name its scope. State what the index cannot support.

A small, authorised local corpus shows the baseline lexical search path without a live Helix connection or copied BMC documentation.

The answer

Evidence with a visible boundary.

The fictional Aster project asks when its recovery window begins and what remains enabled. Searching the selected project corpus and expanding the matching section supports this answer:

In the fictional Aster project, the recovery window begins at 02:15 UTC and lasts twenty minutes. The quartz-lock remains enabled during that window.

Source: Aster Operations Acceptance Note → “Recovery window” · aster-operations.md · project scope aster-tester · project-declared cmdb 26.1.

The version is a tag in this fictional project's manifest. It does not mean BMC published the instruction or that any live Helix environment runs that version. This is an answer composed from observed tool evidence, not a measured autonomous-agent response.

Reproduce locally

One document. Two questions.

  1. Use the public Knowledge v1.31.5 release and download the fictional Aster fixture. The archive contains one Markdown note, two project manifests and an MCP probe.
  2. Extract the archive and work from the directory containing first-query-fixture/. Point CASE_CLI and CASE_PYTHON at the installed release environment. Initialise a disposable workspace, copy the fixture into its project locations, then synchronise and run the MCP probe.
    Show local setup commands
    CASE_CLI=/absolute/path/to/release/venv/bin/helix-mcp-knowledge
CASE_PYTHON=/absolute/path/to/release/venv/bin/python
CASE_ROOT="$(mktemp -d /tmp/helix-knowledge-case.XXXXXX)"
"$CASE_CLI" init --workspace "$CASE_ROOT"
"$CASE_CLI" --config "$CASE_ROOT/config/config.yaml" init-db
mkdir -p "$CASE_ROOT/data/sources/projects/aster-tester/docs"
cp first-query-fixture/aster-tester*.yaml "$CASE_ROOT/config/projects/"
cp first-query-fixture/aster-operations.md "$CASE_ROOT/data/sources/projects/aster-tester/docs/"
"$CASE_CLI" --config "$CASE_ROOT/config/config.yaml" sync-project aster-tester
"$CASE_PYTHON" first-query-fixture/first_query_probe.py --config "$CASE_ROOT/config/config.yaml"
    The project manifest declares cmdb 26.1; the default release configuration uses FTS5 lexical search with semantic search and reranking disabled.
  3. Call search_docs for quartz-lock recovery window with project_id=aster-tester, source_scope=project, product=cmdb and version=26.1. Pass the returned chunk ID to get_section, then cite the returned title, heading, filename, scope and declared version.
  4. Search zircon override in the same scope. With no indexed match, answer that this selected corpus cannot support a rule; do not infer that the rule cannot exist elsewhere.

In the isolated v1.31.5 check on 15 September 2026, the positive query returned one lexical match after indexing and the unsupported query returned none. The empty-index and indexed checks used separate disposable workspaces. This establishes traceable retrieval for this fixture, not an official-document accuracy benchmark or a Helix operation.

Related validation

When evidence informs an approved action.

Knowledge and Gateway have distinct responsibilities when a live state change is required.

Read the controlled DEV case