Public typed contracts
Requests, outcomes, providers, operation semantics, policies, configuration, diagnostics, catalogs, and declarations are implemented and documented.
Audited status · v1.0.1
Implemented, experimental, and explicitly out of scope
BatchWeaver is a working compiler/runtime toolkit published as stable v1. This page separates verified implementation from experimental integrations and from the accepted risks this release ships with, which documentation alone cannot close.
Release evidence
What has been publicly verified
5immutable published tags
29required hosted checks per change
5release archive targets
10public Go packages on main
81architecture decision records
0known vulnerabilities in the release scan
- Public Go proxy and pkg.go.dev installation
- Linux, macOS, and Windows protected CI builds
- Race, coverage, lint, vulnerability, CodeQL, and Dependency Review jobs
- Complete downloaded checksums and release-manifest verification
- SPDX 2.3 and CycloneDX 1.5 SBOMs plus local unsigned provenance
- Byte-for-byte artifact reproduction under the declared toolchains
- VS Code VSIX installation and real Extension Host activation evidence
- GitHub Pages, private vulnerability reporting, protected main, and rollback procedures
Ready and implemented
Working product capabilities
Explicit request-coalescing runtime
Instance-scoped engine, request scopes, partitioning, bounded queues, independent cancellation, deadlines, deduplication, memoization, retries, fallback, result validation, statistics, and hooks.
Static analysis and proof
Package loading, SSA, conservative call graph/effects, declaration discovery, candidates, strategy-specific proof obligations, explicit assumptions, witnesses, deterministic certificates, and fail-closed rejections.
Transformation and overlay execution
Versioned plans, source anchors, static loop prefetch, runtime lowering, exact/composite/bounded-join SQL generation, generated typed bindings, source maps, deterministic diffs, Go overlays, atomic materialization, recovery, and revert.
Adapter and protocol foundation
Adapter SDK, exact/composite-key database/sql PostgreSQL reads with one explicit at-most-one join, HTTP explicit batching, OpenAPI vendor extensions, Redis cluster-safe mapping, gqlgen scopes, and typed grpc-go providers.
Concrete client integrations
Typed pgx v5 array queries, go-redis v9 MGET/HMGET/pipelines, gqlgen operation scopes and field partitions, and explicit grpc-go unary batch RPCs with bufconn coverage.
Adaptive and operational controls
Privacy-safe profiles, cost model, shadow/active modes, SLO guardrails, rollback, replay, fairness, overload admission, multi-operation waves, and recursive breadth-first batching.
Editor and developer experience
Standalone LSP, optional gopls proxy, unsaved-buffer overlays, diagnostics, hover, code lenses, previews, workspace daemon, VS Code extension, and standard LSP editor guides.
Release and supply-chain assurance
Cross-platform archives, VSIX, checksums, SBOMs, local provenance, compatibility/security/performance reports, exact-commit verification, byte reproduction, protected CI, and public-install tests.
Under development
Useful foundations without a complete supported integration
Client deployment breadth
- Live PostgreSQL acceptance
- Multi-node Redis Cluster acceptance
- Generated-schema gqlgen application matrix
- Multiple grpc-go/protobuf version combinations
The bindings are implemented; only combinations backed by the compatibility matrix are claimed.
Broader transformation coverage
- Write synthesis and arbitrary SQL rewrites
- One-to-many or multi-join synthesis
- Automatic GraphQL/gRPC generation
- Aggressive parent-level fan-out enqueue
Composite keys and one bounded join are implemented; unsupported shapes are rejected rather than approximated.
Editor depth
- Marketplace publication
- Version-preconditioned WorkspaceEdit application
- Community-editor host UI automation
Preview-first workflows, real minimum/current VS Code hosts, a real gopls proxy process, the GitHub Release VSIX, and the local shared analysis cache are functional today.
Compatibility and operations
- Go versions outside the tested 1.26.x window
- Live PostgreSQL and Redis Cluster environments
- Windows arm64
- Long production-like workload evidence
Module, vendor, go.work, CGO/non-CGO, native OS, release-target, and exact-client jobs are blocking. Only combinations listed in the compatibility matrix are claimed.
Deliberate limits
Behavior BatchWeaver does not claim
- It does not prove every Go program or transform every N+1 pattern.
- It does not infer arbitrary network fusion or backend batch endpoints.
- It does not batch writes automatically or weaken transaction boundaries.
- It does not upload source, runtime payloads, credentials, tenant IDs, or raw keys.
- It does not mutate source merely by scanning, proving, importing packages, or opening an editor.
- It does not promise batching will improve every workload.
- It does not provide hosted SLSA attestation or cryptographic release signatures today.
- It does not extend the v1 stability promise to the
bridgeoradapters/*packages.
Stable v1 status
Gate results at the released commit
PassCurrent P0/P1 defects
All reproduced defects have focused fixes and regression coverage.
PassSemantic assurance
Differential and mutation suites pass; 12/12 modeled critical mutations killed.
PassCompatibility
Hosted compatibility policy, Go 1.26.0/1.26.5, every build mode, and all native and cross targets pass at the released commit.
PassMigration
An executable suite migrates every published prerelease to the v1 release and asserts scalar rollback.
PassInstallation
go install from the public module proxy is verified and reports the stable channel.
PassPublic API freeze
Tier 1 packages are frozen under Semantic Versioning; the exported surface is baseline-checked.
Accepted riskSupply chain
Checksums, SBOMs, provenance, and reproduction pass; artifacts are not yet signed or attested.
Accepted riskField evidence
The public prerelease period was short and there is no live-backend acceptance run.
PassGovernance approval
Approved with every accepted risk recorded alongside a remediation plan.
A gate marked as an accepted risk is published as a risk, not as a pass. Each one names its exception and remediation in the machine-readable gate report.
Current recommendation
Use v1.0.1 and report reproducible findings
Pin the exact version, review proofs and diffs before materializing anything, run your complete application suite, and report reproducible compatibility or semantic findings.