# LIquid Blog Parity Status

The LIquid blog parity reset is implemented in the shipped extension surface:

- public execution entrypoints:
  - `liquid.query(text)`
  - `liquid.query_as(text, text)`
  - `liquid.read_as(text, text)`
- LIquid program parsing with `.` assertions/rules and one terminal `?` query
- bare variables and `_`
- double-quoted string literals
- `Edge(...)`
- named compounds via `Type@(cid=..., role=...)`
- bootstrap schema through `liquid/type`, `liquid/cardinality`,
  `liquid/subject_meta`, `liquid/object_meta`, `liquid/compound_predicate`,
  and `liquid/mutable`
- query-local rule evaluation with tabular bindings returned in query-variable
  order
- first-class CLS policy compounds, inherited `liquid/acts_for` principal scope,
  and `Principal@(...)` metadata
- install and upgrade coverage for the shipped `0.1.0` surface

The extension also ships PostgreSQL-specific normalization helpers outside the
LIquid blog language itself:

- `liquid.create_row_normalizer(...)`
- `liquid.drop_row_normalizer(...)`
- `liquid.rebuild_row_normalizer(...)`

These are extension management APIs for projecting authoritative relational
tables into LIquid compounds through row triggers. They do not change the
LIquid query language.

Out of scope for the current extension:

- subgraph-return query mode
- public delete syntax beyond internal tombstones
- parallel custom scan execution