REIT property history

REIT history is a reviewed publication matched to a building. It describes the REIT's interest,
which may cover only part of that building. Deployment alone does not publish a disclosure:
a publication must pass data review, source-use permission and building-match checks, then be
explicitly activated. An empty publications array means no accepted publication is available
for that building and requested surface.

Read an accepted publication

Surface	Access
Property page	Open the building's REIT tab, or add `?tab=reit` to its page URL
JSON API	`GET /japan/api/v1/assets/{id}/reit`
MCP	`get_asset_reit` with the building ID
Markdown twin	Request the building page with `Accept: text/markdown`
Financial CSV	`GET /japan/api/v1/assets/{id}/reit.csv`
JSON-LD	`GET /japan/api/v1/assets/{id}/reit.jsonld`

Publication IDs identify the same accepted snapshot across these surfaces. Each surface checks
its own current source-use permissions. These responses use Cache-Control: no-store.
Unknown buildings return 404; merged asset API IDs redirect to their survivor. A failed REIT
read is an error, not an empty publication. On the property page and Markdown twin, only the
REIT section becomes unavailable; the rest of the building remains usable.

Immutable evidence and publication agreement

The JSON/MCP envelope contains buildingId and publications. Each publication has id,
computedAt and a document with source revisions, current revision heads, periods, reviewed
building matches, financial checks and field citations. Private source-file locations are not
included. A citation points to the public source document and its locator.

New publications also include document.agreement, grouped by holding and period. Each field
has its path, agreement status, consensus value and original observations. An observation's
revisionId and path resolve to the immutable source revision and its field citations. Older
publications can omit this additive field.

Agreement status	Meaning
`agreed`	Multiple sources assert the same exact value and state
`singleSource`	One source asserts a value or state; the other observations are absent
`missing`	No source asserts a value or state
`conflict`	Sources assert different values or states
`unresolved`	At least one source observation has not been resolved

Only null and notRecorded abstain. notDisclosed, notApplicable and
outsideHoldingPeriod are explicit assertions. An unresolved observation is never converted to
missing or zero. Different trailing zeros can agree; overlapping rounding ranges alone cannot.
Derived values retain their formula version and input revision IDs. Agreement does not mean an
independent audit has been performed, and conflicts or unresolved agreement fields block release.

Amounts remain exact decimal strings in normalized base units. scale, decimals and rounding
on each source measure describe its published precision. Consensus values do not inherit a
source's precision. The property page shows one financial column per holding/period; open a
value to inspect all original observations, their precision, rounding and citations.

Financial CSV

CSV contains one row per metric, matched holding and period. value is the exact consensus
amount in base units. state preserves recorded, zero, derived and missing-state distinctions;
agreement reports the agreement status. Conflicts and unresolved projections have no numeric
consensus amount. Missing is never zero.

observations is a JSON array inside the quoted CSV cell. It retains each source's revision ID,
field path, original value with source precision/rounding, and citations. citations also collects
those field citations. Top-level scale, decimals and rounding are empty for every agreement status, including singleSource, because the publication
projection has no source precision. revisionId is populated only for a single observation.
formulaVersion and inputRevisionIds are populated for a derived consensus amount.
In the JSON schema, these fields are on the derived branch of ReitHistoryMeasure inside
ReitPublicRevision; the agreement field value preserves them as well.

CSV is a financial projection. JSON and Markdown also carry accepted transaction and ownership
records. Markdown and JSON-LD citations are scoped to holdings matched to the requested building;
JSON/MCP can retain wider accepted publication context. JSON-LD is a DataCatalog containing Dataset metadata with the publication ID, computation
time, building ID, source citations and a distribution link to the complete JSON. The endpoint
returns application/json; it does not duplicate the financial values. Read the JSON
distribution for values and observations.

Withdrawal and identity changes

Withdrawal removes the publication on subsequent reads. Source permission changes can remove
it from an affected surface. Changed building anchors can suspend the entire publication until
the building matches are reviewed again. Store the publication ID with exported values and
check the live response when current authorization matters.