ONE NYC CURB / TEMPORAL RULE APPLICABILITY DOSSIER v0.1

Status: RESEARCH / PRE-CAPTURE ONLY
Utility family: TEMPORAL / JURISDICTIONAL APPLICABILITY
Field fixture: Lewis Street between Broome Street and Delancey Street South, Manhattan
Time comparison: 2026-08-06 vs 2026-08-09
Research date: 2026-08-09
Authority: NONE — research input only
Explicit non-claims: This dossier does not create a parking authorization, legal opinion, CaptureReceipt, SourceEdition, field observation, SRS receipt, admission, standing, or canonical Counterpedia identity.

A. WHY THIS SUBJECT

The user question is mundane:

“Can I park here?”

But the truth-value is not a property of the street.

It is a function of:

• exact curb segment;

• side/direction;

• permanent signs;

• temporary signs;

• general citywide prohibitions;

• day of week;

• clock time;

• date;

• holiday/suspension status;

• vehicle class;

• meter rules;

• physical conditions such as hydrants;

• and, critically, the current state of signs actually posted in the street.

This is a different Counterpedia primitive from both the Demo Corpus Twelve and the USB-C Quiet Utility fixture:

APPLICABILITY — compile rules against a real object, place, actor and time.

The final answer may be derived from several source classes that do not themselves say:

“Frank can park this passenger car at coordinate X at 2:14 PM.”

Counterpedia can resolve the applicable rule stack without pretending that a citywide rule or database is itself a live curb observation.

B. FIXED FIELD FIXTURE

CURB-OBJ1 — Street segment

Street: Lewis Street
Between: Broome Street and Delancey Street South
Borough: Manhattan
Project area: East Side Coastal Resiliency / Parallel Conveyance work zone

This fixture is selected because the City published a real, bounded temporary parking restriction with:

• exact street segment;

• exact start date;

• explicit 24-hour / 7-day operation;

• exact scheduled end date;

• and an explicit warning that field conditions may change and posted signs must be followed.

That gives Counterpedia a clean temporal override without requiring controversy.

C. TWO QUESTIONS ABOUT THE SAME CURB

Q-A — August 6, 2026

According to the official temporary-work record, may a passenger vehicle park on Lewis Street between Broome Street and Delancey Street South on August 6, 2026 at 2:00 PM?

The City's ESCR community advisory says:

• No Parking;

• on Lewis Street between Broome Street and Delancey Street South;

• beginning July 23, 2026;

• 24 hours/day, 7 days/week;

• ongoing until August 7, 2026;

• for roadway restoration.

Research-level result

NO — the captured official temporary-restriction record, if still operative and posted in the field as described, prohibits parking at that time.

Important qualification:

The online advisory itself repeatedly tells users to follow posted signs and says schedules may change due to field/weather conditions.

So Counterpedia should distinguish:

OFFICIAL PLAN / NOTICE STATE
  temporary_no_parking = active

FIELD-CONFIRMED STATE
  requires contemporaneous posted-sign observation

The first can be answered from web custody.

The second requires a field observation.

Q-B — August 9, 2026

May a passenger vehicle park on that same curb on August 9, 2026?

The temporary advisory's stated period ended August 7.

That means:

the July 23–August 7 temporary advisory no longer supplies a current August 9 prohibition.

It does not mean:

parking is therefore allowed.

The lower-level rule stack becomes relevant again:

• permanent curb signs;

• alternate-side rules;

• meter rules;

• hydrants;

• loading/no-standing restrictions;

• any new temporary sign;

• current construction conditions;

• vehicle class.

Research-level result

UNKNOWN / BASE RULES MUST BE RESOLVED.

This is the product reveal:

Aug 6:
temporary rule active
    ↓
NO

Aug 9:
temporary rule expired
    ↓
not YES
    ↓
evaluate permanent + current field rules
    ↓
UNKNOWN until those inputs are resolved

An expired prohibition removes one reason for NO; it does not create positive authorization.

D. PRIMARY SOURCE INVENTORY

CURB-S01 — ESCR active construction notices page

Issuer: City of New York / East Side Coastal Resiliency
Title: PC Construction Notices
Locator: https://www.nyc.gov/site/escr/project-updates/pc-construction-notices.page
Source class: first-party municipal current project notice index
Priority: P0

Relevant current-page facts observed 2026-08-09:

• Parallel Conveyance work includes Lewis Street / Delancey Street areas;

• the page lists No Parking on Lewis Street between Broome Street and Delancey Street South;

• temporary restriction begins July 23, 2026 and continues until August 7, 2026;

• purpose is roadway restoration;

• readers are told to follow posted signs.

Important source-version behavior As of August 9, the page still displays the now-ended advisory. Therefore:

still listed on current page does not mean still temporally operative.

A rule engine must evaluate its explicit valid-time interval.

CURB-S02 — Exact Lewis Street community advisory

Issuer: City of New York / East Side Coastal Resiliency
Document: No Parking — Lewis St. between Broome St. & Delancey St. South
Issue date: July 23, 2026
Exact PDF locator:
https://www.nyc.gov/assets/escr/downloads/pdf/260723_SANDRESPC_Advisory_Parking_Lewis_St_En.pdf
Source class: first-party municipal temporary restriction advisory
Priority: P0

Exact operative content:

• No Parking

• Lewis St. between Broome St. & Delancey St. South

• beginning Thursday, July 23, 2026

• 24 hours/day, 7 days/week

• ongoing until August 7, 2026

• necessary for roadway restoration

• follow all posted signs

• schedule may change due to weather/field conditions

This is the central temporal-rule artifact.

CURB-S03 — NYC DOT Parking Regulation Locations and Signs dataset

Issuer: NYC Department of Transportation / NYC Open Data
Dataset: Parking Regulation Locations and Signs
Dataset ID: nfid-uabd
Landing: https://data.cityofnewyork.us/Transportation/Parking-Regulation-Locations-and-Signs/nfid-uabd
API documentation: https://dev.socrata.com/foundry/data.cityofnewyork.us/nfid-uabd
Source class: municipal operational sign inventory
Priority: P0

The dataset contains current and historical parking regulation signs and includes fields such as:

• order number;

• current/historical record type;

• borough;

• on/from/to street;

• side of street;

• sign code;

• sign description;

• sign-design void date;

• distance from intersection;

• arrow direction;

• coordinates.

NYC DOT says the data underlying its Parking Regulations Map is updated daily.

Critical limitation

NYC DOT/311 warns that the online locator may not reflect new or temporary local changes.

Therefore:

DOT sign inventory
≠
contemporaneous proof of every physical sign currently governing the curb

This is a planning/evidence layer, not omniscience.

CURB-S04 — NYC311 Parking Signs and Rules

Issuer: City of New York / NYC311
Title: Parking Signs and Rules
Locator: https://portal.311.nyc.gov/article/?kanumber=KA-01026
Source class: official public rule guidance
Priority: P0

Key facts:

• DOT maintains and installs NYC parking signs;

• Traffic Rules require only one sign for each block, so a driver should check the whole block;

• Parking Sign Locator provides sign locations and regulations;

• locator may not reflect new or temporary changes;

• actual posted signs should be read;

• ASP applies for the entire posted period even after a sweeper has passed;

• parking within 15 feet of either side of a fire hydrant is illegal;

• painted curb markings at hydrants do not define the legal distance.

This source is crucial because it makes physical-world observation a first-class input.

CURB-S05 — 2026 Alternate Side Parking suspension calendar

Issuer: NYC Department of Transportation
Title: Alternate Side Parking Suspensions
Locator: https://home4.nyc.gov/html/dot/html/motorist/alternate-side-parking.shtml
Source class: municipal annual temporal rule calendar
Priority: P0

Important semantics:

• ASP is suspended on listed legal/religious holidays;

• emergency suspensions can occur separately;

• on ordinary ASP-suspension holidays, other parking rules remain in effect;

• on major legal holidays, some No Stopping / No Standing / No Parking restrictions and meters are suspended if the restriction is not normally in effect seven days a week;

• seven-day restrictions such as No Standing Anytime remain.

This means:

ASP_SUSPENDED
does not imply
ALL_PARKING_RULES_SUSPENDED

CURB-S06 — NYC311 ASP rule semantics

Issuer: NYC311
Title: Alternate Side Parking and Street Cleaning
Locator: https://portal.311.nyc.gov/article/?kanumber=KA-01011
Source class: official rule guidance
Priority: P0

Key facts:

• when ASP is suspended, other posted parking limits/rules still apply;

• planned/emergency suspension has a defined time scope;

• ASP zones have a five-minute grace period;

• major legal holiday semantics differ from ordinary ASP-suspension holidays;

• drivers should inspect the entire block's posted signs.

This creates an explicit modifier relationship:

suspension
  targets = ASP rule class
  does_not_delete = unrelated curb restrictions

CURB-S07 — Parking meter semantics

Issuer: NYC311
Title: Parking Meters
Locator: https://portal.311.nyc.gov/article/?kanumber=KA-01239
Source class: official rule guidance
Priority: P1

Relevant facts:

• a five-minute grace period applies to parking meter expiration and ASP zones;

• Sundays and major legal holidays have special meter treatment.

A meter status is therefore another independent rule dimension rather than a proxy for general legality.

CURB-S08 — NYC DOT parking-regulations data authority/disclaimer

Issuer: NYC Department of Transportation
Title: Data Feeds, Dashboards & Open Data — Parking Regulations
Locator: https://www.nyc.gov/html/dot/html/about/datafeeds.shtml
Source class: municipal data provenance / disclaimer
Priority: P0

DOT says:

• it manages over one million traffic signs;

• its Parking Regulations Map can find regulations on any block;

• underlying sign data is distributed via Open Data and updated daily;

• public users should observe posted signage for compliance;

• the City disclaims completeness/suitability and warns about omissions/errors.

Counterpedia should preserve this source's own limitation rather than silently promoting an operational dataset into a perfect legal oracle.

CURB-S09 — Temporary parking restrictions / construction

Issuer: NYC Department of Design and Construction
Title: Inconveniences — Parking and Traffic Restrictions
Locator: https://www.nyc.gov/site/ddc/projects/inconveniences.page
Source class: municipal construction-rule guidance
Priority: P1

Relevant facts:

• temporary traffic/parking restrictions may be necessary for construction;

• restrictions can change;

• residents should observe posted notices/signage;

• notices are posted on affected streets in advance;

• noncompliant vehicles may be ticketed or relocated.

This is support for treating field temporary signage as a current-state input separate from permanent sign inventory.

CURB-S10 — Temporary-sign lifecycle

Issuer: NYC Department of Transportation
Title: Street and Roadway Construction
Locator: https://www.nyc.gov/html/dot/html/infrastructure/construction.shtml
Source class: municipal construction guidance
Priority: P1

DOT states contractors must remove temporary detour/parking restriction signs after work is complete, but acknowledges that sometimes they are not removed.

That creates a fascinating real-world state:

scheduled restriction expired
+
temporary sign still physically present

The digital schedule and physical streetscape can disagree.

Counterpedia must represent the disagreement rather than silently selecting one source.

CURB-S11 — Parking Summons Advocate sign-conflict guidance

Issuer: NYC Department of Finance, Office of the Parking Summons Advocate
Locator: https://www.nyc.gov/site/finance/vehicles/opsa.page
Source class: official enforcement/adjudication guidance
Priority: P2

The office advises drivers to read all block signs and states that when two signs genuinely conflict, the least restrictive should be followed and photographs preserved.

This is useful as a conflict-resolution/adjudication source, but should not be converted into a universal precedence algorithm without the underlying rule context.

CURB-S12 — NYC Traffic Rules reference

Issuer: City of New York / NYC311 / DOT
Rule family: Chapter 4 of Title 34, Rules of the City of New York
Relevant section: §4-08 — parking, stopping and standing
NYC311 locator: https://portal.311.nyc.gov/article/?kanumber=KA-03062
DOT rules hub: https://www.nyc.gov/html/dot/html/about/rules-and-regulations.shtml
Source class: governing legal rule family / official access surface
Priority: P0

Exact current rule bytes should be captured in CAP1 before authoring legal-rule propositions.

E. THREE EVIDENCE PLANES

The curb demo requires a separation that normal parking apps usually blur.

PLANE 1 — NORMATIVE RULES

Examples:

• §4-08;

• hydrant prohibition;

• ASP rules;

• holiday rules;

• vehicle-class rules.

These answer:

What legal rule exists?

PLANE 2 — ADMINISTRATIVE / DIGITAL STATE

Examples:

• Parking Regulations dataset;

• ASP suspension calendar;

• ESCR temporary advisory;

• meter blockface data;

• construction permit/notice.

These answer:

What does the City's operational record currently declare about this place/time?

PLANE 3 — FIELD OBSERVATION

Examples:

• timestamped photograph of physical sign stack;

• temporary paper sign;

• covered/removed sign;

• hydrant location;

• construction barrier;

• officer/flagger direction.

These answer:

What is actually present at the curb now?

The final parking answer may depend on all three.

F. EVALUATION MODEL

Do not encode one simplistic "parking_rule".

Use typed constraints.

Conceptually:

ParkingQuery:
  curb_segment
  vehicle_class
  observed_at
  intended_action = park | stand | stop
  intended_duration

RuleCandidate:
  kind
  spatial_scope
  temporal_scope
  actor_scope
  action_scope
  source
  source_edition
  field_observation
  status

Then evaluation:

1. resolve physical curb identity
2. resolve general citywide prohibitions
3. resolve permanent posted restrictions
4. resolve temporary restrictions
5. apply date/time activation
6. apply holiday/suspension modifiers
7. apply vehicle-class modifiers
8. apply meter/time-limit requirements
9. test field observations against digital state
10. return result + unresolved prerequisites

This is an evaluation order, not a claim that every item is a legal "higher priority" than every later item.

G. DERIVED RESULTS FOR THE REAL FIXTURE

G1 — August 6, 2026 at 2:00 PM

Inputs:

place:
  Lewis St between Broome and Delancey South

temporary advisory:
  no parking
  valid 2026-07-23 through 2026-08-07
  active 24/7

query time:
  2026-08-06 14:00

Derived:

TEMPORARY_RESTRICTION_ACTIVE = yes
ACTION_PARK = prohibited by captured temporary notice

Reader answer

NO — the City's temporary construction advisory places this segment under a 24/7 No Parking restriction through August 7. Confirm the posted street signs because the advisory itself says field conditions and schedules may change.

That last sentence is not boilerplate. It identifies the missing field-confirmation edge.

G2 — August 9, 2026 at 11:20 AM

Inputs:

same place

temporary advisory:
  end = 2026-08-07

query time:
  2026-08-09 11:20

Derived:

TEMPORARY_RESTRICTION_ACTIVE = no

But:

PERMANENT_SIGN_STACK = not yet captured for this dossier
CURRENT_FIELD_TEMPORARY_SIGNS = not observed
HYDRANT_GEOMETRY = not observed

Reader answer

The July 23–August 7 construction prohibition is no longer active by its stated time range. Counterpedia cannot yet tell you that parking is allowed: the permanent signs and current field conditions for this curb still have to be resolved.

State:

TEMPORARY_NO_PARKING = EXPIRED
FINAL_PERMISSION = UNKNOWN
REOPENING_REQUIREMENTS:
  - current permanent sign inventory
  - current on-street sign observation
  - relevant general constraints

This is the killer demo.

H. WHY-NOT SPECIMENS

Why not 1

“The construction notice expired Friday, so parking is legal Sunday.”

Refuse.

Expiry removes one restriction; it does not constitute positive permission.

Why not 2

“ASP is suspended, so parking is free everywhere.”

Refuse.

NYC explicitly says other posted rules remain in effect when ASP is suspended.

Why not 3

“The DOT map says it's legal, so the street sign doesn't matter.”

Refuse.

DOT/311 explicitly warns the online map may not reflect new or temporary changes and instructs users to follow posted signage.

Why not 4

“The street sweeper already passed, so I can park.”

Refuse.

NYC311 says ASP applies for the entire posted period even after a sweeper passes.

Why not 5

“The curb next to a hydrant isn't painted, so I'm outside the hydrant zone.”

Refuse.

NYC says the prohibition is within 15 feet of either side of a hydrant and painted curbs do not define the legal distance.

I. TEMPORAL-SUPERSESSION REVEAL

A normal knowledge page stores:

Lewis Street:
  No Parking

and becomes stale.

Counterpedia stores:

TemporaryRestriction T1
  place = Lewis segment
  starts = 2026-07-23
  ends = 2026-08-07
  schedule = 24/7
  reason = roadway restoration
  source = exact advisory edition

Then the statement:

T1 applies

is a deterministic function of valid_at.

No article rewrite is required at midnight.

This is:

temporal knowledge as computation, not editorial maintenance.

J. PHYSICAL-WORLD DISAGREEMENT

Suppose on August 9:

• the online advisory has expired;

• the permanent DOT dataset says ordinary curb rules;

• but a temporary No Parking sign is still physically posted.

NYC DOT acknowledges temporary construction signs are sometimes not removed when work ends.

Counterpedia should not collapse that to one state.

It should show:

scheduled administrative state:
  restriction expired

field observation:
  temporary sign still present

relationship:
  STATE_CONFLICT / FIELD_DIVERGENCE

reader:
  do not infer permission

That is a genuinely different kind of epistemic collision from the Twelve.

No one is lying. No scandal is required.

Two representations of the city are simply out of sync.

K. FIELD CAPTURE CONTRACT

This is the first Quiet Utility entry that benefits from operator/mobile observation.

A useful field observation would contain:

observation_kind:
  curb_sign_stack

observed_at:
  exact UTC + local offset

location:
  lat/lon
  accuracy_meters

orientation:
  street
  side_of_street
  facing direction

artifacts:
  photo_original[]
  optional short video

observed_objects:
  sign poles
  sign faces
  arrows
  hydrants
  meters
  temporary notices

operator_statement:
  NONE required

The image itself is an Artifact.

Interpretation occurs downstream.

A timestamped curb photograph should never become:

PARKING_LEGAL = true

at capture time.

It proves only what was visibly observed.

L. REVERSE-WIKIPEDIA VALUE

Open the ESCR advisory:

temporary No Parking notice
      ↓
exact segment
      ↓
valid interval
      ↓
Aug 6 applicability = active
      ↓
parking query result = NO

Change only valid_at:

same exact advisory
      ↓
Aug 9 applicability = expired
      ↓
temporary restriction contributes nothing
      ↓
base rules unresolved
      ↓
parking query = UNKNOWN

One captured source artifact supports two different temporal relationships without the source itself changing.

M. 30-SECOND DEMO

Screen:

Can I park here?

Map pin:

Lewis St between Broome St & Delancey St South

Time slider:

THU AUG 6 — 2:00 PM

NO PARKING

Why?
Temporary ESCR restriction
Jul 23 → Aug 7
24 hours/day

Drag slider to:

SUN AUG 9 — 11:20 AM

The red answer disappears.

Counterpedia does not replace it with green.

UNKNOWN

The construction restriction expired Aug 7.

Still needed:
○ permanent sign stack
○ current field observation
○ hydrant / curb geometry

Then capture a current curb photo.

The answer recompiles.

That is the product reveal:

Removing evidence for prohibition is not evidence of permission.

N. NEW QUIET-UTILITY PRIMITIVES

This fixture suggests research vocabulary candidates:

applicability
spatial_scope
temporal_scope
actor_scope
action_scope
temporary_override
suspension
exception
grace_period
field_observation
administrative_state
field_divergence
derived_permission
reopening_requirement

These are candidate vocabulary, not frozen global enums.

O. CAPTURE PRIORITY — CURB CAP1

P0

1. CURB-S02 exact ESCR advisory PDF

2. CURB-S01 current ESCR notice page

3. CURB-S03 exact current NYC parking-sign dataset slice for Lewis/Broome/Delancey block

4. CURB-S04 NYC311 Parking Signs and Rules

5. CURB-S05 2026 ASP suspension calendar

6. CURB-S06 ASP rule semantics

7. CURB-S12 exact current §4-08 rule bytes

8. FIELD-01 timestamped current sign-stack photo on the Lewis Street segment

P1

1. CURB-S08 DOT data/disclaimer page

2. CURB-S09 DDC temporary-restriction guidance

3. CURB-S10 temporary-sign lifecycle

4. relevant current meter blockface row if metered

5. hydrant / curb physical observation if applicable

P2

1. CURB-S11 Parking Summons Advocate conflict guidance

2. sign-design definitions / sign-code registry

3. historical sign inventory editions to show change history

P. CAPTURE / INGEST / DERIVATION

municipal sources
       ↓
CAP1-A web custody

field photo
       ↓
CAP1-A observation custody
       ↓
CAP1-B dagr-ingest
       ↓
sign / rule / time extraction
       ↓
SRC1
       ↓
rule propositions + spatial/temporal scopes
       ↓
ADJ1
       ↓
applicability engine
       ↓
DerivedPermission
       ↓
reader

SRS remains subject to the same actual emitter boundaries as the existing program.

No capture layer is allowed to declare parking legal.

Q. REGRESSION TESTS LEARNED FROM THIS FIXTURE

CURB-R1 — Expired prohibition does not imply permission

restriction_active = false is not parking_allowed = true.

CURB-R2 — Suspension is typed

ASP suspension removes ASP restrictions, not unrelated rules.

CURB-R3 — Time is operative input

Same curb + same sources + different valid_at can produce different applicability.

CURB-R4 — Digital inventory is not live physical state

The City itself warns temporary changes may not appear online.

CURB-R5 — Field observation is evidence, not legal adjudication

A photo proves visible signage at a time/place; a rule engine must still determine applicability.

CURB-R6 — One source can remain current while its rule is expired

A current webpage can still list an advisory whose own valid interval has ended.

CURB-R7 — Unknown is actionable

UNKNOWN — inspect current signs is more useful than a false green YES.

CURB-R8 — Physical and administrative states can diverge

Scheduled expiry + still-posted temporary sign must remain a conflict state.

R. PROVISIONAL THESIS

This Quiet Utility entry establishes:

Counterpedia can compile public rules into an answer that is specific to a place and time without confusing a database, a regulation, or a photograph with the final decision.

Its strongest public sentence is:

An expired “No Parking” rule does not mean “Parking Allowed.”

Its deeper architecture sentence is:

Permission is a derived relationship among a governed object, actor, action, location, valid time, active rules, exceptions, and observations.

And its quiet-corpus invariant is:

Rules become useful when Counterpedia can tell you not merely what they say, but when and where they actually apply.