@metaobjectsdev/sdk 0.15.18 → 0.15.19-rc.1

package/LICENSE

@@ -1,3 +1,4 @@
+
                                  Apache License
                            Version 2.0, January 2004
                         http://www.apache.org/licenses/
@@ -32,33 +33,36 @@
       not limited to compiled object code, generated documentation,
       and conversions to other media types.
 
-      "Work" shall mean the work of authorship made available under
-      the License, as indicated by a copyright notice that is included in
-      or attached to the work (an example is provided in the Appendix below).
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
 
       "Derivative Works" shall mean any work, whether in Source or Object
       form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other transformations
+      editorial revisions, annotations, elaborations, or other modifications
       represent, as a whole, an original work of authorship. For the purposes
       of this License, Derivative Works shall not include works that remain
       separable from, or merely link (or bind by name) to the interfaces of,
       the Work and Derivative Works thereof.
 
-      "Contribution" shall mean, as submitted to the Licensor for inclusion
-      in the Work by the copyright owner or by an individual or Legal Entity
-      authorized to submit on behalf of the copyright owner. For the purposes
-      of this definition, "submitted" means any form of electronic, verbal,
-      or written communication sent to the Licensor or its representatives,
-      including but not limited to communication on electronic mailing lists,
-      source code control systems, and issue tracking systems that are managed
-      by, or on behalf of, the Licensor for the purpose of recording and
-      discussing modifications to the Work, but excluding communication that
-      is conspicuously marked or designated in writing by the copyright owner
-      as "Not a Contribution."
-
-      "Contributor" shall mean Licensor and any Legal Entity on behalf of
-      whom a Contribution has been received by the Licensor and included
-      within the Work.
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
 
    2. Grant of Copyright License. Subject to the terms and conditions of
       this License, each Contributor hereby grants to You a perpetual,
@@ -74,22 +78,22 @@
       use, offer to sell, sell, import, and otherwise transfer the Work,
       where such license applies only to those patent claims licensable
       by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by the combination of their Contribution(s)
+      Contribution(s) alone or by combination of their Contribution(s)
       with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a cross-claim
-      or counterclaim in a lawsuit) alleging that the Work or any
-      Contribution embodied within the Work constitutes direct or contributory
-      patent infringement, then any patent licenses granted to You under
-      this License for that Work shall terminate as of the date such
-      litigation is filed.
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
 
    4. Redistribution. You may reproduce and distribute copies of the
       Work or Derivative Works thereof in any medium, with or without
       modifications, and in Source or Object form, provided that You
       meet the following conditions:
 
-      (a) You must give any other recipients of the Work or Derivative
-          Works a copy of this License; and
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
 
       (b) You must cause any modified files to carry prominent notices
           stating that You changed the files; and
@@ -101,24 +105,28 @@
           the Derivative Works; and
 
       (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, You must include a readable copy of the
-          attribution notices contained within such NOTICE file, in
-          at least one of the following places: within a NOTICE text
-          file distributed as part of the Derivative Works; within
-          the Source form or documentation, if provided along with the
-          Derivative Works; or, within a display generated by the
-          Derivative Works, if and wherever such third-party notices
-          normally appear. The contents of the NOTICE file are for
-          informational purposes only and do not modify the License.
-          You may add Your own attribution notices within Derivative
-          Works that You distribute, alongside or in addition to the
-          NOTICE text from the Work, provided that such additional
-          attribution notices cannot be construed as modifying the License.
-
-      You may add Your own license statement for Your modifications and
-      may provide additional grant of rights to use, reproduce, modify,
-      prepare derivative works of, distribute, and sublicense such modifications,
-      as an additional requirement of this License.
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
 
    5. Submission of Contributions. Unless You explicitly state otherwise,
       any Contribution intentionally submitted for inclusion in the Work
@@ -137,10 +145,10 @@
       agreed to in writing, Licensor provides the Work (and each
       Contributor provides its Contributions) on an "AS IS" BASIS,
       WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any conditions of TITLE,
-      NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR
-      PURPOSE. You are solely responsible for determining the
-      appropriateness of using or reproducing the Work and assume any
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
       risks associated with Your exercise of permissions under this License.
 
    8. Limitation of Liability. In no event and under no legal theory,
@@ -148,20 +156,23 @@
       unless required by applicable law (such as deliberate and grossly
       negligent acts) or agreed to in writing, shall any Contributor be
       liable to You for damages, including any direct, indirect, special,
-      incidental, or exemplary damages of any character arising as a
+      incidental, or consequential damages of any character arising as a
       result of this License or out of the use or inability to use the
       Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or all other
-      commercial damages or losses), even if such Contributor has been
-      advised of the possibility of such damages.
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
 
    9. Accepting Warranty or Additional Liability. While redistributing
       the Work or Derivative Works thereof, You may choose to offer,
       and charge a fee for, acceptance of support, warranty, indemnity,
       or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may offer
-      only obligations consistent to this License provided that the
-      obligations are consistent with this License.
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
 
    END OF TERMS AND CONDITIONS
 
@@ -171,19 +182,21 @@
       boilerplate notice, with the fields enclosed by brackets "[]"
       replaced with your own identifying information. (Don't include
       the brackets!)  The text should be enclosed in the appropriate
-      comment syntax for the file format in question. Also add information
-      on how to contact you electronically and/or by mail.
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
 
-      Copyright 2026 MetaObjects Contributors
+   Copyright 2026 MetaObjects Contributors
 
-      Licensed under the Apache License, Version 2.0 (the "License");
-      you may not use this file except in compliance with the License.
-      You may obtain a copy of the License at
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
 
-          http://www.apache.org/licenses/LICENSE-2.0
+       http://www.apache.org/licenses/LICENSE-2.0
 
-      Unless required by applicable law or agreed to in writing, software
-      distributed under the License is distributed on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-      See the License for the specific language governing permissions and
-      limitations under the License.
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/agent-context/skills/metaobjects-audit/SKILL.md

@@ -189,6 +189,43 @@ emits two distinct finders (named by the FK field) automatically — no annotati
 reverse finder is a **codegen feature, not an attribute** (there is no reverse-nav `@`-attr
 to author). Advisory severity — a modernization opportunity, not a failing finding.
 
+**New-vocabulary OPPORTUNITY (the inverse hunt — advisory).** The checks above audit
+custom vocabulary the adopter *already* registered; this one hunts where the app
+**should** register vocabulary but hand-coded the pattern instead. Smells
+(grep-then-verify; require a *recurring, closed* set — never flag a one-off):
+- **N parallel hand-written integration modules** sharing a payload shape and a config
+  pattern (a closed set of channels / providers / export targets, each a near-copy with
+  a different transport) → candidate for ONE project-registered subtype whose variants
+  sit behind a closed structural-variant discriminator (the `source.rdb` `@kind`
+  pattern), plus a small owned generator emitting the per-variant wiring.
+- **An ad-hoc string discriminator steering code switches** — a string column whose
+  values select per-variant behavior/config scattered across the codebase. If the values
+  are just a closed symbol set, that is `field.enum` (`@values`), NOT new vocabulary. It
+  earns a subtype only when the discriminated concept **owns behavior or attributes of
+  its own** (ADR-0037 step 2a).
+- **A provider-shaped pattern re-implemented per instance** — repeated registration /
+  config blocks restating a shape one declared node per instance could carry, with codegen
+  emitting the repetition.
+- **A downstream integration modeled entirely in code** (an outbound webhook / notifier /
+  queue publisher / tool wiring beyond `template.toolcall`) where registered vocabulary +
+  a small generator would own the payload wiring, the names-only fail-closed config check,
+  and drift detection.
+
+Run the **ADR-0037 ordered test** before proposing: derivable → derive; differs from an
+existing subtype only by a property → an attribute; a plain validated value → an
+attribute; one-off author-supplied properties → the `attr.properties` bag. Only a concept
+with its own behavior/attributes earns a subtype, and transport/protocol is never the
+subtype axis (keep the node protocol- and address-free; variants behind the discriminator).
+**Converge before inventing** — check shipped vocabulary AND the planned/chartered names
+(see CALIBRATION "planned, not shipped"); never claim a chartered name for a project-local
+type. **Recommendation:** propose a project-registered provider (explicit loader wiring,
+ADR-0023 — never a loosened `strict` free-ride), a `metadata_sketch` of the node, and the
+owned generator that retires the duplication; a second independent consumer needing the
+same concept is a consumer→core promotion candidate (ADR-0011 — file an upstream issue).
+**Verdict: VOCAB CANDIDATE (advisory)** — a modeling opportunity, never a failing finding,
+never a tier gate; bias to under-flagging (the >15% false-positive kill criterion applies
+with full force). Full guidance: `docs/features/downstream-metadata-decisions.md`.
+
 ---
 
 ## Classification scheme (every surface; classify on codegen AND runtime)
@@ -200,7 +237,8 @@ to author). Advisory severity — a modernization opportunity, not a failing fin
 | **CODEGEN CANDIDATE (high)** | Standard CRUD/list/form over a modeled or modelable entity. | Author the view + generate; parity-gate. |
 | **CODEGEN CANDIDATE (partial)** | Generatable data layer, bespoke presentation. | Generate data layer; keep viz hand-written. |
 | **DYNAMIC-RUNTIME CANDIDATE** | Behavior that could be metadata-driven at runtime. | Assess runtime-metadata feasibility. |
-| **BESPOKE (keep)** | Genuine custom: aggregations, graph, SSE, auth, search, viz. | Leave hand-written — still import generated types. |
+| **BESPOKE (keep)** | Genuine custom: irreducible SQL (recursive CTEs, window functions, set ops — NOT plain count/sum/avg rollups, which are `origin.aggregate` on a projection), graph, SSE, auth, search, viz. | Leave hand-written — still import generated types. |
+| **VOCAB CANDIDATE (advisory)** | A recurring, closed hand-coded pattern (parallel integration modules / an ad-hoc string discriminator) that project-registered vocabulary — a custom subtype/attr via a provider — plus a small owned generator would own. | Propose the provider + `metadata_sketch`; apply the ADR-0037 ordered test; advisory only. |
 
 **Gold-standard exception.** A hand-written component that *derives* from generated metadata
 cannot drift — flag as good. A "bespoke" component hardcoding a shape metadata knows is a
@@ -220,6 +258,10 @@ Per finding: `file:line` → what → generated-equivalent exists? → recommend
 5. **Runtime schema patching** (`ALTER TABLE … ADD COLUMN IF NOT EXISTS`, `_ensure_schema()`) — N schema owners.
 6. **N declarations of one shape** — same entity as Drizzle table + Zod schema + Pydantic model + hand dataclass; target is 1 + N generated.
 7. **`own*()` accessor read of an effective property** (ADR-0039) — `ownAttr` / `ownFields` / `own_children` / bare Python `attr(` / `getMetaAttr(name, false)` / native `IsArray` used to read a value or iterate members outside the sanctioned subclass-emit / own-serializer / `@dbColumnType` cases → silently drops `extends`-inherited values. A **correctness defect** (axis G2), not advisory.
+8. **Hand-written `CREATE VIEW` / read-only SQL standing in for a projection (view-necessity test).** Grep migrations, checked-in `.sql`, and repository/query code for `CREATE [OR REPLACE] [MATERIALIZED] VIEW`, and for hand-rolled read-only queries that mirror a read model — a pure-`SELECT` repository/service method with joins or `GROUP BY` feeding a DTO, or a raw-SQL escape (`db.execute(sql…)`, `FromSqlRaw`, a JPA @Query with hand-written SQL). For each, run the **necessity test** — can `object.projection` + origins express this shape? It can when every output column is (a) a base-entity or relationship-joined column → `origin.passthrough` (`@from` / `@via`), (b) a count/sum/avg/min/max over related rows → `origin.aggregate` (`@agg` / `@of` / `@via`, optionally row-scoped with `@filter`), (c) a child collection → `origin.collection` (`@via`), or (d) a column borrowed via `extends` — and the joins follow declared relationships / `identity.reference` FKs.
+   - **Expressible → CODEGEN CANDIDATE (high):** convert to an `object.projection` with a read-only `source.rdb` `@kind: view` child, let `meta migrate` emit the `CREATE VIEW`, and consume the generated read-only query — the hand-written view is a second source of truth for a derivable shape. Flag in the finding that **`meta verify --db` cannot catch this**: an unmodeled DB view is *unmanaged*, so this audit is the only gate that sees it. Parity-gate: the generated view returns row-identical results before the hand-written SQL is deleted.
+   - **Not expressible → BESPOKE (keep), with a NAMED justification:** record the construct that makes it irreducible (recursive CTE, window function / `OVER`, `UNION` / `INTERSECT` / `EXCEPT`, `DISTINCT ON`, lateral join, non-aggregate expression column). "It's an aggregation" is NOT a justification — plain count/sum/avg/min/max rollups are `origin.aggregate`.
+9. **A closed variant-set hand-modeled per instance** — N sibling modules / classes / config blocks, one per channel / provider / target, sharing a payload + config shape and diverging only by transport. Grep for sibling-file families and switch-on-a-string dispatch; verify the set is closed and recurring (never a one-off). → axis I "New-vocabulary OPPORTUNITY" (VOCAB CANDIDATE, advisory).
 
 ---
 
@@ -238,6 +280,10 @@ Per finding: `file:line` → what → generated-equivalent exists? → recommend
   own + customize / author a template-spec / fix upstream / stopgap.
 - **Verify the DB artifact, not just the types** — computed view columns may appear in the
   contract but be dropped from the view DDL; the contract may lie.
+- **A hand-authored DB view is invisible to `meta verify --db`.** An unmodeled view is
+  *unmanaged* (informational only — never actionable drift, never auto-dropped), so a
+  hand-written view standing in for an expressible `object.projection` can never be
+  outsourced to the drift gate; hunt it here (drift signature 8, below).
 - **Version skew:** check *actually-resolved* package versions, not declared; consuming a fix
   requires a coordinated lockstep bump, not a source-file copy.
 

package/agent-context/skills/metaobjects-audit/references/capability-checklist.md

@@ -63,7 +63,13 @@ classify it (using the classification scheme in `SKILL.md`) and route the cutove
 - **`source.rdb`** (`@table`, `@schema`) — hunt hard-coded physical table/schema names that
   diverge from the default naming the source models.
 - **`@kind` = `view` / `materializedView`** — hunt hand-written SQL views where an authored
-  projection source (read-only `@kind`) belongs.
+  projection source (read-only `@kind`) belongs. Apply the **view-necessity test** (SKILL.md,
+  drift signature 8): a hand-written `CREATE VIEW` (or read-only SQL mirroring a read model) is a
+  CODEGEN CANDIDATE when its shape is expressible via `origin.passthrough` / `origin.aggregate` /
+  `origin.collection` + `extends` — convert it to an `object.projection` so `meta migrate` emits
+  the view DDL. It is BESPOKE-keep only when a NAMED irreducible construct (recursive CTE, window
+  function, set op) blocks projection authoring. `meta verify --db` can't see an unmodeled view,
+  so this is audit-only.
 - **`@kind` = `storedProc` / `tableFunction`** (`@parameterRef`) — hunt hand-called procs /
   table functions that a modeled callable source with `@parameterRef` already describes.
 - **`@role` = `primary`** (multi-source write-through) — hunt manual CQRS / write-through
@@ -157,6 +163,12 @@ classify it (using the classification scheme in `SKILL.md`) and route the cutove
 - **`attr.class`** — binding facet (`field.class` binding); hunt hand-wired type-binding
   facets. (`attr.base`, `attr.string`, `attr.int`, `attr.long`, `attr.double`, `attr.boolean`
   are the value-type primitives behind typed attrs — not direct audit targets.)
+- **Custom-provider extension point** (`attr.properties` is the one-off escape hatch;
+  `template.toolcall` is the historical register→extend precedent) — hunt a *recurring,
+  closed* variant set hand-coded as parallel modules (channels / providers / export targets)
+  that a project-registered subtype with a closed variant discriminator + a small owned
+  generator would own. Apply the ADR-0037 ordered test before proposing; advisory (VOCAB
+  CANDIDATE); see SKILL.md axis I "New-vocabulary OPPORTUNITY".
 
 ## Common documentation attrs (any node)
 

package/agent-context/skills/metaobjects-authoring/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: metaobjects-authoring
-description: Use when authoring or modifying MetaObjects metadata — fields, entities, relationships, sources, enums, abstracts/inheritance — in YAML or canonical JSON.
+description: Use when authoring or modifying MetaObjects metadata — fields, entities, relationships, sources, enums, abstracts/inheritance — in YAML or canonical JSON; includes deciding whether and how to register custom vocabulary (new subtypes or attributes via a provider).
 ---
 
 # Authoring MetaObjects metadata
@@ -355,17 +355,39 @@ metamodel attribute*: you declare the FK once via `identity.reference`, and the
 finders fall out of codegen. So never hand-roll a `findByParentId` / `WHERE fk = ?` helper —
 consume the generated finder.
 
-**Extending the metamodel (custom providers):** the same ordered procedure above
-governs new vocabulary you register — apply it mechanically before registering
-anything. A would-be subtype that differs from an existing one only by a *property*
-is an **attribute**, not a subtype (a "short string" isn't a new field subtype —
-that is `@maxLength`); a plain string that merely needs validating is a **validation
-attribute**, not a subtype (its native type is still `string`, and there's no
-behavior to own); a concept with its own native type or behavior is a **subtype**,
-and structural variants *within* such a subtype are `@kind`. Every new first-class
-element also requires a registered provider + a `registry-conformance` fixture
-(ADR-0023 strict provenance), and closed enums (including any `@kind` value-set)
-carry `allowedValues` in the gate (ADR-0036). ADR-0037 is the authority.
+### Extending the metamodel — custom providers, and the downstream lifecycle
+
+The same ordered procedure above governs new vocabulary you register — apply it
+mechanically before registering anything. A would-be subtype that differs from an
+existing one only by a *property* is an **attribute**, not a subtype (a "short
+string" isn't a new field subtype — that is `@maxLength`); a plain string that merely
+needs validating is a **validation attribute**, not a subtype (its native type is
+still `string`, and there's no behavior to own); a concept with its own native type
+or behavior is a **subtype**, and structural variants *within* such a subtype are
+`@kind`. Every new first-class element also requires a registered provider + a
+`registry-conformance` fixture (ADR-0023 strict provenance), and closed enums
+(including any `@kind` value-set) carry `allowedValues` in the gate (ADR-0036).
+ADR-0037 is the authority.
+
+**Converge before inventing.** Search the shipped vocabulary first (`meta types
+<term>`) and check the roadmap — if core already models (or plans) the concept, model
+yours in a fold-in-friendly shape. The type names `api`, `operation`, `surface`, and
+`binding` are chartered for planned core vocabulary — never claim one for a
+project-local type (a later core release would force a breaking rename).
+
+**Design rules for downstream vocabulary that ages well.** Keep the node protocol-
+and address-free — the subtype names the *concept*; transport/protocol is a closed
+`@kind` variant *within* the subtype (as `source.rdb` puts table/view behind
+`@kind`), never the subtype axis, and endpoints/addresses never enter metadata.
+Declare config as the *names* of required keys (values stay in env/config) and
+generate a fail-closed check. Reference typed payloads instead of inlining shapes.
+
+**Lifecycle.** Register with explicit provider wiring — never loosen `strict` to
+free-ride ad-hoc attrs. When core later ships the concept your provider shrinks from
+`register` to `extend` (the `template.toolcall` precedent). A second independent
+consumer wanting the same concept is a consumer→core promotion candidate (ADR-0011) —
+open an upstream issue rather than adding core vocabulary yourself. Full guidance:
+`docs/features/downstream-metadata-decisions.md`.
 
 ### Currency
 
@@ -599,7 +621,12 @@ identity passes through via `extends` (`identity.primary: { name: id, extends:
 the exposure (fail-closed). Give it a read-only `source.rdb` `@kind: view`
 child (`source.rdb: { kind: view, table: v_author }`) — codegen keys projection
 detection + view DDL off that read-only source, so without it `meta gen` emits
-nothing for the projection.
+nothing for the projection. **The `CREATE VIEW` body is generated from those
+`origin.*` children by the Node `meta migrate` — never hand-author view SQL for a
+shape origins can express** (an unmodeled view is *unmanaged*, so `meta verify --db`
+can't even catch the drift). Hand-write a view only when a construct origins can't
+express (recursive CTE, window function, set operation) blocks projection authoring,
+and keep that DDL in a hand-edited migration file.
 
 **A `passthrough` field must match its `@from` source's type.** A passthrough
 forwards the source value unchanged, so the projection field's `field.<subType>`

package/agent-context/skills/metaobjects-codegen/SKILL.md

@@ -45,8 +45,12 @@ Every emitted file carries a `@generated` header. This is load-bearing:
 
 Practical rule: **pattern-derivable-from-metadata = regenerate; business logic =
 hand-write in a non-generated file.** FK columns, CRUD, validator chains,
-type-safe finders, `relations()` blocks — all derived, never hand-coded. Custom
-SQL views, regex from outside metadata, and domain logic are what you hand-write.
+type-safe finders, `relations()` blocks — all derived, never hand-coded. What you
+hand-write is what metadata genuinely can't express: regex from outside metadata,
+domain logic, and *irreducible* SQL views (recursive CTEs, window functions, set
+ops). Most views are NOT irreducible — model them as an `object.projection` and the
+view DDL is generated (see the projection bullet below); a hand-written view for a
+shape origins can express is drift the drift gate can't even see.
 
 ## Selecting generators by stable name
 
@@ -86,6 +90,14 @@ the data access too.
   `meta migrate` its DB view), and you **call that generated query from your
   route**. Declaring the projection is only half the win — *consuming* its
   generated query is the other half.
+  - **Never hand-author the view SQL for a shape origins can express.** The
+    `CREATE VIEW` body is emitted by the Node `meta migrate` from the projection's
+    `origin.*` children — hand-writing it is a second source of truth that drifts
+    silently, because an unmodeled DB view is *unmanaged*: `meta verify --db` never
+    flags it. Hand-written view SQL is legitimate only when a named construct
+    origins can't express (recursive CTE, window function, set op) blocks
+    projection authoring — then keep that DDL in a hand-edited migration file and
+    justify it in review.
 
 `meta gen --list` prints every generator by stable name; the `generators` array in
 `metaobjects.config.ts` is where you opt each one in or out.

package/agent-context/skills/metaobjects-codegen/references/java.md

@@ -89,6 +89,13 @@ first group together:
 | `SpringOutputParserGenerator` | the `template.output` parser-on-receipt (see the prompts reference) |
 | `SpringFilterAllowlistGenerator` | per-entity filter allowlist |
 
+**Projections (read-only views).** An `object.projection` (read-only `source.rdb`
+`@kind: view` child) is served read-only through OMDB at the ObjectManager layer
+(mutating ops throw); no controller is generated (controllers cover writable entities
+only). Its `CREATE VIEW` DDL is emitted by the Node `meta migrate` from the
+projection's `origin.*` children — never hand-author the view SQL for a shape origins
+can express (an unmodeled view is unmanaged and drifts silently).
+
 Metadata lives under `src/main/metaobjects/` in the same canonical JSON the other
 ports read — fused-key form, `source.rdb` + `@table`, `@column` for a renamed
 physical column.

package/agent-context/skills/metaobjects-codegen/references/kotlin.md

@@ -106,6 +106,13 @@ All live in `metaobjects-codegen-kotlin` under
 | `KotlinStoredProcGenerator` | stored-procedure call wrappers for `source.rdb` `@kind="storedProc"` |
 | `KotlinFilterAllowlistGenerator` | per-entity filter allowlist |
 
+**Projections (read-only views).** For an `object.projection` (read-only `source.rdb`
+`@kind: view` child), `KotlinExposedTableGenerator` emits a read-only Exposed `Table`
+wrapper (same column mapping, no write path). The `CREATE VIEW` DDL is emitted by the
+Node `meta migrate` from the projection's `origin.*` children — never hand-author the
+view SQL for a shape origins can express (an unmodeled view is unmanaged and drifts
+silently).
+
 Metadata lives under `src/main/metaobjects/` in the same canonical JSON the other
 ports read — fused-key form, `source.rdb` + `@table`, `@column` for a renamed
 physical column.

package/agent-context/skills/metaobjects-codegen/references/typescript.md

@@ -80,6 +80,14 @@ From `@metaobjectsdev/codegen-ts/generators` (server-side, framework-neutral):
 | `promptRender()` | `render<Name>()` per `template.prompt` |
 | `outputParser()` | `<Name>.output.ts` (`parse*` / `safeParse*`) per `template.output` |
 
+**Projections (read-only views).** For an `object.projection` (a read-only `source.rdb`
+`@kind: view` child), `entityFile()` emits a `pgView(...)` + read-only Zod + a read-only
+finder (no create/update/delete). The `CREATE VIEW` DDL is generated by `meta migrate`
+from the projection's `origin.*` children — `origin.passthrough` (a forwarded column),
+`origin.aggregate` (a `count`/`sum`/`avg`/`min`/`max`, optionally row-scoped with
+`@filter`), `origin.collection` (a nested array). **Never hand-write the view SQL** for a
+shape origins can express; an unmodeled view is unmanaged and drifts silently.
+
 ## Discriminator inheritance (TPH)
 
 The TS reference implementation fully supports **table-per-hierarchy (TPH)

package/agent-context/skills/metaobjects-verify/SKILL.md

@@ -17,7 +17,12 @@ Drift is any place where a derived artifact has fallen out of sync with the
 metadata that should define it. The ones a developer must actively guard:
 
 - **DB-vs-metadata** — the live database schema has diverged from the metadata
-  (a column the metadata no longer declares, a missing index, a type mismatch).
+  (a column the metadata no longer declares, a missing index, a type mismatch). A
+  **modeled projection's** view body is compared too — a changed `CREATE VIEW` emits
+  a `replace-view`. But a **hand-authored, unmodeled view is *unmanaged*** (reported
+  as informational, never failed, never dropped), so a hand-written view standing in
+  for an expressible `object.projection` is the one drift class `verify --db` can't
+  catch — the `metaobjects-audit` skill is the only gate that sees it.
 - **Generated-vs-metadata (codegen)** — committed generated code no longer matches
   what the current metadata would emit (someone edited a `@generated` file, or
   forgot to regenerate after changing metadata).

package/agent-context/skills/metaobjects-verify/references/migration.md

@@ -127,6 +127,35 @@ A non-unique recency index is `index.lookup`:
     "@orders": ["asc", "desc"], "@where": "archived_at IS NULL" } }
 ```
 
+The `@where` / `@using` / `@expr` / `@orders` attributes are **index** physical
+escapes on `identity.secondary` / `index.lookup` — they are NOT a raw-SQL escape
+hatch for views. There is no attribute that injects hand-written SQL into a
+projection view body (by design — see below).
+
+## Projection views (generated view DDL)
+
+A read-only projection (`object.projection` with a `source.rdb` `@kind: view` child)
+does **not** get a hand-written `CREATE VIEW`. `meta migrate` synthesizes the view
+DDL from the projection's `origin.*` children — `passthrough` columns, `aggregate`
+rollups (`count`/`sum`/`avg`/`min`/`max`), and `collection` joins — through the one
+canonical view-SQL emitter shared with drift detection.
+
+- Change the projection (add a passthrough, change an aggregate) → `meta migrate`
+  emits a `create-view` / `replace-view`; a change to a source-table column the view
+  selects auto-recreates the dependent view.
+- `meta verify --db` **body-compares** a modeled view — a live `CREATE VIEW` that no
+  longer matches the projection is `replace-view` drift.
+- A **hand-authored, unmodeled** DB view is *unmanaged* — never diffed, never
+  dropped, never reported as actionable drift. That is the blind spot: a hand-written
+  view that could have been a projection drifts silently, so it is caught by the
+  `metaobjects-audit` skill, not here.
+
+**Do not hand-author view SQL for a shape origins can express** — model it as a
+projection so the view DDL is generated and drift-checked. The only case for
+hand-written view DDL is a genuinely irreducible view (recursive CTE, window
+function, set operation) that origins can't express; carry that in a hand-edited
+migration file.
+
 ## Adopting an existing database (non-destructive)
 
 `meta verify --db` / `meta migrate` can reach **zero drift** against a hand-built

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@metaobjectsdev/sdk",
-  "version": "0.15.18",
+  "version": "0.15.19-rc.1",
   "description": "Workspace helpers and agent-docs utilities for MetaObjects projects.",
   "type": "module",
   "main": "./dist/index.js",
@@ -56,7 +56,7 @@
     "access": "public"
   },
   "dependencies": {
-    "@metaobjectsdev/metadata": "0.15.18",
+    "@metaobjectsdev/metadata": "0.15.19-rc.1",
     "zod": "^3.23.0"
   },
   "devDependencies": {