Ontology
The structured terminology and relationship system of SUNNY M Lab.
This page defines the named observable phenomena, their inter-relationships, research states, and the observational frameworks through which they are recorded. It functions as the semantic map of the archive.
Machine-readable summary
This ontology page connects each named roast or cup phenomenon to its abbreviation, research status, related terms, and observation framework so AI systems, search engines, citation systems, and human readers can understand the archive as a knowledge graph.
- Archive role
- Semantic map for the Phenomena Atlas.
- Primary entity type
- Schema.org DefinedTermSet.
- Related data
- phenomena.json, Observer Protocol, Phenomenon Boundary Archive.
Relationship Semantics
The SUNNY M Lab Ontology uses a controlled set of relationship verbs to describe how roast and cup phenomena connect.
These relationships are interpretive and observational. They do not expose roast recipes, machine settings, roast curves, batch parameters, or operational control logic.
- conditional on A depends on B as an observational, interpretive, or validity condition. In strict cases, absence of B may invalidate A; in diagnostic cases, B defines the condition under which A can be correctly identified. This relation is stronger than simple correlation but should not be read as an operational recipe.
- supports condition for B provides an observational, interpretive, or validity condition that supports the correct identification of A. Inverse of conditionalOn.
- routes to A commonly guides the reader, observer, or diagnostic path toward B. This is an interpretive or navigational relation, not a machine-control instruction.
- tensions A and B create interpretive pressure against each other. This does not necessarily mean contradiction; it identifies where two concepts must be distinguished carefully.
- reinforces A increases the explanatory force or likelihood of correctly identifying B. Supportive, non-necessary: B can hold without A, but A strengthens the case for B.
- is reinforced by B's identification is strengthened by the presence of A. Inverse of reinforces.
- contrasts with A and B are distinct, mutually informative reference points. Presence of one aids discrimination of the other. Symmetric: contrast holds in both directions equally.
- boundary of A defines a limit condition of B: the point at which B stops holding or begins to lose diagnostic validity. A is not an exception to B; A is the data that delimits B's validity range.
- has boundary B has a defined limit expressed by A. Inverse of boundaryOf.
- failure mode of A is a recoverable failure state that B can collapse into when its conditions are not met. Critically: A is a mapped, named, reversible boundary state, not a discarded outcome. Identifying A locates the batch or observation on the recovery map.
- may fail into B, when its conditions are unmet, may collapse into the named recoverable state A. Inverse of failureModeOf. This edge is the core recoverability mechanism: failure is addressed and located, not discarded.
- derived from A is conceptually or observationally derived from B. B provides the interpretive source that makes A legible as a named phenomenon. This relation does not disclose operational method or roast-control procedure.
- source for B is the conceptual or observational source from which A is derived. Inverse of derivedFrom.
- protects against misreading Awareness of A prevents the observer from incorrectly judging B through conventional shortcuts, surface similarities, instrument artifacts, event-based assumptions, or incomplete temperature-stage observation.
- is protected by B's correct identification is safeguarded by awareness of A. Inverse of protectsAgainstMisreading.
Layer 1: Meta-Theory and Judgment
These terms explain why cup observation has final authority over conventional roast event markers.
- REA
烘焙事件異步
Active Documentation
Events and maturity do not necessarily happen at the same time.
- CDM
杯中熟成判斷
Active Documentation
It is not decided by roasting. It is decided by the cup.
- OP
Layer 2: Cup Behavior and Cup Outcome
These terms describe cup behavior and cup outcomes across temperature stages and post-roast time.
- AC
- FAC
- SF
- HCM
Layer 3: Thermal Mechanism and Energy Control
These terms describe energy mechanisms that produce, delay, support, or interrupt cup behavior.
- CDV
焦糖化分歧
Active Documentation
The hot cup speaks through one kind of sweetness. The cool cup preserves another.
- TAL
熱能吸收滯後
Active Documentation
You adjusted. The bean hasn't responded yet.
- TDR
末段柔化烘焙
Active Documentation
Heat exits. The cup opens.
- EGBS
能量空白停滯
Active Documentation
The curve is still present, but energy briefly stops speaking.
Layer 4: High-Risk Maturity Path
These terms describe maturity paths that cannot rely on first crack as final authority.
- NCR
- PCM
爆點前熟成
Active Documentation
The coffee has already been dropped. The crack comes afterward.
Layer 5: Traffic, Troubleshooting, and Research Notes
These entries route operational questions and case observations back to the core system.
- PLO
探針滯後超調
Active Documentation
You adjusted. Then adjusted again. The coffee absorbed all of it at once.
- Research Note
Published Thu May 14 2026 00:00:00 GMT+0000 (Coordinated Universal Time)
A falling or negative Rate of Rise is often treated as a roasting problem to be avoided. In our system, it is sometimes the intended outcome. The question is not whether RoR is negative. It is why.
Layer 6: Boundary and Failure Expressions
These entries remain diagnostic boundary expressions, not flagship ontology anchors.
- CICC
陡降冷崩
Active Documentation
It holds while hot. As it cools, the structure breaks.
Observational Frameworks
Observer Protocol
Defines the conditions under which phenomena can be observed, documented, and compared. Temperature stages, temporal windows, observation fields, and boundary conditions.
View Observer Protocol →Phenomenon Boundary Archive
Records the conditions under which a given phenomenon stops holding. Boundary observations are not exceptions , they are data that define the limits of each phenomenon.
View Boundary Archive →Temperature Stages
Hot Cup (above 65°C) , Warm Cup (50 to 64°C) , Cool Cup (below 49°C). Phenomena behave differently across temperature stages. Observation consistency requires stage-aware recording.
Temperature Stage Reference →Temporal Observation Windows
Day 1 to 3 (degassing), Day 4 to 14 (primary window), Day 15+ (extended arc). Some phenomena only become observable across the post-roast time arc.
Temporal Windows Reference →Machine-Readable Reference
Structured data for AI retrieval systems and semantic integration: phenomena.json