Vehicle record · Australia
BYD SEALION 6 Essential.
A trim-scoped evidence record.
This page records a deliberately narrow set of claims about the Essential trim offered in Australia. It begins with an admission artifact rather than a brochure summary, and it publishes only the measurements that passed that artifact’s entity, source, panel, qualifier, and evidence checks. The result is not intended to imitate a complete specification sheet. It is a traceable record in which absence is preferable to a value borrowed from another trim or inferred from an ambiguous label.
Admitted measurements
The complete numeric vehicle-fact set for this page.
These cells are the entire measurement allowlist. A missing range, dimension, mass, charging rate, consumption figure, output detail, or equipment count has not been replaced with a nearby number. It remains outside this record until its own scoped evidence passes admission.
Why does identity come before specification?
Why the visible tab label controls the record.
The reader-facing label is authoritative
The source interface presents a tab labelled Essential and connects that tab to a technical panel. This record follows that visible relationship. An internal panel identifier uses wording that could suggest another grade, but implementation names are not product identity. Treating an internal identifier as the trim name would contradict the label shown to a reader and would invite figures from the wrong configuration into this page. The admission therefore binds the visible label to the controlled panel and refuses to reinterpret the identifier.
No cross-trim pooling
A model page may place several variants close together, reuse components, and present shared promotional copy above their detailed panels. Proximity is not evidence that a value belongs to every variant. This page does not pool neighbouring columns, hero statements, or labels from another panel. Each published measurement must be located inside the panel controlled by the Essential tab. That boundary is stronger than visual similarity and prevents an attractive figure elsewhere on the source from becoming a claim about this trim.
The path carries the boundary
The trim appears in the address, title, heading, evidence entity, and record name. That repetition is intentional. A qualifier hidden in a footnote can disappear when text is quoted, indexed, or linked. A qualifier embedded across the record is harder to lose. Nothing here should be read as a specification for every SEALION model or for every grade sold in Australia. It is one market, one displayed trim, one bound panel, and one dated source capture.
How to read the three claims
Literal values with explicit unknowns.
Unknown is a useful qualifier
A numeric value can be exact while its basis remains unstated. The capacity row is an example: the literal is admitted, but the source does not identify the accounting convention behind it. This record preserves that separation. It does not silently choose a gross or usable interpretation, because either choice would add a fact the source did not provide. The null qualifier is not missing work; it is the machine-readable expression of a boundary in the evidence.
Maximum is retained, scope is not invented
The power label describes the published figure as a maximum, so the page keeps that word attached to the measurement. At the same time, the source row does not establish which component or combination defines the output. The record therefore avoids substituting terms such as motor output, engine output, or system output. A precise number with an unknown component boundary is more honest than a smooth sentence that quietly chooses one.
Conditions stay unstated
The acceleration row names its start and end speeds and supplies a duration. It does not provide the surrounding test protocol. Temperature, surface, state of charge, tyre state, payload, launch method, and measurement tolerance are not supplied by the admitted row. This page makes no claim about them and offers no prediction for an owner’s result. It reports the source literal within the source’s stated boundary, then stops.
No conversion layer
The record does not convert units, estimate related performance, derive ratios, or calculate a result from the admitted values. Derived numbers can look authoritative even when their assumptions are hidden. Here the display adds spacing between each value and unit for readability, but the underlying quantity is unchanged. Readers can inspect the evidence projection and find the same literals, units, null qualifiers, locators, and snapshot binding used to render the page.
What does this record not claim?
Boundaries are part of the publication.
Not a complete specification sheet
The source contains more material than this page publishes. That difference is deliberate. Range and efficiency claims can depend on test standards and operating modes. Dimensions and mass can depend on configuration. Charging claims can depend on equipment, state, and temperature. Equipment lists can vary by production or market timing. None of those categories becomes safer merely because a value is easy to see. They remain absent until admitted under an equally explicit entity and qualifier contract.
No commercial surface
This page contains no commercial amount, currency, offer, transaction term, or structured product payload. The omission is structural rather than cosmetic: the evidence projection has no monetary fields, the page has no commercial artifact, and the document emits no Product or Offer schema. A non-commercial admission cannot be stretched into a commercial conclusion. Any future commercial record would require its own authorization, evidence, review, and withdrawal path rather than an edit hidden inside this vehicle record.
No rejected observation notice
Material rejected for this entity is not repeated here as a warning badge or a tempting footnote. Repetition would still expose the unsupported value next to the Essential record and could cause it to be quoted without its rejection context. The safer publication rule is absence. The page explains the cross-trim boundary without reproducing any rejected numeric literal, and the evidence projection contains only admitted measurements and nonnumeric limitations.
A snapshot, not a live feed
The cited page may change after capture. Nothing is fetched when this record is viewed, and the builder has no network path. The page is regenerated only from the reviewed admission artifact, while the source address, observation date, snapshot digest, and row locators remain available in the evidence section. This design makes drift visible: a changed admission produces changed bytes, while the same admission produces the same bytes.
Evidence and reproducibility
The public record is bound to one reviewed artifact.
One deterministic input
The page builder reads the admission artifact and no captured source file. It validates the schema, admitted status, exact entity, source snapshot, panel binding, measurement count, values, units, qualifiers, provenance references, and policy boundary before rendering. If any required field is absent or changed, the build refuses instead of generating a partial page. This turns the artifact into a narrow publication interface rather than a bag of fields that a template may copy opportunistically.
Two emitted files
The builder can emit only this HTML document and its evidence projection. It cannot update the sitemap, release manifest, another vehicle page, a brand page, a market page, or a comparison surface. Those integrations are separate reviewed edits. The restricted writer set makes accidental scope expansion testable and keeps the page build from authorizing its own release. Rebuilding in check mode performs a byte comparison and writes nothing.
Machine-readable correspondence
The evidence projection repeats the entity key and carries one record with the three admitted measurements. Each measurement keeps its attribute, literal value, unit, exact qualifier map, source identity, snapshot digest, row locator, observation date, and decision references. The page does not create a second interpretation layer. Human-readable explanations describe the same unknowns that appear as null qualifiers in the evidence file.
Unindexed at birth
This candidate carries a noindex directive and a self-referencing canonical address. The canonical establishes the intended address; it does not authorize indexing, release, or deployment. The record remains a candidate in the manifest, and deployment is explicitly outside this build. Search visibility can be reconsidered only after the real page tree passes its release gates and a separate authorization is recorded.
Source and admission binding
- Source
- BYD Australia model page
- Observed
- 2026-09-22
- Snapshot SHA-256
- 53a5692b9863fe9e2685816eb227407ea502b307dcdd09de6fba124f21a449a2
- Admission artifact
metadata/SEALION6_ESSENTIAL_ADMISSION.json- Admission SHA-256
- 6be0b6c8c4ae27d96c869229e3a6ae997144a784d0bb0e7b8d5446f38c31c1fb
- Structured evidence
- evidence.json