Concordance

Which ERPNext DocType each coined design-document term refers to, and which design documents discuss each DocType.

This page links the system-design corpus’s vocabulary to the 448 documented entities: a coined term maps to its ERPNext DocType below, and a DocType links back to every design document that names it.

The corpus’s entity names are coined by design — vendor-neutral labels like “Legal Entity” or “Posting Batch” chosen so a design reads independently of any one ERPNext implementation. That convention is not applied uniformly: several documents name real ERPNext DocTypes directly, in the same bold-emphasis style as the coined terms, with nothing on the page to tell the two apart. This page exists because of that inconsistency.

The coined-term table below covers only multi-word terms declared with Markdown strong emphasis (**Term**) in two or more documents — the mechanically identifiable, recurring candidates. Plain-text mentions, Mermaid diagram labels, and terms coined in a single document are outside this rule; a single-document coinage stays defined by the document that uses it.

The reverse index matches multi-word DocType names only. Single-word names such as Item, Bin, and Batch are ordinary English words that match constantly in prose, so single-word matching would produce mostly false positives; this restriction is deliberate. As a result, 21 of the 73 design documents mention no multi-word DocType and do not appear in the reverse index at all.

Coined terms

DocTypes in design documents

This table is generated, not hand-authored: it matches every multi-word entity name from entities.json against the design-document text, and lists every document where a match occurs. It is a snapshot of the corpus at the time this page was written — a new design document, a renamed entity, or new prose in an existing document will not update it automatically.