Incumbent Use Register¶
Artifact — instantiates Displacement-Aware Capacity Admission
A register of existing formal and informal uses of a shared substrate, including protected functions and dependency strength.
Before you can judge what a newcomer will push out, you have to know who is already there — and most of them are not on any list. Incumbent Use Register is the standing artifact that names the shared substrate once, in a fixed capacity unit, and then enumerates every activity currently drawing on it: the metered and billed ones, but also the informal, seasonal, low-status, public-good, and ecological uses that no ledger tracks. Its defining move is to make the invisible occupants visible and citable before any admission decision is on the table, so that a displaced party is a named row in a document rather than a complaint that surfaces only after the space is gone. It is a description, not a decision: it says who is here and how much they lean on the substrate, and it says nothing about who should stay.
Example¶
A mid-sized city library is under pressure to hand two of its six ground-floor meeting rooms to a new coding-bootcamp partnership that promises attendance figures and a grant. Before anyone signs, a librarian builds an Incumbent Use Register for the rooms. The substrate is stated plainly — six rooms, roughly 84 bookable room-hours a week — and every current user gets a row. The formal ones are easy: the ESL class that reserves Tuesday evenings, the two nonprofits with standing bookings. The register's real value is the rows nobody had written down: the job-seekers who walk in and use an empty room for interviews, the Alzheimer's caregivers' support group that meets informally when a room is free, the after-school kids who have nowhere else warm to sit until a parent finishes a shift.
Each row carries a rough dependency strength — could this use go elsewhere, and at what loss? The support group is flagged as high-dependency with no substitute; the interview walk-ins are medium; a book club that could meet at a member's home is low. When the register is laid on the table, the conversation changes shape. The bootcamp had claimed the rooms were "mostly empty" — technically true by the booking system, which never saw the walk-in uses. The register doesn't decide whether the bootcamp gets its rooms. It just makes sure that if the caregivers lose their meeting space, that outcome is a choice someone made with the row in front of them, not a fact discovered months later.
How it works¶
What distinguishes the register from a generic asset inventory is its insistence on the unmetered occupants and on dependency, not just presence:
- Fix the substrate and unit once. One named resource, one capacity unit (room-hours, acre-feet, shelf-facings), so every row is commensurable.
- Enumerate across visibility tiers. Walk the substrate for formal bookings, then deliberately hunt the informal, seasonal, public-good, and ecological uses that generate no transaction record — these are exactly the ones an entrant's "unused slack" claim will quietly annex.
- Tag dependency strength and substitutability. For each use, record how much it leans on this substrate and whether it can move elsewhere without loss; a low-volume use with no substitute can matter more than a high-volume one that can relocate freely.
- Mark protected candidates, don't set floors. Flag which uses are plausibly public-good or vulnerable, leaving the actual reservation level to the mechanisms that set floors.
The output is a living document, refreshed on a cadence, that other mechanisms read as their baseline.
Tuning parameters¶
- Discovery depth — how hard you hunt for informal and ecological users. Deeper discovery catches the uses most likely to be silently sacrificed, but costs field time and can surface uses no one wants to acknowledge.
- Dependency scale granularity — a coarse high/medium/low tag versus a quantified reliance score. Finer grain sharpens later prioritization but invites false precision about tacit needs.
- Refresh cadence — one-shot snapshot versus a standing register updated each cycle. Frequent refresh keeps the baseline honest as uses drift, but adds upkeep.
- Inclusion threshold — how small a use must be before it gets its own row versus folding into an "other" bucket. A low threshold protects marginal users; a high one keeps the register legible.
When it helps, and when it misleads¶
Its strength is that it defeats the "empty space" illusion at its source: the entrant's benefit is measured, the incumbent's use is diffuse, and the register is what drags the diffuse thing into a citable form before the decision. It is the artifact that makes Ostrom's point operational — that durable governance of a shared resource depends on first recognizing the users a formal system renders invisible.[n1]
Its failure mode is the register that records only what is easy to see and then wears the authority of completeness. A tidy list of formal bookings can legitimize a displacement by making the walk-in users look like they were considered when they were never enumerated — an absence dressed as a clean bill. It also goes stale: a snapshot from last year misstates today's occupants. The guarding discipline is to treat the informal-use hunt as the register's real work, date every entry, and refresh on a cadence rather than freezing the first pass. The register describes; it does not decide, and dressing it up as a verdict is its most common misuse.
How it implements the components¶
The register is a pure baseline artifact — it fills the two descriptive components and no more:
shared_substrate_inventory— names the finite shared resource once and fixes the capacity unit that makes every use commensurable.incumbent_use_baseline— enumerates existing formal and informal uses with dependency strength, establishing the "who was here, and how much" that every later comparison is measured against.
It does not set the protected_function_floor (it only flags candidates — Capacity Reservation Rule sets the level), does not estimate capacity_budget_and_slack_estimate (that is Substrate Capacity Budget), and does not model displacement_channel_map or displacement_elasticity_estimate — those belong to Displacement Impact Assessment.
Related¶
- Instantiates: Displacement-Aware Capacity Admission — the register supplies the incumbent baseline the whole archetype is measured against.
- Sibling mechanisms: Substrate Capacity Budget · Displacement Impact Assessment · Shadow Displacement Accounting · Capacity Reservation Rule · Moratorium and Reversal Gate · Offset or Relocation Plan · Phased Admission Trial · Crowding-Out Monitoring Dashboard
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: Incumbent Use Register operates as a durable record, ledger, register, or trace whose value depends on preserving actual state or history because it a register of existing formal and informal uses of a shared substrate, including protected functions and dependency strength
Independent corroboration: The frozen evidence defines Incumbent Use Register as 'A register of existing formal and informal uses of a shared substrate, including protected functions and dependency strength', so its operative form is Record, Log & Register.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Political Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Recognizing all legitimate formal and informal users before allocating a shared resource follows common-pool resource governance.
Related originating lineages:
- Economics & Finance — Scarce-capacity allocation, displacement, and incumbent dependence are economic incidence concerns.
- Environmental Science & Climate Studies — Ecological and customary uses of land, water, and commons provide canonical applications.
- Public Administration & Policy — Retained as a formative lineage because the independent reviewer identified it as primary: Recording formal and customary claims before reallocating a shared resource follows common-pool resource governance associated with Ostrom.
- Sociology & Anthropology — Ethnographic recognition of informal and customary use prevents the register from reducing reality to formal title.
Review resolution: Ostrom’s primary work on common-pool governance identifies clear user boundaries, collective-choice rights, monitoring, and nested institutions. A register of incumbent users operationalizes those institutional-governance principles; public administration remains a material implementation lineage. The retained alternate domains identify independent or materially shaping provenance, not downstream reach alone. domain_reach=multi_domain because the mechanism has independent established use in several fields. The encyclopedia entry deliberately composes those lineages.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
- https://www.nobelprize.org/uploads/2018/06/ostrom_lecture.pdf — Ostrom prize lecture enumerating user boundaries and other design principles for robust commons governance.
Notes¶
The register is foundational: nearly every other mechanism here reads it. That is exactly why it must stay a description. The moment it starts recording who ought to keep their space, it becomes a reservation rule wearing an inventory's clothes, and the neutral baseline everyone else relies on is lost.
[n1] Elinor Ostrom's studies of common-pool resource governance found that durable, self-organized management depends on first recognizing the full set of legitimate users — including customary and informal claimants a formal registry ignores. The register operationalizes that recognition step. ↩