M6Glossary
Glossary
In one sentence: Short definitions of the terms used across Module 6, each linked to the page that explains it.
A to D
Section titled “A to D”- Acceptance criteria: A numbered list of checks that define when a product is done. See PRD: Trading Desk.
- ADR (architecture decision record): A short record of one decision and its rationale. See PRD: Marketing Studio.
- ATR (average true range): The typical daily price range of a stock, used to set invalidation levels. See Technical Design: Trading Desk.
- Backtest: Running rules on past data to see how they would have done. See Technical Design: Trading Desk.
- BuildManifest (build record): The record of one build: sources, record count, coverage and defects fixed, diffed against the previous run. See Technical Design: Provider Research.
- Canonical fact: The one authoritative location for a fact, such as a course price. See Case Overview: Content Operations.
- Challenger: The Provider Research role that attacks the built dataset: seven lenses, three verifiers per finding, and a critic that re-derives the code set without seeing the answer. See Technical Design: Provider Research.
- Check mode: A later rebuild that reports what changed since delivery without replacing the delivered list. See PRD: Provider Research.
- Citation: A link from an answer to the passage that supports it. See Case Overview: Tutor / Support RAG.
- Contact sheet: A document stating, for each contact channel, whether it is allowed for the stated use and why. See Case Overview: Provider Research.
- Conviction: How strongly the desk backs a call: Low, Medium or High. See Technical Design: Trading Desk.
- Cutoff: The moment a run’s data stops. Nothing after it may be used. See Case Overview: Trading Desk.
- Definition document: The plain-language explanation of who is in a dataset, who was left out and why. See PRD: Provider Research.
- Delivery Plan: The document listing tasks, estimates, owners and milestones. See Delivery Plan: Trading Desk.
- Deterministic: Done by code, so the same input always gives the same output. See Case Overview: Provider Research.
E to M
Section titled “E to M”- Escalation: Handing a question to a person because the assistant should not answer it. See Case Overview: Tutor / Support RAG.
- Evidence ID: The label that links a number to its stored source. See Technical Design: Trading Desk.
- Finished when: A task’s checkable completion condition. See Delivery Plan: Trading Desk.
- Fingerprint (hash): A short code computed from a file; any change to the file changes it. See PRD: Provider Research.
- Gate: A stop point where nothing continues until a person approves. See Cross-Case Comparison.
- GATE R / GATE D: Provider Research’s two human gates: approval of sources and code set before the large download, and approval of the deliverable before delivery. See Case Overview: Provider Research.
- Grounding: Keeping an answer inside its retrieved sources. See Case Overview: Tutor / Support RAG.
- Guard test: A test that deliberately tries to break a product rule and checks that the system refuses. See Technical Design: Trading Desk.
- Holdout: A slice of past data kept aside and used once, after the rules are frozen. See PRD: Trading Desk.
- Idempotency: The property that repeating an action has no extra effect. See Extension: From RAG to Support Agent.
- Invalidation level: The price at which a call is treated as wrong. See PRD: Trading Desk.
- Lookahead bias: Using information in a past decision that did not exist at the time. See Case Overview: Trading Desk.
N to R
Section titled “N to R”- n8n: A workflow-automation tool with ready-made nodes for channels, ticketing systems, vector stores and LLM calls, used in Lesson 1 as the reference build. See Reference Build: Support RAG on n8n.
- Non-goal: Something a PRD deliberately excludes. See PRD: Marketing Studio.
- NPPES NPI Registry: The US government’s public registry of healthcare providers. See Case Overview: Provider Research.
- Paper trading: Simulated trading with no real money. See PRD: Trading Desk.
- Point-in-time data: Data as it was known at a given moment, excluding later revisions. See Technical Design: Trading Desk.
- PRD (product requirements document): The document that says what is built, for whom, why, and what is out. See Introduction.
- Provenance: Where a value came from, when, and in what version. See Case Overview: Provider Research.
- Puffo: The team-collaboration agent platform the Lesson 2 to 4 systems run on: agents live in spaces and channels and act when a message arrives. See chat.puffo.ai and the puffo-agent daemon.
- Publishing check: A condition that blocks a call from being published. See Technical Design: Trading Desk.
- RAG (retrieval-augmented generation): Answering by first retrieving relevant passages, then generating from them. See Case Overview: Tutor / Support RAG.
- Reconcile: Checking that the parts of a dataset add back to the total. See PRD: Provider Research.
- Record vs. person: One row in a list is not one real-world person. See Case Overview: Provider Research.
- Restatement: A later correction of a reported figure. See Technical Design: Trading Desk.
- Run manager: The backend component that stores each run’s state and tells the Desk Lead what to post next. See Adding Complexity Layer by Layer.
S to Z
Section titled “S to Z”- Snapshot: A data load written once and never changed. See Technical Design: Trading Desk.
- Stopping check: A check that halts a build rather than warning. See PRD: Provider Research.
- SUE (standardised unexpected earnings): The earnings surprise measured against its own recent variability. See Technical Design: Trading Desk.
- Taxonomy code: The official code that says what kind of healthcare provider someone is. See Case Overview: Provider Research.
- Technical Design (TDD): The document that says how a product is built. See Technical Design: Trading Desk.
- Variant log: A record of every rule variant tested. See Technical Design: Trading Desk.
- Visual master: The one editable file every export is produced from. See PRD: Marketing Studio.
- Wake: A Puffo agent’s turn, triggered by a message in one of its channels. See Technical Design: Trading Desk.