Economap Logo

Economap

☰
×

Library route

Reference notes are working rules for reading product structure without guessing

These notes exist for moments when the reader is not stuck on a single product, but on the method they should use to interpret the whole structure. Product nouns often overlap. A product can be wearable and medical-adjacent, consumer-facing and measurement-heavy, reusable but still dependent on controlled cleaning, or portable but only inside a facility. Reference notes preserve a small set of rules that keep classification consistent when overlap is real.

The focus is practical. These notes emphasize how to choose a dominant path, when to accept legitimate multi-axis reading, how to avoid accidental polyhierarchy, and how to tell whether a classification claim is supported by real selection pressure rather than by a convenient label. They also clarify what a canonical page should contain and what it should refuse to pretend it can solve.

Back to Library Browse comparisons

Working principles

Principles that keep product classification consistent under overlap

These principles are intended to be small, repeatable, and practical. They are not definitions. They are rules for choosing a reading that stays stable when the product list grows.

01

Choose the dominant pressure, not the most descriptive noun

Many nouns fit. The dominant pressure is what repeatedly decides value: user risk, result confidence, downtime, or routine friction. If you cannot name the pressure, the placement is not stable yet.

02

Separate category from environment

Category is broad world placement. Environment is a use setting. A product can be a consumer product and still need a clean environment reading. When the setting changes the meaning, use environment pages to keep that truth visible.

03

Prefer a single dominant home, then refine by facets

A stable system usually assigns one dominant placement, then refines through type, form factor, application, environment, and feature. This avoids duplicating the same object across multiple category trees.

04

Use comparisons when the boundary changes expectations

If the label changes what the reader expects about reset, evidence, safety, or maintenance, a comparison page is often the correct first stop. It clarifies what changes downstream when one side wins.

05

Cycle questions beat moment questions in home and reuse

Some products fail not at the moment of use, but in the minutes after: cleaning, drying, storage return, and next-use readiness. When cycle behavior dominates, treat it as a feature and environment problem, not only a type problem.

06

Evidence obligations create instrument-like behavior

When outputs are treated as evidence rather than guidance, measurement trust becomes dominant. That pulls in calibration, drift, and interpretation discipline. It can change whether a product is better read as a device or an instrument.

07

Industrial fitness is often a recovery problem

If downtime and safe recovery dominate, service access, isolation behavior, and diagnostic clarity become part of product meaning. In that case, the industrial landscape and site environment often clarify the strongest constraints.

08

Do not hide ambiguity inside a shallow page

If a page cannot state boundaries and pressure, it should not pretend to be a final placement. Use the Library routes to resolve the ambiguity before forcing a taxonomy branch to absorb it.

Decision recipes

Short procedures for common classification decisions

These recipes are meant to be used quickly. Each one forces a dominant reading and then names the next route that usually resolves the remaining uncertainty.

Recipe: Choose dominant category when two categories seem plausible
  1. Name the most punished failure: user harm, result doubt, downtime, or abandonment.
  2. Name who maintains correctness: trained staff, technicians, or ordinary habit.
  3. Choose the category whose dominant pressure matches those realities, then refine by type and environment.
Category Overviews Application Landscapes Catalog Categories
Recipe: Decide whether home-use logic is actually dominant
  1. Ask whether the product must survive ordinary storage, visual clutter tolerance, and partial maintenance.
  2. Ask whether the product must be readable by non-specialists without a controlled workflow.
  3. If yes, treat home-use setting as interpretive, then refine by reusability, portability, and form factor.
Home and Personal Use Reusable Products Portable Products
Recipe: Decide whether reuse is real or only theoretical
  1. Describe the reset loop: clean, dry, store, retrieve, trust.
  2. Identify the failure point: drying time, residue traps, parts scatter, no storage home, loss rate.
  3. If the loop cannot be completed reliably, treat disposable behavior as the honest reality for that context.
Reusable vs Disposable Everyday Reusable Products Containers and Cases
Recipe: Decide when a measurement-heavy product should be treated as instrument-like
  1. Ask whether outputs are treated as evidence with accuracy expectations, not only as guidance.
  2. Ask whether calibration, drift management, and repeat comparability matter in the real workflow.
  3. If yes, treat measurement trust as dominant, then refine via measurement application and instrument type.
Devices vs Instruments Measurement and Monitoring Instruments

Overlap rules

How to handle products that legitimately touch multiple branches

Overlap is normal. The goal is not to eliminate it. The goal is to keep the system readable by choosing when overlap becomes a cross-link versus when it becomes duplication.

Facet overlap is expected

A product can be wearable and reusable and portable at the same time. These are facets. They should usually be handled through cross-links and downstream refinement rather than through multiple dominant placements.

Category overlap should be rare and deliberate

Broad category overlap is a high-risk move because it creates inconsistent expectations. If you allow it, it should be because the product genuinely operates under two dominant pressure regimes and both readings remain stable.

Environment overlap is common but needs dominance

The same product class can appear at home, in labs, in clinics, and on sites. The environment that dominates is the one that changes meaning the most. When in doubt, use the landscape route first, then the environment page.

Use cross-links as evidence, not decoration

A cross-link should indicate that a real pressure is shared, not that two words sound related. The link is a promise: the reader will learn why the relationship matters in practice.

Anti-patterns

Patterns that quietly destroy clarity in product classification

These are common failure modes in structured product systems. They are easy to create and hard to clean up later.

Anti-pattern
What it looks like
What to do instead
Marketing category drift
Words like professional, advanced, premium used as placement.
Name the dominant failure cost and workflow discipline.
Polyhierarchy by accident
A product appears under multiple category trees without a rule.
Choose a dominant placement, then cross-link via facets.
Type overload
Everything becomes a device or equipment without pressure detail.
Use application, environment, and landscape to supply meaning.
Cycle blindness
Reusable and home products judged only at first-use moment.
Evaluate cleaning, drying, storage return, readiness, abandonment risk.
Evidence inflation
Numbers shown as if they are measurements without obligations.
Decide whether outputs are evidence or guidance, then choose instrument logic only when warranted.

Next routes

Continue into the route that matches the kind of uncertainty you still have

Reference notes resolve method. The next step is usually a route that resolves content.

Library route Application Landscapes When sector context changes the meaning of familiar product classes. Library route Category Overviews When broad branch placement is unclear and needs boundary rules. Library route Comparisons When a close boundary changes expectations about reset, evidence, or maintenance. Catalog Catalog When you know the dominant frame and now need structured refinement by axis. Products Products When the classification is clear and the remaining need is canonical product-facing detail. Updates Updates When new launches, guidance, or changes materially shift how a branch should be read.