RECURRING SPATIAL TYPE / LIBRARY 0.11

Fixture Observation Tower Typology

Fictional typology used to test structure classification.

Explain recurring spatial or programmatic types through problem, organization, variation, examples, scale, geography, and time without treating one manifestation as universal.

definition

Definition & scope

Fictional typology used to test structure classification.

Development fixture proving that a typology can compare spatial problems, organization, variants, examples, and measurements without turning one example into a universal template.

Entity summary + explicit fixture source This development record demonstrates information architecture, not real-world subject matter.

spatial_problem

Recurring spatial problem

Typology analysis should state the recurring spatial or programmatic problem only when a source does.

No sourced spatial-problem assertions are attached to this fixture. APU011 keeps the section explicit instead of filling it from the entity name or one example.

organization

Organization

Plans, circulation, access, and sectional organization require explicit evidence.

No sourced organizational assertions are attached to this fixture. APU011 keeps the section explicit instead of filling it from the entity name or one example.

variants

Variants

Variants require multiple supported manifestations or a source-defined taxonomy.

No sourced variant assertions are attached to this fixture. APU011 keeps the section explicit instead of filling it from the entity name or one example.

examples

Manifestations

Graph-backed example

Fixture Observation Tower

Fictional tower used to exercise structure, chronology, measurements, and media references.

Manifested by · apu:rel:tower-typology

measurements

Scale & measurable fields

No normalized property values are emitted for this fixture. The system exposes comparison rules without inventing measurements.

Measurement / property policy

Dimension ranges

Value type: Measurement Range · Unit: source-defined

Only compare ranges normalized to the same definition and unit.

Capacity

Value type: Measurement · Unit: source-defined

Capacity requires a documented counting method.

Organizational pattern

Value type: Sourced Statements

Do not infer plan organization from the typology name.

geography

Geographic manifestations

Conceptual records do not receive a pin merely because an example has one. Geographic context is derived through explicit examples and validated city scope.

City Atlas via built example

Fixture Harbor City

Supported by 1 explicit example inside the city scope.

Open global Atlas →

chronology

Typology through time

No explicit APU Time evidence exists for this development fixture. No period is inferred from the name, example, or lifecycle state.

Open global Time →

boundaries

Boundaries & cautions

A typology is a comparison framework, not a claim that all examples share the same form.

Typical dimensions must never be fabricated from a single example.

Program names and typologies are not automatically interchangeable.

Open evidence questions

What recurring problem defines this type in sourced literature?
Which organizational variants are documented?
Which measurement definitions are comparable across examples?

provenance

Evidence & provenance

fixture

APU001 Synthetic Fixture Specification

Internal development-only source. All referenced entities are fictional and exist solely to validate data contracts.

apu:source:apu001-fixture-spec

media

Media & rights

No media is attached. APU011 does not generate visual evidence or infer appearance from names.

No additional Graph connections exist beyond the built-example relationship.

Open relationship graph foundation →

← Typologies index Architecture & Places home →