02 / VENTURE SYNAPTIC FOUNDRY

Foundry — From prototype to dependable tooling

Foundry transforms research prototypes and software engineering concepts into modular, testable, and documented tools that developers can inspect and evaluate.

§ 01 — PIPELINE

Technology maturation workflow

How an exploratory compiler or protocol prototype progresses toward usable developer infrastructure.

01 —STAGE

Interface & Contracts

Define stable CLI contracts and canonical JSON schemas (such as efch-evidencia/1.0) decoupled from internal research scripts.

02 —STAGE

Typed Implementations

Build strongly typed adapters and language servers without duplicating core semantic parsers or SMT engines.

03 —STAGE

Automated Verification & Tests

Validate behavior with unit tests, differential test vectors, and deterministic solver environments.

04 —STAGE

Packaging & Sandboxing

Enforce shell-free process execution (execFile), explicit timeouts, AbortSignal support, and pinned wheel hashes.

05 —STAGE

Documentation & Limits

Document exact domain constraints, supported versions, and unverified boundaries before distribution.

06 —STAGE

Distribution & Feedback

Deliver via CLI, language SDKs, LSP servers, and editor extensions, feeding field diagnostics back into Labs and Foundry.

§ 02 — FEATURED TOOLCHAIN[EXP]Alpha 0.1.x · Bounded Domains

EFCH Lang & Ecosystem Tooling

“EFCH Lang is an experimental programming language and toolchain exploring explicit contracts and verifiable behavior, initially within bounded program domains.”

Version lines & release reality

0.1.x Line (Alpha)[Active Alpha maintenance & tooling integration]

Includes the EFCH 0.1.0a1 core compiler/verifier in Python + Z3 5.1.0.0, canonical evidence export (efch-evidencia/1.0), TypeScript SDK, .NET 8 SDK, LSP v3.17 server, and VS Code extension (v0.1.2).

0.2 Line (In development)[In development — Not released]

Explores expanded semantic capabilities and language ergonomics. Version 0.2 is under active development and is not published as a general release.

[FORMAL VERIFICATION BOUNDARY]

Formal verification scope notice: Discharging formal proof obligations in the typed EFCH core and specified bounded domains proves mathematical properties of the model in Z3; it does not constitute a formal verification proof of the Python translator, the generated C code, or the final compiled binary.

§ 03 — STANDARDS

Engineering & quality standards

01Safe process invocation

SDKs invoke the compiler binary via direct process execution (execFile) without shell interpolation, enforcing buffer limits and cancellation signals.

02Fidelity to formal solver states

Tooling strictly preserves SMT verification outcomes (proved, refuted with concrete JSON counterexamples, or unknown/timeout) without masking solver uncertainty.

03Reproducible solver pinning

Verification workflows pin exact Z3 wheels (Z3 5.1.0.0) and comparator toolchains via SHA-256 verified vendor scripts.

04Zero semantic duplication

Editor extensions and SDKs consume the canonical compiler CLI and JSON schemas rather than reimplementing ad-hoc parsers.

§ 04 — DISTRIBUTION

Delivery channels

How EFCH Lang and Foundry tooling are structured for consumption across environments.

Compiler & Verifier CLI (python3 -m efch)

Available in public P2/P1 artifact archives (0.1.0a1)

Command-line interface supporting check, eval, verify, build (C emission), synth, and semantic store operations.

TypeScript SDK (efch-lang-sdk-ts)

Alpha 0.1.x · Repository private pending public release

Strongly typed Node.js/TypeScript wrapper with automatic compiler discovery (.venv, EFCH_PATH, PATH) and structured diagnostics.

.NET 8 SDK (efch-lang-sdk-dotnet / EfchLang.Sdk)

Alpha 0.1.x · Repository private pending public release

Non-invasive .NET 8 SDK integrating efch export check/lang contracts (efch-evidencia/1.0) into C# and xUnit test pipelines.

Language Server (efch-lang-lsp) & VS Code Extension

Alpha 0.1.x (v0.1.2) · Repository private pending public release

Standard LSP v3.17 server over stdio providing real-time diagnostics, counterexample surfacing, go-to-definition, and hover across .efl and .efch files.

§ 05 — REPOSITORY INDEX

Repository status & public access

We distinguish between repositories that are publicly accessible today and internal tooling repositories in the venture-synaptic organization awaiting public release.

venture-synaptic/efch-artifacts-p2-lang-binary-decoding

Python 3.10+, Z3 5.1.0.0, C (gcc) · v1.0-lang (EFCH 0.1.0a1)

Public archive containing the EFCH 0.1 core & EFCH Lang implementation, 178 unit tests, and reproducible scripts for EXP-004 to EXP-015.

Public & verifiable now

venture-synaptic/efch-lang-sdk-ts

TypeScript, Node.js (execFile) · 0.1.x Alpha

Official TypeScript SDK for interacting with the EFCH 0.1.x compiler, formal verifier, and CLI diagnostics.

Internal Alpha · Public release pending

venture-synaptic/efch-lang-sdk-dotnet

C#, .NET 8, xUnit · 0.1.x Alpha

.NET 8 SDK (EfchLang.Sdk) consuming canonical efch-evidencia/1.0 JSON contracts for C# / xUnit CI integration.

Internal Alpha · Public release pending

venture-synaptic/efch-lang-lsp

TypeScript, LSP v3.17 (stdio) · 0.1.x Alpha

Language Server Protocol (v3.17) server for .efl and .efch specifications built on efch-lang-sdk-ts.

Internal Alpha · Public release pending

venture-synaptic/efch-lang-vscode

TypeScript, VS Code Extension API · v0.1.2 Alpha

VS Code extension for syntax highlighting, formal verification commands, and LSP integration for .efl and .efch.

Internal Alpha · Public release pending