Back to corpus
research noteexperiment writeup candidatescore 26
System Glossary: Milk Men
**Document ID:** GLOSSARY-001 **Version:** 1.0.0-DRAFT **Created:** 2025-12-26 **Governing Document:** 0.1.1-PROJECT-CHARTER.md **Purpose:** Define all core terms to eliminate ambiguity in implementation
Full HTML reader
Read the full artifact
Extracted abstract or opening context
**Document ID:** GLOSSARY-001 **Version:** 1.0.0-DRAFT **Created:** 2025-12-26 **Governing Document:** 0.1.1-PROJECT-CHARTER.md **Purpose:** Define all core terms to eliminate ambiguity in implementation
1. **No term may be used in code, documentation, or discussion unless defined here** 2. **Terms are case-sensitive in code; case-insensitive in discussion** 3. **If a term appears ambiguous, this document is authoritative** 4. **New terms require glossary update before use**
| Attribute | Value | |-----------|-------| | **Definition** | A distinct business entity that uses the platform; the top-level tenant boundary | | **What it is** | A company, team, or business unit with its own members, data, and configuration | | **What it is NOT** | A user account; a region; a team within an organization | | **Layer** | Domain / Conceptual | | **Database Table** | `organizations` | | **Swift Type** | `Organization` | | **Cardinality** | One user belongs to exactly one organization |
| Attribute | Value | |-----------|-------| | **Definition** | An industry category that determines default terminology and feature configuration | | **What it is** | A preset configuration template (Coffee & Beverage, Food Service, Retail & Wholesale, Custom) | | **What it is NOT** | A separate product; a customizable workflow engine; a user-defined category | | **Layer** | Domain / Configuration | | **Database Column** | `organizations.vertical_id` | | **Swift Type** | `VerticalType` (enum) | | **Values** | `coffee_beverage`, `food_service`, `retail_wholesale`, `custom` |
| Attribute | Value | |-----------|-------| | **Definition** | A user who belongs to an organization with an assigned role | | **What it is** | The association between a user account and an organization | | **What it is NOT** | The user account itself; an agent record; an invite | | **Layer** | Domain / Access Control | | **Database Table** | `organization_members` | | **Swift Type** | `OrganizationMember` |
Promotion decision
What has to happen next
Attach run IDs, datasets, metrics, and reproduction commands.
Why this is not always a full paper yet
Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.