PlantLightIndex Research Methodology

Why PlantLightIndex publishes its methodology

Plant-light advice often looks more precise than the evidence behind it. A care page may show one number for a species, another site may show a much wider range, and a grow-light manufacturer may publish PPFD at one distance without showing the complete measurement map. PlantLightIndex is designed around a different idea: users should be able to see not only the recommendation, but also the kind of evidence used to create it and the uncertainty that remains.

The methodology hub documents that process. It explains how plant identities are resolved, how practical PPFD references are separated from physiological experiments, how grow-light measurements are stored, how confidence is assigned and why calculator behavior changes when evidence is weaker. This is not a promise that every record is perfect. It is a record of the rules used to keep imperfect evidence from being presented as certainty.

Measured values, estimates and recommendations are different things

PlantLightIndex treats a measurement as an observation, not automatically as a recommendation. A PPFD reading taken at a leaf tells you how much photosynthetically active photon flux reached that position at that moment. A published greenhouse treatment tells you what researchers supplied under a particular experiment. A photosynthetic light-saturation point describes a physiological response. A practical indoor reference is an editorial recommendation intended to help a houseplant grower make a decision. Those records can inform one another, but they are not interchangeable.

This distinction prevents a common failure in plant-light advice. A plant may survive under a very low PPFD treatment while growing slowly or changing form. Another study may show photosynthesis continuing to increase until a much higher PPFD. Neither number, by itself, proves that the lower value is ideal or that the higher value should be used in a home. PlantLightIndex therefore stores measurement context, evidence scope, source type and recommendation status alongside the number.

Missing evidence stays visible

Some plant profiles contain a practical numerical PPFD range. Others show only a parent-species or genus reference. Some remain qualitative because a defensible species- or cultivar-specific numerical target has not been established in the sources reviewed for the site. That unevenness is intentional. A database becomes less useful when every empty field is filled with a plausible-looking number.

When a value is absent, the site should explain what is known instead. A page may state that a plant is commonly described by an extension source as preferring bright indirect light, or that a cultivar has demonstrated a different physiological response from its green parent, without converting those statements into a precise household target. The calculators then change behavior according to the record: full, contextual or qualitative.

Four layers sit between a source and a recommendation

1. Identity

The first question is whether the source is about the same plant. Scientific names, horticultural names, patents, trade names and cultivars do not always line up cleanly. PlantLightIndex keeps the accepted scientific identity separate from common names and commercial labels. When sources disagree, the conflict is preserved instead of silently choosing whichever name is most convenient.

2. Observation

The second layer records what the source actually reports. That may be a PPFD treatment, DLI, photoperiod, light-saturation point, window description, manufacturer PPFD point or a qualitative placement such as bright indirect light. The observation is stored with its source and context before the site decides whether it is useful for a recommendation.

3. Interpretation

The third layer asks what the observation can support. A tissue-culture treatment may be valuable evidence about propagation but weak evidence for a mature living-room specimen. A genus-level extension category can provide context for a cultivar but should not be presented as an exact cultivar target. Manufacturer measurements can support a bounded fixture interpolation only when the distances and settings are compatible.

4. Recommendation

Only then does PlantLightIndex assign a practical range, contextual range or qualitative status. The recommendation carries an evidence scope, basis, confidence level and status so the user can understand how much weight to place on it.

How the methodology changes the calculators

The calculator engine is not allowed to treat every plant record the same. A full record can compare a measured PPFD against a practical target. A contextual record can show how the user's reading relates to a broader parent or genus reference while warning that the range is not exact for the selected plant. A qualitative record can calculate DLI from PPFD and hours, but it cannot declare that DLI good or bad without a supported target.

The same rule applies to fixtures. A grow light with only wattage and PPF can appear in the fixture database, but it cannot produce a distance recommendation. A fixture with one PPFD point can show that observation but cannot define a curve. Multi-point data can be interpolated only inside the measured span. The grow-light measurement methodology documents those boundaries in detail.

Source hierarchy is useful, but context still matters

PlantLightIndex generally gives more weight to peer-reviewed controlled studies, university extension guidance, botanical institutions and government sources than to commercial or community observations. That hierarchy is not mechanical. A high-quality physiology paper can still be poorly matched to a household recommendation if the experiment studied tissue culture, production seedlings or a different taxon. A manufacturer can be the best primary source for its own fixture's electrical specification while still being a commercial source.

The site therefore scores both source quality and relevance. Taxon specificity, direct measurement, independent agreement and household relevance matter alongside authority. The evidence-confidence methodology explains how those dimensions become High, Medium or Limited labels.

What PlantLightIndex does not claim

The site does not claim that a practical PPFD range is a universal biological optimum. It does not claim that crossing the top of a practical range means immediate damage. It does not claim that a window direction predicts one exact PPFD, or that two fixtures with the same wattage deliver the same canopy light. It also does not claim that a calculated DLI target exists for a plant simply because PPFD can be multiplied by hours.

These limits are part of the product. When a user sees “Not established,” “contextual reference,” or “above our practical indoor reference,” the wording is deliberate. It protects the difference between what can be calculated and what can actually be recommended.

How to audit a PlantLightIndex result yourself

1. Open the plant or fixture page and read the evidence-transparency block.
2. Check whether the evidence scope is exact cultivar, exact species, parent/genus or broader.
3. Check whether the numerical value is a practical reference, experiment, physiology benchmark or fixture measurement.
4. Open the supporting sources and compare the site summary with the original publication.
5. For grow lights, verify the measurement distance and dimmer setting before using an interpolated range.
6. For natural light, measure at leaf level when a decision matters instead of relying only on window direction.

The searchable Source Library and downloadable Data Hub make this audit possible without reverse-engineering the site.

Methodology pages

How methodology supports search and AI retrieval

Clear methodology is useful to search systems because it makes entity relationships explicit. A plant page states the plant identity, the measured quantity, the evidence scope, the recommendation basis and the source. A fixture page states the model, measurement distance, PPFD, measurement source and interpolation limits. Those explicit relationships are easier to interpret than vague care prose that mixes all evidence into one paragraph.

The goal is not to write for a crawler instead of a person. The same structure helps a human decide whether a number is relevant. Answer-first sentences, descriptive headings, source links and stable terminology make the page easier to scan while also making claims easier to extract accurately.

Why methodology belongs in the navigation

Trust information should not be hidden in a footer disclaimer. PlantLightIndex exposes Methodology, Sources and Data as first-class site sections because they explain the product itself. A user who sees a contextual range on a plant profile can move directly to the methodology that defines contextual mode. A user who sees an interpolated fixture distance can inspect the measurement rules and download the underlying fixture record.

This internal linking also keeps the site focused. Instead of repeating the complete methodology on every profile, each profile shows the decision-specific evidence block and links to the canonical explanation.

Methodology review checklist

• Is the entity identity correct and clearly separated from aliases?
• Does each numeric observation retain source and measurement context?
• Is a practical recommendation separated from physiology and survival evidence?
• Does calculator behavior match the evidence mode?
• Are contextual ranges labelled as contextual at every use point?
• Does fixture interpolation stay within compatible measured endpoints?
• Do public datasets preserve null values and provenance?
• Can a user reach the original source from the profile or Source Library?

These questions guide Stage 10 and future releases. The downloadable data and source library make the answers visible outside the codebase.

What changes as PlantLightIndex grows

The methodology is designed for a small curated launch database and for a much larger future catalog. Adding hundreds of plants should not require weakening the publication threshold. Instead, the same statuses can identify records that are ready for numerical calculation, records that are useful only as context and records that still need research. The database can grow unevenly while remaining honest about where the evidence is strongest.

The same applies to grow lights. A larger fixture catalog will naturally contain a mix of multi-point curves, single measurements and specification-only products. The public interface should make those differences easier to see as the catalog expands, not hide them behind one generic comparison score. Independent testing can add a new evidence layer without deleting manufacturer provenance.

Future methodological changes should be documented when they alter the meaning of a public field or calculator result. Cosmetic interface changes do not require a new scientific method, but changing confidence thresholds, interpolation rules or publication criteria should be treated as a data-governance decision. That keeps old and new records comparable.

One methodology, several user interfaces

The same evidence rules appear differently across the site. A plant profile emphasizes recommendation basis and scope. A calculator emphasizes whether a measured PPFD is below, within or above a practical reference. A chart emphasizes comparison and missing-data visibility. A fixture page emphasizes measurement span and source provenance. A dataset page exposes the underlying fields directly.

These interfaces should not contradict one another. If a plant is qualitative in the data layer, no chart or calculator should quietly invent a numerical target. If a fixture is spec-only, no commercial guide should display a calculated distance. Stage 10 makes those cross-page rules explicit and gives users canonical methodology pages when they want the deeper explanation.