registry-bound vectors
protocol boundary vector registry

boundary vector registry

Protocol Boundary Vectors are release regression vectors for m0de reading boundaries.
A passing vector means the expected reading boundary stayed stable. It does not establish supplied text as fact. It does not attest pasted text origin. It does not score answer correctness or rank models. It does not replace receipt or capsule replay.
Not AI benchmarks. Not answer-correctness scores. Not factuality certification.
Not source attestation, diagnostics authority, proof authority, or a fixture corpus.
registry lock
Visible vector families are bound to registry data and acceptance coverage. Full fixture text and answer text stay out of this public surface. Debug traces, internal move labels, scoring, ranking, and proof authority stay out.
source lane

Pasted source lane, public client lane, adapter return, and source capture boundaries.

BV-01

source lane purity

Pasted lane remains label-insensitive.

checksource label purity limitno source attestation
boundary detail
expected

pasted_answer / user_supplied / null / pasted / not_model_attested remains stable across external labels

check

source label purity

does not

let platform, provider, adapter-used, custom-instruction, verified, or official labels become source evidence

BV-02

public client lane quarantine

Homepage client remains pasted-only.

checkpublic client lane limitno live homepage lane
boundary detail
expected

homepage browser runtime uses pasted_answer only while protected backend live_model capability remains retained

check

public client lane

does not

expose, select, call, or revive live_model from the public homepage client

BV-03

source capture parity

Source packets bind lane fields without full-text logging.

checksource capture limitno full-text logs
boundary detail
expected

source packets bind hashes and source lane fields without full question or full answer logging

check

source capture

does not

turn source claim wording into proof authority or leak full answer logs

BV-04

adapter return bridge

Returned generated text uses the canonical intake.

checkadapter return limitno separate return intake
boundary detail
expected

returned generated text is bridged to the canonical supplied-text intake; the bridge does not create source packets, receipts, capsules, or output provenance

check

adapter return

does not

make a platform name, recipe heading, copy hash, instruction slot, or adapter-use claim into origin attestation

reading closure

Question frame, definition, reference, prediction, and scope boundaries.

BV-05

question frame and closure

Question frame is resolved before closure.

checkframe closure limitno lexicon-trigger truth
boundary detail
expected

question frame is resolved before mode closure; missing required boundaries remain residue

check

frame closure

does not

treat frame recognition or a lexicon trigger as answer truth

BV-06

definition loop boundary

Repeated terms without differentiation remain open.

checkframe closure limitno circular closure
boundary detail
expected

a repeated requested term without differentiating content remains missing_definition and residue_open

check

frame closure

does not

accept a repeated word as completed definition closure

BV-07

reference resolution boundary

Unresolved references stay unresolved.

checksource vector acceptance limitno invented referent
boundary detail
expected

this, that, it, today, tomorrow, event, claim, and thing stay unresolved when no referent is supplied

check

source vector acceptance

does not

invent a referent or collapse context_missing into closure

BV-08

prediction boundary

Future wording stays prediction-bounded.

checksource vector acceptance limitno future fact
boundary detail
expected

future wording remains a prediction frame with uncertainty or missing event boundary when not established

check

source vector acceptance

does not

convert future wording into an established future event

BV-09

answer-scope boundary

Scope overrun remains visible when present.

checkframe closure limitno residue flattening
boundary detail
expected

unsupported short or mixed-scope answers can remain answer_scope_overrun instead of generic residue

check

frame closure

does not

downgrade answer_scope_overrun into plain residue_open

word / response / adapter

Written-form, subject-position, response-regime, and adapter boundaries.

BV-10

written form and referent boundary

Words enter as written forms first.

checkwritten-form differential limitno referent proof
boundary detail
expected

words enter as written forms first; referent links are read-as relations and not proof authority

check

written-form differential

does not

treat a word or referent link as proof of the described subject, source, or happening

BV-11

first-person subject-position

First-person grammar does not attest a subject.

checkfirst-person differential limitno subject attestation
boundary detail
expected

first-person wording does not attest action, desire, feeling, memory, lived time, experience, personhood, or human state

check

first-person differential

does not

let first-person grammar become subject attestation

BV-12

response-regime boundary

Basis, validity, and stop boundaries remain visible.

checkresponse-regime limitno continuation authority
boundary detail
expected

answer basis, requested frame, validity boundary, and stop boundary remain visible

check

response-regime

does not

let a response continue beyond the requested frame or turn basis wording into authority

BV-13

adapter non-authority

Instruction text may shape generated text only.

checkadapter instruction limitno generated-text guarantee
boundary detail
expected

adapter instruction may shape generated text while matching generated text remains generated text

check

adapter instruction

does not

control or guarantee generated text, certify output, or create proof authority

replay / evidence / proof

Projection, proof corridor, external evidence, diagnostics, and public wording boundaries.

BV-14

projection auxiliary replay

Projection replay remains auxiliary.

checkprojection replay limitno correctness proof
boundary detail
expected

reading_group_hash and projection replay are auxiliary and preserve closure, release state, and residue

check

projection replay

does not

enter canonical ui_binding_surface_hash or prove semantic correctness

BV-15

proof corridor same event

Proof corridor preserves the same proof event.

checkproof corridor limitno answer verification
boundary detail
expected

runtime, receipt, capsule, alpha packet, projection evidence, and returned evidence preserve the same proof event

check

proof corridor

does not

turn same-event reproducibility into answer truth or source origin proof

BV-16

external evidence non-authority

Returned external evidence stays evidence.

checkexternal replay evidence limitno external authority
boundary detail
expected

external replay evidence can be accepted as evidence while authority remains capsule replay against pinned roots

check

external replay evidence

does not

make external evidence, returned evidence, or a third party into proof authority

BV-17

protocol diagnostics non-authority

Diagnostics report bounded status only.

checkprotocol diagnostics limitno answer verification
boundary detail
expected

diagnostics report bounded surface status only

check

protocol diagnostics

does not

verify answers, attest source origin, replace receipt or capsule replay, expose private logs, or self-certify the protocol

BV-18

public wording non-authority

Public wording stays inside authority boundaries.

checkpublic wording limitno authority overclaim
boundary detail
expected

public copy stays within receipt, replay, projection, source packet, and evidence boundary language

check

public wording

does not

allow answer-as-fact, source-origin, integration-overclaim, projection-as-correctness, or generated-text guarantee wording to become authority claims

non-benchmark corpus boundary
The registry is a release boundary map. It does not publish a prompt corpus, does not publish answer fixtures, does not create a leaderboard, does not score correctness, and does not certify factuality.