VENTURE SYNAPTICLABS · FOUNDRY · STUDIO

Research. Engineer. Build.

A technology initiative connecting scientific exploration, engineering maturity, and real-world products.

Explore our work View research

01Research

LABS

Computational hypotheses, formal models, controlled experiments, and public artifact packages.

Enter division

02Engineering

FOUNDRY

Compilers, SDKs, language servers, reproducible packaging, and developer tooling.

Enter division

03Ventures

STUDIO

Focused software products built around real operational and engineering problems.

Enter division

Three specialized disciplines operating under one technical standard — with both research-driven maturation and direct product paths.

§ 01 — ARCHITECTURE OF THE INITIATIVE

Three disciplines, one ecosystem

Venture Synaptic separates scientific inquiry, tool engineering, and product development so each discipline is evaluated by the right standard — falsifiable evidence in Labs, reproducible engineering in Foundry, and practical utility in Studio.

01 / LABSScientific research & experimental evaluation

Labs — Explore what is possible

Research into computational models, program properties, verification, and evidence-driven experimentation.

01.Formally stated questions & falsifiable hypotheses
02.Controlled empirical comparisons (positive & negative results)
03.Reproducible artifact archives with SHA-256 manifests

Discover Labs

02 / FOUNDRYEngineering maturation & developer tooling

Foundry — Make technology usable

Turn validated concepts and engineering prototypes into documented, testable, installable tooling.

01.EFCH Lang 0.1.x experimental language & compiler CLI
02.Typed SDKs (TypeScript, .NET 8) and LSP v3.17 integration
03.Deterministic test suites and pinned solver dependencies

Explore Foundry

03 / STUDIOSoftware products for concrete operational needs

Studio — Create products that matter

Build and develop software products around real needs, whether or not they originate in research.

01.Fladya — Product Engineering Intelligence
02.Nicxello — Spreadsheet-to-Web Applications
03.Independent product roadmaps and dedicated brands

See products

Non-linear ecosystem topology

Products in Studio do not require an origin in Labs. Findings from real-world software engineering and tooling can inform new research questions, while validated prototypes from Labs can mature through Foundry.

[PATH A]Research maturation path: Labs → Foundry → Studio

[PATH B]Direct product path: Real-world problems → Studio

[LOOP]Empirical feedback & problem constraints → Labs / Foundry

§ 02 — ECOSYSTEM INDEX

Featured work

Each initiative is labeled by its nature and current verified stage — never conflating exploratory research with production software.

EFCH

Labs · Research program

Property-oriented engineering, synthesis and formal verification: an experimental research direction.

[RES]Research prototype (0.1.0a1) · Under investigation

Inspect EFCH research

EFCH Lang

Foundry · Language/toolchain

An experimental language and toolchain focused on bounded, verifiable programs.

[EXP]Alpha 0.1.x · Bounded program domains

Inspect EFCH Lang

Fladya

Studio · Product

Engineering intelligence across software delivery, traceability and workflows.

[DEV]Product in development · Independent brand

View Fladya sheet

Nicxello

Studio · Product

Transform structured spreadsheet workflows into shareable web applications.

[DEV]Interactive preview · Independent brand

View Nicxello sheet

§ 03 — VERIFIABILITY STANDARD

Research with evidence

We distinguish hypotheses, experimental results, reproducible artifacts, and product capabilities. Claims should be traceable to publicly available evidence whenever possible.

01Hypotheses: Explicit research questions framed with falsifiable criteria before claiming general validity.
02Experimental results: Controlled evaluations within declared domains, reporting both supported findings and refuted or inconclusive outcomes.
03Reproducible artifacts: Public archives with SHA-256 digests, pinned solver versions, raw logs, and informed reproduction scripts.
04Product capabilities: User-facing software evaluated on workflow utility, reliability, and clear operational scope.

Publicly verifiable repositories, DOIs, and author identity

Structure of our scientific records (2026-11-02): We distinguish two public draft preprints from their two published software/data artifact packages on Zenodo and GitHub, grouped by research line (P1 and P2) and linked to author identity via ORCID (an author attribution registry, not a peer-review certification).

Investigation P1 — Preprint & Published Artifacts (EXP-019)Zenodo DOI · P1 Line

Preprint (Public Draft): 'Safe Reuse Is Not Enough' · Artifacts (Published): EFCH P1 Artifacts (Concept DOI: 10.5281/zenodo.23873678 · v1.1-exp019 DOI: 10.5281/zenodo.23874125 · v1.0-exp019 DOI: 10.5281/zenodo.23873679)

Investigation P2 — Preprint & Published Artifacts (EXP-004 to EXP-015)Zenodo DOI · P2 Line

Preprint (Public Draft): 'Verified Binary Decoding with a Domain-Specific Language' · Artifacts (Published): EFCH P2 Artifacts (Concept DOI: 10.5281/zenodo.23874419 · v1.0-lang DOI: 10.5281/zenodo.23874420)

GitHub — EFCH Research & Reproducible Artifact ExportsGitHub Code & Data

Public artifact repositories (efch-artifacts-p1-evidence-persistence & efch-artifacts-p2-lang-binary-decoding) exported with SHA-256 manifests from venture-synaptic/efch-research.

ORCID — Academic Author Identity (0000-0001-7268-5510)ORCID Registry

Erik Fisher Cueva Huari (VentureSynaptic Labs). Persistent researcher identifier linking preprints and artifact DOIs (author identity, not peer-review certification).

Interested in the research or the products?

Explore the open work or reach out about technical collaboration.

Browse research Contact