Basis & Coordinate Table¶
Reference record — instantiates Coherent Linear Space Design
Fixes one basis and tabulates each element's coordinates and the meaning of each axis, turning abstract vectors into a readable, shareable record.
A vector space is an abstract object; you cannot email one. The Basis & Coordinate Table is the artifact that makes it concrete and shareable: it chooses one basis, records the space's dimension, lists every element's coordinates in that basis, and — the part people skip — annotates what each axis actually means and how it is normalized. Its distinguishing commitment is that it fixes a single frame of reference and writes down the resulting numbers, together with the standing reminder that those numbers are relative to that choice. It is not the sheet that declares the operations, and it is not the review that moves between frames; it is the ledger of "in this basis, here is where everything sits," which is what lets two people compare, store, and reconstruct elements without re-deriving the space each time.
Example¶
A print lab needs to communicate ink colors between its measurement rig and its designers. Each ink's true color is a reflectance spectrum sampled at hundreds of wavelengths — far too much to work with. The lab fixes a basis of three primaries and builds a coordinate table: every ink becomes three numbers, the dimension is recorded as 3, and each axis is annotated ("axis 1 ≈ long-wavelength primary weight," normalized so a perfect diffuser reads 1.0). Designers now compare inks by three coordinates instead of a spectrum. The table also carries an explicit caution born of its own semantics: because the basis has only three dimensions, two physically different spectra can collapse to the same three coordinates — they will look identical under one light and different under another. That is metamerism,[n1] and the table records that its coordinates are a lossy, basis-relative view, not the ink itself.
How it works¶
- Choose and freeze a basis. A standard basis, an orthonormal one, or a data-derived one (e.g., the top principal components) — but one, named and fixed.
- Record dimension. How many basis vectors, and therefore how many coordinates each element carries; note whether the basis spans the carrier or truncates it.
- Project and tabulate. Express each element as its coordinate tuple in the chosen basis and lay them out as rows.
- Annotate semantics. For each axis, what it represents, its units, and its normalization — so a reader knows whether coordinate
3.0means "three of something real" or an arbitrary scaling.
The result is a reference the whole team reads the same way; interpretation of what happens across bases is delegated to its sibling review.
Tuning parameters¶
- Basis choice — natural/standard (interpretable axes) versus data-derived like PCA (compact but abstract axes). More compactness usually costs interpretability.
- Dimension / truncation — how many basis vectors to keep. Truncating a high-dimensional element to a few coordinates saves space and noise but discards information (the metamerism trap).
- Normalization — unit-length axes, standardized scales, or raw. Normalization decides whether coordinate magnitudes are comparable across axes.
- Coordinate precision — decimals or significant figures recorded. Coarser rounding is portable but can make near-distinct elements collide.
When it helps, and when it misleads¶
Its strength is turning an abstract space into a shared, storable, human-readable record — the thing dashboards, databases, and reports actually consume, and the substrate every comparison runs on.
Its failure mode is that coordinates are not intrinsic: they are properties of the arbitrary basis, yet they read like properties of the element. The classic misuse is ranking axes by raw coordinate magnitude — "axis 2 is biggest, so it matters most" — when a different basis, or merely a different normalization, would reorder them entirely, and when a truncated basis has quietly thrown away the distinctions that mattered (metamerism again). The guarding discipline is to always record the basis and normalization alongside the numbers, flag any truncation as lossy, and defer every cross-basis claim to the Change-of-Basis Review, which is built to test what survives a change of frame.
How it implements the components¶
The table fills the archetype's record face — it captures a chosen frame and what its numbers mean:
basis_dimension_coordinate_record— its core content: the fixed basis, the dimension, and every element's coordinates.interpretive_coordinate_semantics— the per-axis annotations of meaning, units, and normalization that keep coordinates from being read as intrinsic.scalar_domain_specification— pins down which scalars the coordinates are drawn from (reals to N decimals, nonnegative reflectances), so the tabulated numbers are unambiguous.
It does not declare the carrier or the operations (the Vector-Space Specification Sheet), verify the axioms (the Linear-Axiom Verification Checklist), rule on admissible combinations (the Linear-Combination Membership Test), transform between frames (the Change-of-Basis Review), or register nonlinear exceptions (the Nonlinear-Boundary Stress Test).
Related¶
- Instantiates: Coherent Linear Space Design — the table is the concrete coordinate record the abstract space is read through.
- Consumes: Vector-Space Specification Sheet — a basis is only meaningful for a carrier and scalars that have already been declared.
- Sibling mechanisms: Vector-Space Specification Sheet · Linear-Axiom Verification Checklist · Linear-Combination Membership Test · Change-of-Basis Review · Zero-Span Linearity Check · Linear Embedding Diagnostics · Nonlinear-Boundary Stress Test
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: Fixes one basis and tabulates each element's coordinates and the meaning of each axis, turning abstract vectors into a readable, shareable record, making its operative form a non-executable information artifact that externalizes static or prospective structure.
Independent corroboration: The frozen evidence defines Basis & Coordinate Table as 'Fixes one basis and tabulates each element's coordinates and the meaning of each axis, turning abstract vectors into a readable, shareable record', so its operative form is Representation, Specification & Plan.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Mathematics
Origin pattern: Single lineage
Present-day reach: Specialized
Rationale: Linear algebra represents elements by coordinates relative to a declared basis and normalization convention.
Related originating lineages:
- Data Science & Analytics — Tabular feature representations annotate axes for shared interpretation.
- Physics — Physical coordinate systems make basis dependence operationally consequential.
Review resolution: Linear algebra is the agreed primary through basis-relative coordinates. Physics and data representations materially motivate the semantics and normalization fields; the named shared table artifact is an Encyclopedia packaging of those established ideas.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] Metamerism is the phenomenon where two objects with different reflectance spectra produce identical color coordinates under one illuminant but differ under another. It is the everyday face of a coordinate record being lossy and basis-relative: equal coordinates in a low-dimensional basis do not guarantee equal underlying elements. ↩