# Toolchain Boundary Record: Current Xeno Build System

## Identity

- Component: TypeScript/Node development, test, analysis, bundling, packaging, native-build, and CI toolchain
- Replacement milestone: PROPRIETARY-TOOLCHAIN-1
- Repository and paths: CLI/SDK manifests and lockfiles, build/test configs, native build scripts, CI workflows, and generated compliance inventories
- Record owner: Xeno engineering, final owner assignment pending
- Audit date (UTC): 2026-07-12
- Status: boundary inventory and anti-overclaim controls complete; P4 implementation not started

## Current Boundary

- Product target: P2.
- P4 capability gate: false.
- Generated CLI development graph at audit: 397 records, including 392 build-only and 5 external-runtime records.
- Unique development package names at audit: 324.
- Direct tool groups: TypeScript/type contracts, tsup/esbuild, TSX, Vite/Vitest/Rollup, ESLint/typescript-eslint, npm/lockfile tooling, and @yao-pkg/pkg.
- Native and hosted boundaries: operating-system compilers/SDKs/linkers, Node/N-API headers, shell/PowerShell, and GitHub Actions remain external.
- License review: seven installed development entries require review; no claim resolves those entries automatically.

## Controls Added

- `@yao-pkg/pkg@6.21.0` is exact and committed to the lockfile.
- The cross-platform owned packaging orchestrator invokes the exact installed `@yao-pkg/pkg@6.21.0` entry point directly; release packaging does not use `npx` or download a moving package compiler.
- Deterministic ZIP/TAR generation, checksums, target validation, and runtime-manifest orchestration are Xeno-owned control logic.
- Optional Bun packaging requires a preinstalled executable and never downloads Bun in the build script.
- `scripts/verify-toolchain-boundary.mjs` reconciles direct manifest requests to lockfile versions, generated development records, license-review entries, and the false P4 policy gate.
- `npm run compliance:toolchain` writes and immediately verifies `docs/compliance/toolchain-boundary.json`.
- Human-readable scope and exit criteria are in `docs/TOOLCHAIN_BOUNDARIES.md`.

## P4 Replacement Scope

P4 requires owned language parsing/type analysis/transpilation, bundling and source maps, test runtime/assertions/mocking/coverage, static analysis, package resolution/integrity/packing/publication, executable packaging, native build orchestration, and deterministic provenance. The accepted OS/compiler/SDK/hosted-CI boundary must be approved before implementation.

## Verification Evidence

- Toolchain boundary write/verify passes against the current lock, policy, ownership graph, and license inventory.
- The packaging control path passes focused deterministic archive and PE-import tests, a clean Debian dual-target run, exact Windows cross-built execution, and same-environment byte comparison.
- CLI build and TypeScript checks pass with the sibling SDK junction restored.
- CLI compliance reports zero ownership violations; artifact-inclusive audit reports 927 records and zero violations.
- These results prove classification, control-path behavior, and same-environment reproducibility only. They do not prove P4 or independent-environment byte reproducibility.
- No release was published by this work.

## Handoff

- Phase 7 inventory and claim boundary complete: yes
- P4 implementation complete: no
- P4 evidence complete: no
- P4 capability gate may be marked achieved: no
- Ready to scope a separately funded compiler/toolchain program: yes
- Counsel/public P4 approval: pending
- Author/date: Codex implementation assistant, 2026-07-12