100000x · 05 — No-Vector Verification

Phase: D component · Status: PASS — 4 layers held; CUT does not vectorize.

Live evidence

Layer	What	Live result
L1 — staging CHECK	iu_core.iu_staging_record_vector_excluded_chk: vector_excluded = true	Enforced on every MARK row in proof (3 rows: NVSZ-PROOF-100000x + G6 + G7 fixtures all show vec_excluded=t)
L2 — sidecar policy	public.collection_registry_vector_policy (COL-IUS-001 + COL-IUS-002 — D36 Macro A)	Unchanged; no rows added/modified by 100000x
L3 — sync_point shape	public.iu_vector_sync_point table has only unit_id + parent_piece_id references; no staging_record_id / staging_payload_id columns	Schema introspected; structurally CANNOT reference staging
L4 — view eligibility	public.v_collection_vector_eligibility (D36 Macro A)	Unchanged

Post-cut verify

fn_iu_verify_cut_result axis no_vector_ok query (live):

SELECT count(*) FROM iu_vector_sync_point
 WHERE unit_id        = ANY(pieces_created)
    OR parent_piece_id = ANY(pieces_created);
-- = 0

After CUT created 2 IU pieces, this returned 0. Zero VSP rows reference the new cut pieces — CUT performs zero vectorization, by construction.

Post-rollback verify

iu_vector_sync_point row count: pre=152, post=152. Equal. Zero VSP mutation across the entire proof envelope.

Qdrant

• No Qdrant API call from 040R/041R. No outbound network from postgres fns.
• iu_core.vector_sync_enabled = false (untouched).
• iu_core_iu_chunks collection: not contacted; per memory 149 points; unchanged.

production_documents

• Table does not exist in directus DB (structural absence).
• 040R/041R contain zero references to production_documents.
• Healthcheck (Phase E): row count comparison N/A by absence.

Cross-links

• [[feedback-iu-vector-sync-point-has-no-staging-path]] (L4 structural guarantee).
• [[project-d36-no-vector-staging-zone-macro-a-substrate-birth-dot-healthcheck-partial-with-exact-gap-2026-05-25]] (sidecar + view authored).
• 91000x report 04 (4-layer NVSZ structural proof).