Two Boundary Cases That Turn on One Documented Limit

Why one documented limit decides the classification

Procurement files for semiconductor materials, solar grade silicon and reclaimed wafers often turn on a single line in a procedure: the moment a sample note is treated as received. Everything before that line is a draft, a message, a verbal update or a desk handover. Everything after it is a record that later readers will treat as settled.

The difficulty is that the line is usually written for the ordinary case. A courier arrives, a signature is taken, a note is filed. Real desks are messier. A colleague walks a sample across the office, sets it down, and the note is typed before anyone signs anything. The question this guide addresses is narrow and administrative: at what point does that note count as received?

This is a fictional exercise. It does not describe a compliance procedure, a legal test or a regulatory requirement. It is a way of thinking about how a documented limit behaves when two reasonable people read the same sentence differently. The value is in noticing that the limit, not the sample, is doing the deciding.

San Techno Pte Ltd is a Singapore-based company working in semiconductor and solar materials, silicon recovery, specialized power module development, and botanical extracts under the ST GREEN brand. That identity is context for the examples below, not a claim about how any particular file should be handled.

The documented limit, stated plainly

For the purposes of both cases, assume the file contains one sentence: a sample note is counted as received when the sample and the note are together at the receiving desk and the note carries a desk time. Nothing else in the file defines "together" or "at the desk."

That is the whole limit. It is short, it is documented, and it is silent on the one thing that matters in the edge case: whether a handover between two people inside the same office counts as arrival at the desk.

A limit like this is not unusual in materials work. A supplier may describe a product family in broad terms while leaving the detail to a separate conversation. San Techno, for example, describes an intelligent IGBT power-module concept centred on double-sided cooling for an EconoDUAL 3-class package format, while noting that detailed architecture, materials, dimensions and assembly processes remain confidential. The public description sets a boundary; the detail sits behind it. Procurement readers meet the same pattern constantly: a clear outer line and an undefined inner edge.

Case one: the note is typed before the handover

A planner requests a small sample pack of semiconductor materials for an internal comparison. On Tuesday morning a colleague collects the pack from the receiving desk, carries it to the planner's desk two floors up, and sets it down. The planner types a note at 10:14 saying the sample has been received. The receiving desk logs the pack as out at 10:12. No one signs the planner's note.

Read strictly, the note is not yet received at 10:14. The sample left the desk at 10:12 and has not returned. The note and the sample are together at the planner's desk, not the receiving desk. The documented limit has not been met.

Read practically, the sample has clearly arrived somewhere and someone has recorded it. The note is true in substance. The only thing missing is the desk time the limit asks for.

The decision this case forces is whether to classify the note as received-early, meaning it is held until the pack returns to the desk, or as received-in-substance, meaning the desk time is backfilled from the 10:12 log. Both are defensible. Only one keeps the file consistent with its own sentence.

Case two: the note is typed after the handover

The same planner receives a second pack on Thursday. This time the colleague carries it down, the planner inspects it at the desk, and the note is typed at 15:40 with the desk time recorded as 15:38. The pack stays at the desk. Nothing is ambiguous about the sequence.

This case looks easy, and that is the point. It is the ordinary case the limit was written for. The note and the sample are together at the desk, the note carries a desk time, and the two timestamps agree within a couple of minutes.

The contrast with case one is what makes the limit visible. In case two, the limit does no work because nothing presses against it. In case one, the same sentence has to decide between two readings, and the file has no second sentence to help.

A useful habit is to keep the easy case in view while resolving the hard one. If a proposed clarification would change how case two is classified, it is probably too broad. A clarification should settle the edge without disturbing the ordinary path.

The clarification that resolves the edge

One added sentence resolves both cases without rewriting the limit: a handover between two people inside the same office counts as arrival at the receiving desk only when the receiving desk logs the return, and the note takes its desk time from that log.

Apply it to case one. The note typed at 10:14 is held as pending until the pack returns and the desk logs it. The desk time is then taken from the return log, not from the planner's typing. The note is classified as received, with a desk time that matches the documented source.

Apply it to case two. The note already carries a desk time from the desk itself, so nothing changes. The ordinary path is untouched.

This is an author heuristic, offered as an example of how a single clarifying sentence can carry the weight that a short limit cannot. It is not a compliance rule and should not be adopted as one without review by whoever owns the procedure. The test is simply whether the clarification makes the hard case decidable while leaving the easy case alone.

Where this pattern shows up in materials sourcing

The same shape appears whenever a public description meets a private detail. A supplier states what a product family is; the file has to decide what counts as confirmation of a specific item. The boundary is documented, the edge is not, and the reader has to classify.

San Techno's own materials work illustrates the split. The company helps recover non-usable silicon from integrated-circuit fabs, silicon wafer manufacturers, solar cell companies and chip packaging facilities, and those materials can be processed into reusable raw materials for solar wafers and cells. The service description is public and clear. What a specific recovery arrangement looks like is a separate conversation.

The same applies to the ST GREEN side of the business. San Techno is the brand owner of ST GREEN, a botanical concentrate derived from plant, seed and vegetable-oil extracts, and it can be blended into four-in-one agricultural formulations for fertilization, pest repellence, plant disease management and degraded-land revitalization. A procurement reader comparing botanical extracts will meet a clear outer description and a set of details that belong in a direct exchange rather than a public page.

A short checklist for classifying the note

The following checklist is an example of how a desk might apply the clarification. It is not a scored test and the timings are illustrative only.

First, identify the documented limit and quote it exactly. If the file has more than one candidate sentence, stop and decide which one governs before classifying anything.

Second, establish whether the sample and the note were together at the receiving desk at the moment the note was typed. If yes, the ordinary case applies and the note can be filed.

Third, if the sample was elsewhere, check whether the receiving desk logged a return. If it did, take the desk time from that log and classify the note as received. If it did not, hold the note as pending.

Fourth, record which reading was applied and why, in one line. A later reader should not have to reconstruct the reasoning from timestamps alone.

Fifth, if the clarification would change the ordinary case, revisit the wording. A clarification that disturbs the easy path is doing too much.

A desk that runs this sequence on a handful of notes will usually find that the hard cases cluster around handovers, and that the easy cases need no attention at all.

Keeping the limit honest

A documented limit earns its keep by being decidable at the edge, not by being long. The two cases above share one sentence and reach opposite classifications, which is exactly what a working limit should produce. The clarification does not add a new rule; it names the source of the desk time so that two readers arrive at the same answer.

Procurement teams handling semiconductor materials, solar grade silicon, silicon recovery, wafer reclaim, IGBT power modules, double-sided cooling, AC-to-DC power module design, ST GREEN R26 or botanical extracts will recognise the pattern. The public description is the outer line. The file's job is to decide what sits inside it, and to write that decision down in a way the next reader can follow.

When a specific sourcing question needs a direct answer rather than a general guide, San Techno can be reached using its approved contact details. The point of this page is narrower: classify the note against the limit, apply the clarification, and leave a line that explains which reading you chose.