Regulation · Object 360

Special Local Regulation; Lake Havasu, Lake Havasu City, AZ

Special Local Regulation; Lake Havasu, Lake Havasu City, AZ: a regulation cited by 9 reports, first seen 2026-10-28.

As of 2026-10-28 · 9 links

Signals

The operational read — at a glance.

Each signal traces to the surface that produced it.

Analytics

This object's own intelligence.

Fused from the shipped analytics libs — Heat, demand, reflexivity, evidence independence, track record.

Graph footprint

Reports reached 9 Verticals 0 Provenance edges 9

First seen 2026-10-28 · primary vertical software-ai.

Trace in the explorer →

Recommended actions

What to do next.

State-derived next moves — the hooks the decision ledger wires into.

Positions

Who's staked a decision here.

Analysts and agents record a typed stance on this object — the audit trail. The aggregate is public; the full theses are Pro.

0 pursuing 0 watching 0 passing
Take a position →

No positions recorded on this object yet — be the first to stake a falsifiable claim.

What changed

What moved on this object — and around it.

A factual digest of the append-only change ledger over the last 30 days. It reports what moved — not whether it helps or hurts a thesis.

hot

12 direct changes and 1971 nearby in the last 30 days — hot

Direct changes (12)

  • 2026-10-28 Special Local Regulation; Lake Havasu, Lake Havasu City, AZ: daysUntilEffective -7 → -8
  • 2026-10-27 Special Local Regulation; Lake Havasu, Lake Havasu City, AZ: daysUntilEffective -6 → -7
  • 2026-10-26 Special Local Regulation; Lake Havasu, Lake Havasu City, AZ: daysUntilEffective -5 → -6
  • 2026-10-25 Special Local Regulation; Lake Havasu, Lake Havasu City, AZ: daysUntilEffective -4 → -5
  • 2026-10-24 Special Local Regulation; Lake Havasu, Lake Havasu City, AZ: daysUntilEffective -3 → -4

Nearby in the vertical

  • 2026-10-28 playwright (npm): fourWeekGrowthPct -44.5 → -12.1
  • 2026-10-28 fastapi (pypi): fourWeekGrowthPct 31.5 → 28.1
  • 2026-10-28 Hacker News: ideaCount 65 → 66
  • 2026-10-28 monitor template: ideaCount 27 → 28
  • 2026-10-28 signal software: ideaCount 26 → 27
Full ledger →

Connections

Everything this node links to.

Each link carries its provenance — declared in the data, classified by algorithm, or inferred by overlap.

Mandated by (9)

Provenance trail

Every read traces to a surface.

No un-sourced claims — the audit trail that makes this operational, not decorative.

  • Reaches 9 reports across 0 verticals in the ontology graph /explore/
  • First observed 2026-10-28 /changes/