> For the complete documentation index, see [llms.txt](https://housing-data-korea.gitbook.io/housing-data-korea-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://housing-data-korea.gitbook.io/housing-data-korea-docs/apttosell-housing-subscription/followup-event-registry-2026.md).

# 2026 Follow-Up Event Registry

The **AptToSell Follow-Up Event Registry 2026** is a published event-level dataset linking 103 South Korean apartment subscription projects in 2026 to their first observed follow-up supply notices.

It preserves stable AptToSell project IDs, official follow-up notice IDs, canonical official source URLs, first follow-up dates and explicit evidence grades.

## Published release

* Public version: **0.2**
* Publication date: **2026-10-06**
* Projects with follow-up supply observed: **103**
* First-event rows: **103**
* Stable AptToSell project-ID matches: **103 / 103**
* Official follow-up notice IDs: **103 / 103**
* Canonical official source links: **103 / 103**
* `PRIMARY_VERIFIED`: **13**
* `ID_CORROBORATED_SECONDARY`: **90**
* License: **CC BY 4.0**
* Zenodo DOI: **<https://doi.org/10.5281/zenodo.23176906>**

## Interpretation

A follow-up supply event means a later official supply notice was identified and linked to the initial project.

It must **not** be interpreted as a contract-failure rate, cancellation rate, or unsold-rate estimate.

## Evidence grades

* `PRIMARY_VERIFIED` — the event is supported by a directly inspected official project/public-agency artifact.
* `ID_CORROBORATED_SECONDARY` — the numeric official notice ID and canonical ApplyHome detail URL are retained, but the event artifact itself has not been promoted to direct-primary status.

Primary promotion is optional enrichment and does not change the published v0.2 cohort.

## Public files

* Publication-ready CSV: <https://raw.githubusercontent.com/cheer710815-hub/apttosell-subscription-data/main/datasets/followup-event-registry-2026/apttosell-followup-event-registry-public-v0.2.csv>
* Dataset repository: <https://github.com/cheer710815-hub/apttosell-subscription-data/tree/main/datasets/followup-event-registry-2026>
* Publication notes: <https://github.com/cheer710815-hub/apttosell-subscription-data/blob/main/datasets/followup-event-registry-2026/PUBLICATION-NOTES.md>
* Methodology: <https://github.com/cheer710815-hub/apttosell-subscription-data/blob/main/datasets/followup-event-registry-2026/METHODOLOGY.md>
* Data dictionary: <https://github.com/cheer710815-hub/apttosell-subscription-data/blob/main/datasets/followup-event-registry-2026/DATA-DICTIONARY.md>
* Schema.org Dataset metadata: <https://github.com/cheer710815-hub/apttosell-subscription-data/blob/main/datasets/followup-event-registry-2026/schemaorg-dataset.jsonld>

## Citation

> Kim, Eun. *AptToSell Follow-Up Event Registry 2026*, version 0.2, 2026-10-06. AptToSell. CC BY 4.0. <https://doi.org/10.5281/zenodo.23176906>

## Related analysis

The earlier competition/follow-up analysis remains available separately:

<https://doi.org/10.6084/m9.figshare.34064439>

The Zenodo DOI above is the preferred citation for the version-specific public event registry.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://housing-data-korea.gitbook.io/housing-data-korea-docs/apttosell-housing-subscription/followup-event-registry-2026.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.