Navigate the Shape

Challenge

Your navigation tools exist - now stretch them on three questions Dani’s keyword portal could not answer. Use the tools first; each slide also shows the Cypher underneath, to run in the sandbox and see what the tool traverses.

Walk a table of contents

An agent’s first question about any document estate is "what’s here?". The tree answers it directly:

shell
Table of contents for the Falcon manual
python skill/scripts/outline.py technical-library/manuals/man-fal-3.pdf

You should see the manual’s three chapters - Engine, Electrical, Brakes - sections in reading order, and rows where its sections link out. Underneath, the tool runs one variable-length walk - MATCH path = (root)-[:HAS*0..25]→(n) - and the renderer turns path lengths into indentation.

Keyword search cannot produce this view at all: it has no concept of "contains".

Find every document about a part

Dani’s real question: the recall mentioned coil IC-2042-A - what else covers it?

cypher
All documents that reference a part
MATCH (d:Document)-[:HAS*]->(s:Section)
      -[:REFERENCES_PART]->(p:Part {partNumber: 'IC-2042-A'})
RETURN d.docType AS type, d.title AS document,
       collect(s.displayName) AS sections

Three documents - of three different types - reference this part: the service manual, a bulletin, and a safety recall. That cross-document view is exactly what 40 keyword hits buried.

Try experimenting:

  • Change the part number to BP-7720 to map the brake-pad documents

  • Try the same question through search: python skill/scripts/search.py 'IC-2042-A'

From the misfire bulletin, what related guidance exists - and why is it related?

cypher
What does TSB-21-114 link to?
MATCH (b:Bulletin {id: 'TSB-21-114'})-[:HAS_SECTION*]->(s:Section)
      -[l:LINKS_TO]-(other:Section)<-[:HAS_SECTION*]-(d:Document)
RETURN DISTINCT d.title AS linkedDocument,
       other.title AS section,
       l.sharedKeys AS via
ORDER BY linkedDocument

Every row is explainable: the bulletin links to the Falcon manual’s coil sections via IC-2042-A, and to the recall via the coil part numbers. An agent following these links retrieves a connected set - the right meaning in the right shape.

Now answer the questions below from your query results.

Documents About the Coil

Which document types reference part IC-2042-A?

  • ❏ Only the Falcon service manual

  • ❏ A manual and a bulletin

  • ✓ A manual, a bulletin, and a recall notice

  • ❏ Only bulletins

Hint

Run the "All documents that reference a part" query with IC-2042-A and look at the type column.

Solution

The correct answer is a manual, a bulletin, and a recall notice.

The Falcon Service Manual, bulletin TSB-21-114, and recall RC-2021-04 all reference IC-2042-A. The shared part number connects three document types that never cite each other.

Brake Guidance

Adapt the part-centred query to part BP-7720 (the front brake pad kit). Which bulletin references it?

  • ❏ TSB-21-114

  • ✓ TSB-22-031

  • ❏ TSB-20-087

  • ❏ TSB-23-052

Hint

Change the partNumber value in the query to BP-7720 and look for the row with type Bulletin.

Solution

The correct answer is TSB-22-031 - "Front Brake Judder After Pad Replacement".

cypher
MATCH (d:Document)-[:HAS*]->(s:Section)
      -[:REFERENCES_PART]->(p:Part {partNumber: 'BP-7720'})
RETURN d.docType AS type, d.title AS document, collect(s.displayName) AS sections

The part also appears in the Falcon and Heron service manuals - three documents in total.

Summary

You navigated the document graph:

  • Tree walks - [:HAS_SECTION*] produces a table of contents keyword search cannot

  • Part-centred views - one query collects every document type covering a part

  • Explainable links - LINKS_TO traversals return connected, justified context

In the next module, you will run community detection over these links to surface the themes nobody named.

Chatbot

How can I help you today?

Data Model

Your data model will appear here.