Compiled, stateless deployment prelude artifact (Capability Prelude V1).

A deployment loads curated PTC-Lisp prelude source that declares protected namespaces (e.g. crm) and exports functions/constants. The compiler (PtcRunner.Lisp.Prelude.Compiler) turns that source into one of these artifacts, which is then attached to a run and consulted — unchanged — across direct Lisp execution, SubAgent execution, and the REPL (plan §1A).

Fields

• namespaces — sorted list of declared namespace-name strings. These are the prelude-protected namespaces (host-boundary string-backed).
• exports — list of %PtcRunner.Lisp.Prelude.Export{} public export records (:prompt + :discoverable). Private helpers are NOT here.
• private_env — the captured private prelude environment, keyed by namespace then bare symbol: %{namespace => %{symbol => callable}} ({:closure, ...} for defn). Namespace-scoping keeps same-named definitions in different namespaces distinct (e.g. crm/who vs hr/who). Public exports call their own namespace's private helpers through this env; user code cannot resolve private helpers by qualified symbol (plan §5). The CALLABLE values are the contract slice 2 (evaluator threading) depends on.
• source_hash — sha256 hex digest of the prelude source (plan §12 traceability).
• source_index — precomputed %{full-ref => rendered-source} map for the (source ns/name) discovery form (issue #1095). Keyed by full ref for public exports PLUS the private helpers transitively reachable from some public export; unreferenced privates stay out. Values are rendered strings (a labeled effective-metadata header + the Formatter-rendered defining form), so this cache leaks no captured closure or raw parser AST. NOTE: it exposes export IMPLEMENTATION, not just contract — deployments must keep secrets/credentials out of prelude bodies, not just docstrings.
• metadata — small map of namespace-level facts for traces/debugging, e.g. per-namespace docstring and default visibility.

Private-env capture seam (fact #6)

defn/defn- in the prelude desugar through the existing analyze+eval pipeline to {:closure, params, body, captured_env, turn_history, meta} tuples stored under their bare symbol in a user_ns-shaped map. The compiler captures that whole map as private_env. Sibling helpers are NOT folded into each closure's captured_env — they resolve by name through user_ns at call time, and private_env is exactly that namespace. P2 therefore threads private_env as the user_ns layer (resolver position between the mutable user namespace and built-ins) when invoking exports: a public export resolves qualified (crm/get-user) to private_env[symbol] and runs its body against private_env, so private helpers resolve, while private symbols stay absent from exports and so are unreachable by qualified user calls. Proven end-to-end during P0.

Validation errors

Compile-time failures are returned as {:error, %PtcRunner.Lisp.Prelude.ValidationError{}}, never raised.