VEYNDO
Handbook
docs/evidence/app-object-graph-contracts-2026-11-05.mdView source ↗

English source · 4 min

Shared app object and intelligence graph contracts: 5 November 2026

Delivered ownership

Apps 0.9.0 supplies model 0.6.0 from exact source fab9d1c18faa43799278355582c6e47f7659a303. components.lock.json verifies its complete snapshot/file hashes; provenance retains the original native owners at Core 4d37ed01.

Shared owner Native consumer Authority retained by host
model/src/object_extensions.rs core_extensions.rs Current object/PII rights and immutable native reference ownership; the verified configuration-release predicate keeps its direct native caller
model/src/intelligence.rs manifest.rs, surfaces.rs Full typed package admission, original validator order, MCP exposure opt-in, current agent rights and inference dispatch
model/src/ontology.rs ontology.rs, authorized lists in data.rs and native-object extension_projection.rs Actual tenant-scoped/current-authority queries, field/language/reference validation, record ownership and private/public release

Product, customer, order and company binding declarations retain their original private unique indexed required reference anchors. Bound models require declared native list/data reads; list/save actions retain the exact native object scopes, including PII for customer/order data. Actual current actor checks stay native.

Strict intelligence and mapping types preserve original wire defaults, unknown-field rejection and legacy omission. Tool/entity names and budgets refer to declared models/actions; this metadata does not enable MCP, grant an agent a tool or replace complete package validation. Mapping checks retain selected fields, localized labels, namespace grammar and existing reference-edge constraints.

The same pure projector derives bounded graph output from already-authorized current rows, preserving app/version/entity/record/revision provenance. Explicit mappings expose selected properties; inferred object-extension views retain their original declared-field behavior. Reference edges carry metadata only: they neither read target records nor confer access or become confirmed product claims. The existing row/edge/byte budgets and omitted-record reporting remain unchanged. There is no duplicate graph database, new production table, schema/role change, credential, model provider or second commerce ledger in this extraction.

Independent acceptance

All 71 model tests pass, including ten new object-binding/graph/intelligence scenarios. They cover all four native objects and exact read/write/PII declarations, private unique anchors and invalid handlers, unknown wire fields, actual selected properties and current revisions, localized labels, reference-only namespaced edges, invented/duplicate mappings, model/tool limits, 24-row/100-relation/byte bounds, malformed rows and legacy/inferred projections.

The executable Rust example cargo run --locked --example object_graph validates an app-owned product extension and derives its graph from synthetic admitted rows without Core, SQL, network, credentials or inference. A real host must obtain its input through the current authorized tenant-scoped list. Model/storage lint and formatting pass; the independent model retains its own lockfile and direct CI. Actual isolated PostgreSQL storage/installation contracts pass, preserving CAS, rollback, immutable versions, quota, replay and package-writer/lease fencing. Component PR and CI pass.

Composed acceptance

A fresh native build, clippy and all 73 native app unit tests pass. The original native adapter tests remain attached. All 34 bundled packages pass full native validation and retain their exact fingerprints after the moved wire types.

Twelve affected actual PostgreSQL/HTTP modules pass: apps, consent, schema, Studio, ontology, private preview, core extensions, staging, tenant isolation, surfaces, AI app generation and Marketplace. In particular:

  • API and MCP return the same current tenant-owned graph records, fields, revision and relations. Foreign shops, disabled apps and actors without current rights cannot read private tools. Invalid mappings reject before installation.
  • All four native object lists/details project typed revisioned app fields; indexed filters run before pagination, oversized previews remain explicit and public products exclude private data. Read-only/revoked actors cannot mutate.
  • Private product/company extension cloning and selected publication retain live customer/order records and reject installed object rebinding.
  • Actual model transport receives bounded selected context, respects agent/MCP opt-out and current tool budgets, creates validated immutable drafts, opens the real private preview and exercises record/upload/reload. Selected publication reaches the existing native simulated order workflow without paid calls.
  • Marketplace HTTP/MCP, sync, native order/stock/invoice/Flow and restart/replay composition remains green.

AI generation uses the existing local synthetic model fixture and the selected working Node 22 executable. These are affected checks, not a new paid provider or whole-platform acceptance. Snapshot/source structure, documentation/site, existing extracted Lean kernel and negative mutation checks pass; new model/graph/host/SQL paths remain outside the proved kernel. Full coverage keeps its daily schedule.

Remaining independent service scope

MKT-03b remains open for remaining typed UI/domain extension validators, identity and credential/lifecycle hosting, an independently supported production schema and standalone API/MCP/SDK service. A graph Context or tenant string is metadata, not authentication. The graph projector requires an already-authorized record consumer and owns no source store or target-record resolver.

The component release and Core source integration do not establish a public commerce-runtime deployment or a new real payment acceptance. Public handbook publication is checked separately after merge.