ABI is a compiler and evidence system, not an inference runtime.
- Qualify a source. Pin a model and tokenizer revision, hash every weight file, record the license identifier, and reject mutable or remote-code sources from promotion.
- Survey bounded capabilities. Execute a declared probe catalog. The resulting inventory describes only those probes; it is never presented as exhaustive teacher introspection.
- Label every record. Route linguistic-form records toward the English core, specialist claims toward a named domain, and ambiguous material into quarantine.
- Select and budget. The user chooses English and/or named domains. Nested budgets expose the marginal effect of imported teacher information.
- Package immutably. Canonical serialization and SHA-256 bind sources,
records, labels, probes, budgets, and accounting into
.abixor.abiciracquisition artifacts. - Hand off through the canonical boundary. An external host such as LayerCake consumes qualified acquisition material and owns any host-side conformance, package installation, routing, and execution.
- Teacher output is untrusted input until labeled and qualified.
- A classifier suggestion is not a human label unless a human attests it.
- An acquisition artifact can contain teacher material and is not a deployable model package.
- A LayerCake cake is a host artifact and is not owned by this repository.
- Exact byte identity, bounded functional retention, and general semantic equivalence are separate claims.
ABI V2 adds an experimental representation-neutral extension/runtime boundary for already sealed capability packages:
frozen host checkpoint/tokenizer
|
v
capability-blind host certification -> frozen generic adapter
|
immutable package -> canonical context/runtime/output intent
|
v
exact host-native token/UTF-8 realization
The canonical state uses fixed typed semantic channels plus exact UTF-8 anchors for names, numbers, identifiers, literals, Unicode, and formatting. Host-private hidden width, residual basis, tokenizer vocabulary, layer count, position encoding, and normalization remain outside the capability contract.
Each host adapter is frozen before packages are revealed and must then accept all compatible packages without fitting, calibration, or mutation. The reference V2 adapters are zero-parameter native codecs. The generic runtime owns authenticated execution of the capability package; it does not inject the package tensors into a foreign model's private residual coordinates.
This distinction is the exact claim boundary. The local V2 evidence proves an extension/runtime ABI across three named hosts. It does not prove that Qwen or Pythia hidden states learned, generated, or modified the capability semantics.
English-core records must use a declared linguistic capability and a domain-minimized content basis. They cannot carry specialist labels or atomic domain claims, and they cannot introduce facts absent from supplied context. Specialist facts, procedures, reasoning, and code require an explicit domain destination. Known conflicts fail closed; uncertain cases are quarantined.
These controls prove enforcement of the declared data boundary. They do not prove that an arbitrary neural representation contains literally zero world knowledge.
The supported import surface is exported from abi/__init__.py. Phase-numbered
modules are preserved research implementations and may change between alpha
releases. New production-facing behavior should enter through a small,
documented facade with focused tests rather than another versioned top-level
module.