Sentence patterns
Explore the sentence patterns the parser has seen and which ones have rules.
Open a pattern to see where it occurs, whether a rule colours it, and what text supports it. This page is for exploring examples—not for measuring completion.
The post-simplification recursive-slice trie. Simplify’s emitted logical clauses are placed one per line and parsed again. Each projected tree is visited node by node. At every root, each child may stop at the frontier or expand recursively; every resulting head-first, left-to-right sequence is inserted into one normal trie. Counts therefore mean generated output-tree slices, not pre-merged DAG-node occurrences.
This output trie is a separate diagnostic replay; do not compare its counts to the coverage cards until the next matching cohort-stamped refresh.
3 predicate occurrences are deliberately left uncoloured. The projected clause contains more than one verb with the same base word, so the replay cannot safely tell which one a rule produced. These are not automatically grammar failures. ambiguous_same_lemma: 3
all occurrences handled all occurrences open mixed: green share handled, red share open declared normal form when no producer/open colour applies declared retained fragment when no producer/open colour applies source-only edge rewrite heat
Next production qualification
C:VERB is the most recurrent unproduced output shape: 4 open occurrences across 1 source documents · 0 current producer-attributed occurrences. This count is a search lead, not the scope of a rule.
No cross-document owner/edge cluster is available for this output shape. It remains inspection-only and must not be used as a rule request.
Inspect the exact parser envelope and missing logical fact, reject artifacts, then either build the smallest rule with red/negative proof or explicitly close this cluster as non-transformable.
Current-engine rule qualification
host:VERB:VBP|conj:VERB:VB|cc:and|aux:none · 21 missing right-hand predicates across 5 source documents.
Replay engine d2c60d518db5 · trie colour engine 5ad8cded9584 · different engine revision from this trie; this is a discovery baseline, not a colour delta.
The rule quality question is concrete: does this exact host/conjunct/coordinator interface warrant projecting the omitted predicate and its authored and relation? The emitted-predicate baseline is shown under each witness.
[product name] shows you exactly where YOUR customers are already talking, what channels actually work for YOUR product category, and what to do first — so you stop guessing and start getting traction.ai-research:L51 · emitted: stop
The agency owner AI buyer cluster: where 53,000+ marketing professionals discuss tools, share frustrations, and drive word-of-mouth for AI software. Primary surfaces are Online Geniuses Slack (largest marketing Slack), r/DigitalMarketing (900K+ Reddit members), and Seven Figure Agency (leading agency growth community).ai-research:L409 · emitted: be, cluster
) — This is data from their own products, meaning they understand and respond to the same conversion mechanics they use on their customers.ai-research:L554 · emitted: be, use
Root-first sentence trie
One root-first canonical S→O→C→A/& path per output sentence. This is the non-multiplied corpus view: each projected node appears once in its sentence path, main clause first, so related sentences share their opening construction. In this replay every delivered sentence begins at a VERB predicate, so that shared root is opened to show the first useful split below it.
All recursive sentence-tree slices
For a(b(c,d),e,f(g,h)), this includes a, ab, abef, abcdef, abefgh, abcdefgh, plus the same cuts rooted at b, f, and every other node. A parse node deliberately appears in more than one slice, so these are generated-slice counts, not raw corpus-node counts. Green/red is evidence for the current (rightmost) node in each displayed slice; it never colours an entire subtree. All 73 root patterns are present below; a deep branch loads only after you open it, so the page does not silently drop the graph or make the browser render the full 653,040-slice tree at once.