Why not chunk-and-embed
For a 200-page reglement where “Art. 14 applies subject to Art. 9 para. 2”, the second
column is the one that gives a defensible answer.
How it works
1
Build the tree
The document is parsed into a hierarchical outline — parts, chapters, articles, paragraphs —
with each node summarised by what it covers.
2
Assemble
Nodes are assembled into a navigable tree that can be rendered as an outline.
3
Search by reasoning
A query walks the tree: at each level the model decides which branch could contain the answer,
and descends. The result is a node path, not a similarity score.
4
Answer with a citation
The answer names the section it came from, so it can be checked.
Current scope
Suitable documents
- Collective labour agreements (GAV / CCT)
- Pension fund reglements
- Cantonal and federal ordinances
- Long employment contracts and their annexes
- Internal policy handbooks
Provider
Claude, through the platform’s central model configuration (document-intelligence.tree), which is Opus-class by default because the quality of
the structural reasoning is the whole feature.