LAB CATEGORY
Start with concept identity, clear field definitions, and a vocabulary that can evolve without breaking the records that depend on it. These guides explain how to separate topics from tags and entities, structure assignments, and make integration decisions visible. Read them before choosing a classifier or building a large catalog.
1 ARTICLE IN THIS COLLECTION
Use the schema guide to follow a single document through a proposed integration. Identify the concept record, the assignment, and the document revision separately. Then ask what a consuming screen should show when the label changes, the evidence disappears, or the article receives an update. These cases reveal whether an identifier preserves meaning or merely preserves a convenient string.
Before adding fields, write the decision each field supports. Can a client distinguish an unsupported subject from an interrupted request? Can it recover the vocabulary definition used for an older assignment? Compare the foundations article with the prediction contract guide when a record includes statements and time horizons. Leave with a small field dictionary, three representative response examples, and an explicit rule for reviewing changed meanings.
Build a topics API contract that readers, editors, and developers can understand. Explore stable identifiers, evidence, uncertainty, document revisions, and vocabulary changes through practical examples for content classification.
Read the article : Topics API design: IDs, labels, and useful JSON contractsFollow the core topic guides for examples, field definitions, and related reading.