Skip to content
✎ FeedbackNew here?
How well testedNever testedno settled test on record — read it as unproven, not as workingRecorded: LIVE (viewing surface — applies no selection)

Microstructure Stress — Canonical Reference

One-line definition: Microstructure Stress applies no selection rule and filters nothing: it is a viewing surface over exchange housekeeping — stock-lending activity, price-band locks and surveillance (ASM/GSM) lists — as each is published. It reports an observed state, not a judgement about it.


1. What it is

Three mechanical facts about how a stock is currently allowed and able to trade:

This lens has no rule. Nothing here screens a universe or ranks a name. A stock appears because the exchange published a list and it was on it, or because its own closing price met an arithmetic definition of a lock. The admission criterion belongs to the exchange.

Where this stands: these are conditions, not conclusions. A name under surveillance is a name the exchange has placed under extra measures — often producing mechanically forced flows as leveraged positions unwind under higher margins. That is information about plumbing. It is not a verdict on the company.

2. Our variation vs. the standard technique

There is no standard technique. The deliberate choices are:

3. How it works (methodology)

Band locks. A lock is an arithmetic condition on the published close: close equals the day's high or low, and that equals the band limit. Consecutive locked days form a streak, and streaks at or beyond a stated minimum length are marked as a persistence cohort. The threshold is a named constant in code (band_lock.FLAG_MIN_STREAK) and is printed on the board beside the count, so the reader always sees the definition next to the number. It is a definition of an observable state — not a filter on what the board shows, and not a claim about what follows.

Surveillance. The day's published list is the day's state. Transitions are obtained by self-joining consecutive dates. Price-band events are carried with their NULL semantics kept honest rather than defaulted.

Stock lending. Two EOD files per trading day: the fee/flow tape and the open-position stock. A missing file on a holiday returns 404 and is a clean skip, never a zero (§6).

What is deliberately absent. No ranking, no score, no ordering by attractiveness, and no claim in either direction about what any of these states precedes.

4. Status, validation & honesty fence

LIVE — and no study has been run on any of these feeds, in either direction. That is the recorded status, stated in the code's own on-page fences and in the feed manifest, not an omission from this page:

Any future consumer that ranks or trades off these feeds must first record a pre-registered, leak-free study in the strategy ledger. None exists today.

5. Where it lives (code· routes· DB· timers)

6. Data & provenance

All primary-source (Guardrail #8), all NSE:

StreamSourceClock rule (verbatim from the manifest)
SurveillanceNSEthe day's list is the day's state; transitions derivable by self-join
Stock lendingNSE (archives/slbs)EOD publish; 404 = holiday/not-published = clean skip
Price bandsNSEcaptured from the security-wise band feed's birth date forward

🔴 Three provenance facts a reader must carry:

1. The band record has a birth date. Past bands are reconstructed from the change log back to that day and no further. Streaks cannot exceed the captured window, and earlier locks are invisible by construction. The board prints this date. 2. A 404 is a skip, not a zero. A non-publishing day is absent, and an absent day must never be read as "no lending activity". 3. The earliest surveillance date is a baseline. Because transitions are diffed between consecutive lists, the first captured list looks like mass entry and is not.

7. Terminology canon

Reader-facing definitions: the metrics glossary.

8. Decision & session history

9. Open items / frozen work

10. Sources of truth