# Technology-Induced Discovery Clustering — Open Research Handoff

## Purpose

This file is the durable continuation and publication record for the Technology-Induced Discovery Clustering (TIDC) research surface.

## Public posture

```text
posture: RESEARCH_NOTE
research_state: PILOT_NOT_CONFIRMATORY
site_role: public mirror, not proof authority
manual_user_action_required: false
```

Publication does not establish the clustering hypothesis as a historical law. Seed coding is revisable, missing dates remain explicit, and negative or contradictory evidence must be retained.

## Public surface

```text
page: technology-induced-discovery-clustering.html
machine_readable_ledger: data/tidc/pilot-events-v0.1.json
constraint_pressure_note: docs/TIDC_CONSTRAINT_PRESSURE_HYPOTHESIS.md
quantum_access_tracking_note: docs/TIDC_QUANTUM_ACCESS_INFLECTION_TRACKING.md
validator: scripts/check_tidc_publication.py
registry_claim: TIDC-OPEN-RESEARCH-001
```

## Research question

Do general-purpose problem-solving technologies produce delayed, learning-mediated clusters of mathematical and scientific discovery, and do later waves become increasingly capability-centered, overlapping, and verification-constrained?

## Current framework

The current publication draft distinguishes:

```text
candidate generation
verification
public disclosure
publication
disciplinary acceptance
later recognition
```

It also distinguishes:

```text
known problems becoming tractable
new problems becoming formulable
problems being solved or closed
```

The proposed discovery cycle is:

```text
availability
-> experimentation
-> self-capability research
-> technology-native methods
-> rapid discovery
-> saturation or overlap
```

## Access-inflection extension

A tracked precursor class has been added for infrastructure changes that may alter effective technology exposure without themselves constituting discoveries.

The first registered case is:

```text
case_id: QAI-2025-JP-OSAKA
date: 2025-07-28
class: access_infrastructure_inflection
wave: Quantum computing
posture: tracked precursor, not pilot discovery event
```

The relevant transition is:

```text
specialized device construction
-> remote access
-> wider experimentation
-> self-capability research
-> technology-native methods
-> external application discovery
```

The Osaka case combines domestically integrated hardware, cloud execution, browser-facing public interaction, and the open-source OQTOPUS operational stack. It is tracked because these conditions may jointly reduce access, learning, inspection, and experimentation barriers.

No discovery cluster is inferred from the launch. The event ledger remains unchanged until downstream mathematical, scientific, or independently verifiable capability results can be coded.

The provisional directional expression is:

```text
potential discovery-cluster intensity
~ (effective capability * accessibility * inspectability)
  / (learning cost * experimental cost)
```

This is a research expression, not an estimated law.

## Constraint-pressure extension

A conceptual extension has been added to test whether resource pressure moderates the transition from experimentation to technology-native method formation.

The proposed mechanism is:

```text
resource constraint intensity
-> architectural search pressure
-> efficiency-oriented innovation
-> competitive imitation and diffusion
-> new industry baseline
```

The initial directional model is an inverted-U relationship rather than a claim that constraint always improves innovation:

```text
I_a = beta_0 + beta_1 C_r + beta_2 C_r^2 + controls + epsilon

predicted initial signs:
beta_1 > 0
beta_2 < 0
```

Interpretation:

```text
low constraint: brute-force scaling may dominate
moderate constraint: architecture, algorithm, data, and infrastructure efficiency may intensify
extreme constraint: experimentation and verification may be suppressed
```

This mechanism remains untested. It must separate original research from transferred, licensed, open-weight, imitated, or distilled capability and must not use national labels as substitutes for laboratory-level evidence.

The governance boundary is explicit:

```text
compute scale != architectural efficiency
architectural efficiency != governed execution
benchmark capability != commit-time admissibility
low inference cost != reconstructable authority
accessibility != admissibility
open source != execution provenance
```

## Pilot Tranche 01

```text
events: 10
sources: 10
high_confidence: 7
medium_confidence: 3
external_events: 8
self_capability_events: 2
tracked_access_precursors: 1
```

Mechanisms represented:

```text
classical computer-assisted proof and exhaustive search
internet-mediated collective mathematics
AI-assisted candidate generation and verification
quantum self-capability benchmarking and characterization
```

## Current observations

1. The initial evidence separates exhaustive proof/search, networked collaboration, and candidate-generation-plus-verification as distinct mechanisms.
2. Publication dates are comparatively easy to establish; candidate-generation, verification, acceptance, and recognition dates are frequently missing or different.
3. Aggregate events must be split before confirmatory analysis, including Polymath8, AlphaTensor's multiple tensor improvements, and FunSearch's separate domains.
4. The selected quantum events are presently self-capability events, not broad external-application events.
5. The Osaka system is tracked as an access-layer precursor rather than coded as a discovery event.
6. Constraint pressure is registered as a candidate moderator, not an established explanation for national, institutional, or laboratory-level differences.
7. The next valid step is archival reconstruction and independent double coding, not statistical confirmation.

## Progressive release sequence

```text
Release 0: research opening and seed ledger        COMPLETE
Release 1: expanded event and source tranches      ACTIVE
Release 2: independent coding and disagreement     PENDING
Release 3: exploratory timelines and lag analysis  PENDING
Release 4: preregistered confirmatory protocol      PENDING
Release 5: confirmatory results and replication     PENDING
```

## Immediate research queue

```text
1. Retrieve original four-color theorem papers and computation records.
2. Split Polymath8 into dated subevents.
3. Add AlphaProof / AlphaGeometry and post-2024 AI-assisted research events from primary sources.
4. Add physical-to-logical quantum error-correction experiments.
5. Collect downstream adoption and output evidence for QAI-2025-JP-OSAKA.
6. Define laboratory-level resource-constraint and efficiency measures.
7. Separate original research from transferred, licensed, open-weight, imitated, and distilled capability.
8. Add access-exposure and constraint-exposure fields to future event tranches.
9. Test quadratic, threshold, spline, and regime-switching specifications.
10. Create a blinded second-coding packet.
11. Publish agreement, disagreements, and codebook revisions.
12. Add negative-control events, fields, and placebo dates.
```

## QAI-2025-JP-OSAKA longitudinal fields

Future evidence collection should attempt to establish:

```text
operational access date
public access date
hardware architecture and qubit count
user eligibility restrictions
browser, API, notebook, and local access modes
software source availability and component coverage
documentation and educational-material availability
registered users and institutions
executed jobs where available
external repositories, papers, patents, experiments, and applications
time to independently verifiable downstream results
self-capability versus external-application share over time
```

## Release gate

The next maturity transition is permitted only after an independent second coding pass.

The primary gate is coding reliability:

```text
Can independent coders identify the same event,
dates,
technology dependency,
exposure,
orientation,
constraint posture,
efficiency claim,
and acceptance posture
from the historical evidence?
```

The gate is not whether the hypothesis appears supported.

## Falsification posture

The framework must be weakened or rejected where reasonable specifications show:

- no reproducible clustering after general research growth is controlled;
- peaks preceding effective technology availability;
- no stable relationship between learning maturity and takeoff;
- no generation-versus-acceptance divergence under verification constraints;
- no decline in self-capability share as external applications mature;
- no field response to measured technology exposure;
- access-layer changes producing no measurable change in participation, experimentation, or downstream output;
- no relationship between problem-inventory balance and tapering or overlap;
- no increase in efficiency-oriented method formation under moderate resource pressure;
- innovation declining monotonically as constraint rises;
- apparent efficiency gains disappearing after transferred knowledge and distillation are controlled;
- nominally constrained laboratories having equivalent effective compute access;
- no relationship between constraint exposure and TIDC learning lags, wave intensity, tapering, or overlap;
- negative controls producing effects comparable to confirmatory estimates;
- process tracing showing supposedly necessary technology, access change, or constraint was incidental.

## Authority boundary

```text
research hypothesis != historical law
seed-coded event != validated event
tracked precursor != discovery event
public access claim != effective research access
publication date != candidate-generation date
citation count != discovery significance
model output != accepted knowledge
resource constraint != innovation proof
architectural efficiency != governed execution
open source != execution provenance
national label != laboratory-level evidence
Site display != proof
progressive publication != confirmation
```

## Continuation rule

Every future event tranche must:

1. append or version records rather than silently overwrite history;
2. retain uncertainty and open questions;
3. name primary sources wherever available;
4. identify superseded classifications;
5. publish negative and rejected cases;
6. update this handoff, the JSON ledger, validator, and public registry together.

Conceptual extensions that do not add or recode events must update the public page, this handoff, and a dedicated versioned research note. They must state explicitly that the event ledger is unchanged.

Tracked precursors must remain separate from discovery events until evidence establishes a codable result. Their downstream adoption and output measures should be collected longitudinally and negative findings retained.

## Latest change

```text
date: 2026-07-27
change: added quantum access-layer inflection tracking
new_file: docs/TIDC_QUANTUM_ACCESS_INFLECTION_TRACKING.md
tracked_case: QAI-2025-JP-OSAKA
public_page_updated: true
event_ledger_changed: false
reason: infrastructure and exposure precursor; no discovery event added or recoded
```
