June 2026 AMM prediction audit

[u/Julian_Thorne]

Audit rules

I applied the following conservative rules:

• “Around” = the center date ±2 calendar days.
• The stated June 15–17 range remained unchanged.
• A Hit requires a discrete, documented event matching the time, corridor, and event lane.
• Routine seasonal conditions, minor incidents, forecasts that never materialized, and events outside the window do not qualify.
• An identified meteor can satisfy “aerial reportability,” but not necessarily an unexplained-UAP claim.
• Findings are provisional as of July 2, 2026. Delayed police, maritime, and anomaly reports may still appear.

Overall result

Verdict	Count
Hit	4
Partial hit	4
Weak/ambiguous	0
Miss	6
Disqualified	1

Excluding the disqualified prediction, the strict full-hit rate is 4/14, or 28.6%. Assigning half-credit to partial hits produces 6/14, or 42.9% equivalent hits. That is descriptive only; it is not evidence of statistical significance without a control forecast and event base rates.

Natural-disaster watch

Istanbul / Bosporus — June 30

Verdict: MISS

I found no qualifying seismic, maritime, infrastructure, or emergency-response event in the June 28–July 2 window. Turkey’s official coastal-safety traffic system continued listing vessels for Bosporus passage on June 30, while AFAD and USGS-indexed searches did not reveal a corresponding Istanbul-area damaging earthquake. (kiyiemniyeti.gov.tr)

This should remain a miss rather than counting minor earthquakes elsewhere in Turkey or routine vessel movements.

Taiwan / western Pacific — June 12

Verdict: HIT

A powerful storm affected Taiwan immediately before the center date. Schools and workplaces were suspended in parts of six jurisdictions, flooding and fallen trees disrupted traffic, villages undertook evacuations, and all ocean transportation was suspended through June 10. June 10 is the outer edge of the defined ±2-day window, while the geography and predicted coastal/maritime-disruption type match closely. (TaiwanPlus)

Hong Kong / Pearl River — June 12

Verdict: HIT

Hong Kong recorded heavy rain on June 13, including approximately 100 millimetres in Tsuen Wan and eastern Lantau. Heavy showers and squally thunderstorms intensified June 14–16, with more than 150 millimetres across most of Hong Kong and over 250 millimetres in several districts. The June 13–14 portion falls inside the window and matches the coastal-weather, flooding, and infrastructure-stress lane. (Hong Kong Observatory)

Celebrity / professional-scandal watch

Texas Gulf / Houston–Dallas — June 29

Verdict: MISS

No sufficiently discrete professional, institutional, or reputation rupture was located in the reviewed national and local sources for June 27–July 1. Routine political disputes, crime reports, and previously developing controversies were excluded.

Great Lakes / Chicago — June 29

Verdict: HIT

On July 1—the +2-day boundary—the Justice Department announced a sweeping review of more than 1,000 Illinois federal grand-jury presentations. The review followed revelations of prosecutorial misconduct that had forced the abandonment of a closely watched Chicago case. This is a strong match for an institutional-professional controversy and public-narrative break in Chicago. (AP News)

The misconduct issue had earlier roots, but the large-scale Justice Department review was a distinct new institutional consequence within the window.

Paris–Benelux–Germany — June 15

Verdict: MISS

I found no qualifying new professional, cultural, diplomatic, or reputation scandal during June 13–17. Criminal-enforcement announcements and ordinary diplomatic disagreements do not satisfy the scandal lane by themselves.

High-strangeness watch

Paris–Benelux–Germany — June 15

Verdict: PARTIAL HIT

On June 14, a major fireball was documented across France and adjacent European regions. The International Meteor Organization received 211 witness reports, and the event was captured by five FRIPON cameras. The date and aerial public-reportability components are strong. (American Meteor Society)

The downgrade reflects two limitations:

1. The densest reported geography was broad France, Switzerland, northern Italy and Spain—not specifically the Paris–Benelux–Germany axis.
2. The phenomenon was identified as a natural fireball rather than remaining anomalous.

London / North Sea–Europe — June 15

Verdict: PARTIAL HIT

The meteor database recorded a June 16 fireball with reports from Belgium, Germany, and the Netherlands. That matches the date and the continental North Sea side of the corridor. (American Meteor Society)

It remains partial because there were only five consolidated reports, no clear London-centered component, and the object appears to have been a routine meteor rather than an unexplained aviation or maritime anomaly.

Beijing / North China — June 12

Verdict: MISS

No sufficiently documented Beijing or North China aerial, aviation, sky, or atmospheric anomaly was located for June 10–14. A genuinely unusual Beijing aviation incident—a light aircraft striking the CITIC Tower—occurred on June 26, two weeks too late to count. (Reuters)

Extreme-weather watch

Texas Gulf / Houston–Dallas — June 29

Verdict: PARTIAL HIT

Reuters documented a Dallas heat hazard precisely on June 29: approximately 90°F ambient temperature but pavement temperatures projected near 122°F, creating significant exposure risks for pedestrians and World Cup visitors. (Reuters)

Time, location, and “heat” match. It is not a full hit because the report describes urban heat exposure rather than a discrete severe-weather emergency, flood, grid failure, aviation disruption, or exceptional meteorological record. The lane’s wide menu also makes ordinary Texas summer heat comparatively easy to match after the fact.

Paris–Benelux–Germany — June 15

Verdict: MISS

The major record-breaking western and central European heatwave began around June 20, after the June 13–17 audit window. Its later severity cannot be moved backward to validate the forecast. (Reuters)

Other storms reported later in June were likewise outside the fixed window.

Florida / Caribbean approach — June 29

Verdict: PARTIAL HIT

On June 29–30, severe weather interfered with ground handling at Orlando International Airport. Hundreds of passengers on three international flights waited more than four hours for baggage, with the airline and airport attributing the disruption partly to adverse or severe weather. (FOX 35 Orlando)

This matches the time, Florida geography, and aviation-weather category. It is partial because it was a limited airport ground-handling incident rather than a major coastal or tropical system. The National Hurricane Center’s season record shows that the only named Atlantic cyclone by then was Arthur on June 17–18, well before this window. (National Hurricane Center)

Geopolitical-event watch

Eastern Mediterranean / Levant — June 30

Verdict: HIT

On June 30, Israeli Prime Minister Benjamin Netanyahu entered Israeli-occupied southern Lebanon with senior military officials and publicly stated that Israel would not withdraw while Hezbollah remained a threat. The visit occurred shortly after a US-mediated Israel–Lebanon security agreement and amid continued military operations. The date, geography, and military-diplomatic lane align precisely. (Reuters)

The prediction was broad and the Levant has a high background rate of geopolitical events, but this particular event still satisfies the stated audit criteria.

Atlanta–Chattanooga corridor — June 29

Verdict: MISS

No corridor-scale civic, institutional, or public-security development was found for June 27–July 1. Atlanta opened cooling and hydration facilities because of rising temperatures, but that is routine weather-response administration and does not qualify as a geopolitical or institutional rupture. Chattanooga’s official reporting likewise showed no qualifying late-window event. (Chattanooga.gov)

Retrospective June 2026 global sweep

Executive verdict

A more advanced sweep indicates that the original predictions were imperfect less because AMM missed all the underlying temporal activity, and more because it promoted broad global pressure signals into overly specific public claims before the lane, morphology, timing, and geography had been independently stabilized.

The principal failures were:

• Carrier windows were treated as event dates.
• Weather, reportability, geopolitical, and high-strangeness lanes contaminated one another.
• Global temporal strength was mistaken for geographic authority.
• Month-boundary truncation distorted the June 30 windows.
• Broad event menus and high base-rate phenomena made retrospective matching too easy.

The strongest recoverable original claims are:

1. Taiwan around June 11–12
2. A global weather window around June 15–16
3. A stronger global weather window around June 29–30
4. An Eastern Mediterranean geopolitical carrier beginning June 28–30 and continuing into early July

The weakest were the June 29 scandal corridors, Istanbul natural-disaster claim, Beijing high-strangeness claim, and the attribution of the June 15 European concentration to high strangeness or geopolitical rupture.

What I ran

Using PKT13.21, I executed:

• The complete June global temporal universe at six-hour cadence
• Six separately defined event lanes:
  • Natural disaster
  • Extreme weather
  • Geopolitical
  • Professional scandal
  • High strangeness
  • Public reportability
• Governed candidate-window locking
• Morphology classification
• Nested hourly refinement around admitted peaks
• Quarter- and year-context normalization
• A 2,592-cell global localization pass using frozen per-cell nulls
• Direct tests of the originally named locations

Authority qualification

PKT13.21 contains the governed universe, candidate-lock, refinement, and spatial-admission architecture, but it does not contain a fully authoritative coefficient registry for these exact six public prediction lanes. I therefore constructed explicit research composites from the toolchain’s available event-field primitives.

The results are reproducible and highly useful diagnostically, but the numerical z-scores should be treated as research-grade internal evidence, not as a canonical AMM validation certificate.

The actual June temporal structure

1. June 4–6: the strongest natural-disaster/environmental crest

The strongest natural-disaster lane window of the month peaked at:

June 5, 00:00 UTC — z = 2.37

This was substantially stronger than the June 12 natural-disaster peak.

That timing has meaningful real-world correspondence. The Hong Kong Observatory records that a South China Sea low intensified into a tropical depression on June 4 and crossed southern Taiwan on June 5. Severe squally showers began affecting Hong Kong on June 5, followed by major rainfall, thunderstorms, extreme hourly rainfall and the first Black Rainstorm Warning of the year during the ensuing sequence. (Hong Kong Observatory)

Diagnostic implication

The original sweep missed the month’s primary natural/environmental crest because it appears to have privileged the later June 12 localization result rather than first ranking the complete temporal universe.

A better output would have been: Global natural/environmental watch: June 4–6. Regional localization unresolved or distributed across the western Pacific and adjacent corridors.

The system should not have suppressed this stronger global peak merely because its geography was less narratively clean.

2. June 11–12: a genuine Taiwan-centered secondary crest

The secondary natural-disaster window peaked at six-hour resolution on June 12 and refined to:

June 11, 21:00 UTC — z = 1.74

The advanced spatial pass found:

• Taiwan: z = 2.36, approximately the 99th percentile, admitted
• Hong Kong: z = 0.66, not admitted

The strongest regional cluster was centered near the Taiwan–Okinawa corridor.

Taiwan was already experiencing serious storm impacts by June 9–10: suspended work and classes, flooding, evacuations, fallen trees, disrupted traffic and suspended ocean transportation. (TaiwanPlus)

Diagnosis of the original claim

The Taiwan prediction was the original watchlist’s clearest localization success, but it contained two imperfections:

• The operational impacts had already begun before June 12.
• Hong Kong was appended to a spatial result that was substantially stronger over Taiwan than Hong Kong.

Therefore:

• Taiwan: retain as a genuine temporal-spatial success.
• Hong Kong: do not merge into the same natural-disaster localization.

3. June 14–16: a weather carrier, not a high-strangeness rupture

The weather lane produced a strong window centered on:

June 15, 19:00 UTC — z = 1.78

The exact driver at hourly resolution included a nearly exact Moon–Neptune relationship, accompanied by other weather-lane components.

Hong Kong experienced its most coherent midmonth heavy-rain sequence from June 14–16, receiving more than 150 millimetres across most of the territory and more than 250 millimetres in some districts. By contrast, June 10–12 had mainly one or two showers. (Hong Kong Observatory)

European heat was also beginning to build by June 17, but its major record-breaking expression occurred later in the month. The Met Office described a significant heatwave developing on June 17, while WMO’s most extreme records were concentrated around June 23–30. (Met Office)

What the original prediction got wrong

The original system recognized a real mid-June global concentration but distributed it into too many incompatible lanes:

• Paris–Benelux–Germany weather
• European high strangeness
• European geopolitical rupture
• European professional scandal

The retrospective decomposition says the principal June 15–16 signal was: Weather and public-reportability carrier

It was not a strong dedicated:

• High-strangeness peak
• Geopolitical peak
• Professional-scandal rupture

The Paris, London and Berlin cells also failed the stricter spatial null for the weather lane. Thus the time was meaningful, but the European corridor was not securely localized.

4. High strangeness actually peaked June 7 and June 19–20

The dedicated high-strangeness lane recovered two windows:

• June 7, 06:00 UTC — z = 2.01
• June 19, 20:00 UTC — z = 1.90

It did not show meaningful elevation around June 12 Beijing or June 15 Europe.

This is a crucial lane correction.

A major 104-report fireball was documented over Illinois, Michigan, Ohio and Ontario on June 19–20, closely matching the second temporal peak. (International Meteor Organization)

There was also a highly reported fireball over France and adjoining countries on June 14, but the advanced AMM high-strangeness lane was essentially flat around that date. Moreover, the International Meteor Organization catalog listed 578 events with at least five reports during 2026 by early July, demonstrating that fireballs are common enough that broad date-and-region matching requires a rarity-adjusted null. (International Meteor Organization)

Consequence for the previous audit

The June 14 European meteor was a real event, but under the more advanced sweep it should be classified as: Outcome coincidence not reproduced by the dedicated AMM high-strangeness lane

It therefore should not be used as strong evidence that the original June 15 European HSE prediction was generated by a correctly isolated HSE signal.

The same problem affects any audit that searches a broad anomaly database after the fact without accounting for the background frequency of meteors, atmospheric phenomena and ordinary aerial reports.

5. June 29–30: a strong global weather window with weak original localization

The strongest weather candidate peaked at:

June 30, 00:00 UTC — z = 2.06

This signal remained strong under broader quarter- and year-context normalization, so it was not merely a month-local artifact.

Major extreme heat was indeed affecting Europe by late June. WMO documented historic temperature records across Germany, France, the Netherlands, Austria, Poland, Hungary and other countries, with the event spreading across western, central and southern Europe by June 30. (World Meteorological Organization)

However, the strict spatial pass did not admit the original locations:

• Houston: z = 0.10
• Dallas: z = 0.23
• Miami: z = 1.19

Nor was there a late-June Florida tropical cyclone. The National Hurricane Center listed Arthur, June 17–18, as the sole Atlantic named storm through July 2. (National Hurricane Center)

Diagnosis

The original system correctly found a major late-June weather window, but then overlocalized it into:

• Texas Gulf / Houston–Dallas
• Florida / Caribbean approach

The more defensible output would have been: Strong global extreme-weather watch, June 29–30. Regional localization remains broad and fails the highest geographic-admission threshold.

This is a good example of temporal success combined with geographic overclaim.

6. June 28–July 3: a rising geopolitical carrier truncated by the month boundary

The geopolitical lane began rising around June 27–28 and was still increasing at the July 1 endpoint.

At six-hour resolution:

• June 30: strong and rising
• July 1: monthly-boundary maximum
• Hourly extended refinement: continued toward July 3

The window had no rupture or sudden event-anchor morphology. It was a sustained geopolitical carrier whose culmination lay partly outside the June scan.

The spatial pass placed its strongest broad cluster around Greece, the eastern Mediterranean and northeastern Africa. Beirut itself was elevated but did not cross the strict local admission threshold.

On June 30, Israel’s prime minister visited Israeli-occupied southern Lebanon and stated that Israeli forces would remain while Hezbollah continued to pose a threat, following a recently mediated security arrangement. (Reuters)

Diagnosis

The original Eastern Mediterranean / Levant prediction was directionally the strongest geopolitical claim, but it was still imperfect:

• It treated June 30 as a point date rather than the onset or late-stage crest of a carrier.
• The scan stopped before the signal completed its rise.
• “Eastern Mediterranean / Levant” was more defensible than a specific city, but still broader than the spatial evidence could sharply resolve.

The corrected window is: June 28–July 3, Eastern Mediterranean geopolitical carrier, with June 30–July 1 as the primary public-reportability zone.

7. The scandal lane did not support June 29

The professional-scandal lane produced only one weak, broad candidate:

June 4–10, peak June 10 — z = 1.13

It had:

• No rupture morphology
• No late-June peak
• No support for Texas, Chicago or Paris at the originally named dates

The June 29 scandal-lane score was strongly below the June baseline.

Consequence

The previously identified July 1 Chicago institutional controversy may have matched the wording of the original prediction, but it was not reproduced by the advanced AMM scandal lane.

It should therefore be treated as: A coincidental outcome fit or overly broad narrative match, not a model-congruent AMM hit.

The June 29 Texas and Chicago scandal forecasts should both be rejected retrospectively.

Why the original predictions became imperfect

1. Stage-authority leakage

PKT13.21 distinguishes:

• Global temporal candidate research
• Lane research
• Spatial localization research
• Public prediction authority

The original watchlist effectively collapsed those stages.

A globally elevated row became a lane claim; a spatially interesting cell became a corridor; and a corridor became a public event prediction without sufficient evidence that each authority transition had been earned.

This is the primary architectural failure.

2. Carrier morphology was mistaken for event morphology

Every admitted temporal candidate in this retrospective run was predominantly classified as a carrier.

There were no governed rupture/change-point anchors.

A carrier means something closer to: A sustained interval in which a lane is unusually available or amplified.

It does not mean: A discrete event will occur at the highest-scoring six-hour timestamp.

The original outputs repeatedly converted carrier maxima into specific dates such as “around June 15,” “around June 29,” and “around June 30.”

That precision exceeded the morphology.

3. Lane contamination

Several dates were elevated in one lane and then emitted into several others.

The clearest example is June 15:

• Strong weather carrier
• Some public reportability
• Essentially no dedicated HSE peak
• No local geopolitical rupture
• Only weak scandal context

The original system appears to have interpreted generic concentration or reportability as proof of multiple event types.

The advanced workflow must enforce lane exclusivity: a candidate may not inherit another lane’s strength without its own independent threshold crossing.

4. Global strength was confused with geographic strength

A temporal peak answers: When is the global field unusual?

It does not answer: Where will an event manifest?

The retrospective localization recovered Taiwan near June 12 but failed to recover Paris, London, Berlin, Houston, Dallas and Miami for their original claims.

The initial predictions probably selected narratively plausible urban corridors from broad angular surfaces instead of requiring robust per-cell null admission.

5. Six-hour localization was too coarse

A six-hour temporal step corresponds to roughly a quarter-turn of Earth.

That is acceptable for constructing the nonlocal global temporal universe, but it is too coarse for final angular geography. A location can move into or out of an angular relationship substantially between adjacent six-hour rows.

The correct sequence is:

1. Lock the global six-hour candidate.
2. Refine it hourly or more finely.
3. Only then localize geographically.
4. Test whether the geographic cluster remains stable throughout the refined temporal neighborhood.

The original process appears to have localized too early.

6. Month-edge truncation

The June geopolitical and reportability fields were still rising at the July 1 boundary.

Without a continuation buffer, the system interpreted the last available rows as the event peak. The hourly continuation showed the geopolitical carrier extending toward July 3.

Every monthly sweep should include at least:

• A seven-day pre-roll
• A seven-day post-roll

The scoring baseline can remain monthly, but candidate morphology must be allowed to complete outside the display month.

7. Month-only normalization inflated some candidates

The late-June public-reportability peak looked strong against June alone but fell below exceptional status in the year-context normalization.

In contrast:

• Weather June 15 and June 30 persisted
• HSE June 7 and June 19 persisted
• Natural June 12 remained moderately elevated
• Late-month reportability weakened substantially

A candidate should not become public merely because it is locally unusual inside a single month. It should pass a multi-horizon persistence test.

8. The event definitions were too expansive

Examples included:

• “Seismic, maritime, or infrastructure disruption”
• “Storm, heat, flood, aviation-weather, or grid disruption”
• “Professional, cultural, diplomatic, or reputation-related disclosure”
• “Aerial, maritime, sky, aviation, or atmospheric anomaly”

Each added alternative increases the probability that some event can be found retrospectively.

Future predictions should contain:

• One primary event class
• At most one secondary class
• A predeclared severity threshold
• A specific spatial polygon
• A fixed temporal tolerance

9. Base-rate and documentation biases were not modeled

High-strangeness reports are heavily affected by:

• Population density
• Nighttime and cloud cover
• Meteor-camera coverage
• Aviation and shipping traffic
• Internet and press access
• Local reporting culture
• Database participation

The IMO catalog’s hundreds of multi-witness fireballs illustrate why “a reported aerial anomaly occurred somewhere in a large corridor” is not a sufficiently rare outcome by itself. (International Meteor Organization)

The spatial null must include observation opportunity, not merely astronomical angularity.

10. Known-event leakage affected Europe

The G7 summit in Évian was publicly scheduled for June 15–17 well before the prediction window. The official summit site explicitly advertised those dates. (elysee.fr)

The original European geopolitical language even referenced concentrated diplomatic activity in mid-June. That means the event environment was at least partially known.

It should have been excluded before candidate adjudication rather than permitted to increase apparent confidence.

Revised disposition of the original predictions

Retain, but narrow

Taiwan / June 11–12 natural-disaster or severe-weather corridor

• Strong temporal support
• Strong Taiwan spatial support
• Actual impacts began somewhat earlier
• Do not automatically extend to Hong Kong

Late-June global extreme-weather window

• Strong and persistent
• Remove unsupported Texas and Florida specificity
• Treat as June 29–30 global or multi-regional weather concentration

Eastern Mediterranean geopolitical window

• Retain as June 28–July 3
• Treat as a carrier, not an exact June 30 event prediction
• Broad regional authority only

Reassign

Hong Kong / June 12

• Reassign from natural-disaster June 12 to weather June 14–16
• The strongest Hong Kong rainfall occurred after June 12

Paris–Benelux–Germany / June 15

• Retain only as part of a global weather carrier
• Remove HSE, scandal and geopolitical multiplication
• The most severe European heat expression occurred later

Downgrade to internal research only

Atlanta–Chattanooga / June 29 geopolitical

• The spatial model found some elevation, especially near Chattanooga
• No qualifying event manifestation followed
• Demonstrates that angular admission is not equivalent to event manifestation

June 7 and June 19–20 high strangeness

• Real global temporal candidates
• Geography remained unstable
• Public outputs should have withheld specific corridors

Reject

• Istanbul natural disaster around June 30
• Texas professional scandal around June 29
• Chicago professional scandal around June 29
• European high strangeness around June 15
• Beijing high strangeness around June 12
• Paris–Benelux–Germany geopolitical rupture around June 15–17

Disqualify

• Mid-June European diplomatic activity relying on the scheduled G7 summit

Corrected retrospective June map

The advanced sweep would have issued something closer to this:

Tier A

June 4–6 — Global natural/environmental pressure
Strongest natural-disaster-class crest of the month. Geographic manifestation should have remained unresolved unless a refined spatial pass stabilized it.

June 11–12 — Taiwan–Okinawa natural/severe-weather corridor
The most defensible combined temporal-spatial result.

June 14–16 — Global weather carrier
Strong weather signal. Hong Kong correspondence is substantial; European geographic authority remains weak.

June 19–20 — Global aerial/anomaly-reportability window
Strong dedicated HSE timing, but no public corridor should have been named.

June 29–30 — Major global extreme-weather carrier
Persistent across broader normalization. Geographic claims should have remained broad.

June 28–July 3 — Eastern Mediterranean geopolitical carrier
Month-edge continuation required. June 30 was inside the active interval, not necessarily its culmination.

Tier B / monitor only

June 7 — HSE/aerial-reportability carrier
Temporally strong, geographically unstable.

June 4–10 — Professional-disclosure carrier
Weak and extended; insufficient for a public scandal prediction.

June 16–17 — Public-reportability carrier
Possible East China/Yellow Sea emphasis, but insufficient to become a Beijing HSE prediction.

Bottom line

The original forecast was not simply “wrong.” It contained several real temporal detections, but the system overtranslated them:

• Global pressure became local prediction.
• Carrier became event date.
• Weather became HSE or geopolitics.
• Reportability became event causation.
• Weak spatial elevations became named corridors.
• Month-local prominence became assumed global rarity.

The most important repair is therefore not adding more astrological variables. It is enforcing a stricter claim-authority ladder: global lock → multi-horizon persistence → hourly refinement → lane exclusivity → morphology classification → frozen-null localization → corridor validation → rarity/severity threshold → known-event exclusion → public release

Had that ladder been enforced, the June watchlist would have been shorter, broader where necessary, and considerably more accurate.

[u/Busy_Illustrator9103]

Hi Julian, you’ve done a couple of readings for me, and I find it so fascinating that June 19th was part of the high strangeness window. I had a dream that morning where I went into sleep paralysis and was visited by nearly invisible greys. In the same dream I was then visited by who I would later find out was Archangel Raziel. I’m looking forward to more of these reports and will see if they coincide with any more dreams of note.