Skip to content

SolveLang documentation

SolveLang full-project completion evidence

Repository source status was re-audited on 2026-09-22 at main 59ab9ff271850454a2029495c2faf34cb93a10c7 after #945. Production/runtime and native-platform observations below were checked on 2026-09-20 through main 632b6ff82f2f54babe46e4e11e672675e4ca838e (#938–#942); each external observation is separately identified and keeps its own collection date. The goal includes the existing roadmap and requested Studio account persistence. It excludes the separately deferred Solve Runners/Solblend product and does not invent a 1.0 language/platform promise. Completion requires evidence, not a percentage estimate or a count of merged PRs.

RequirementEvidence/statusRemaining acceptance
Remove beta positioningConfirmed: #938 merged; six public resources returned 200 with zero beta labelsNone for this copy change
GitHub About descriptionConfirmed saved in the authenticated repository UINone
Main governanceConfirmed: ruleset 18206723, four strict checks, PR required, threads resolved, no bypassHuman approval count is zero by configured policy
MCP v0.3.0 publicationConfirmed npm registry and published GitHub ReleaseDoes not prove marketplace installation
Studio account savingMerged #939 at 8ef4829228e89c1c04ab3f2e0565dc6357b5fce7; 515 API tests, full Studio suite, five CI workflows passedBackend deployed in run 35531150309 with configuration preserved; all six authenticated account-isolation, conflict, switching, offline, export and removal checks remain required before frontend enablement
Safe API maintenance deploymentMerged #940 adds bounded changes, parameter preservation and rollback; 521 API tests pass with #942Plan 35530924473 and deployment 35531150309 passed; all parameters/health flags preserved; unauthenticated Studio GET returns 401
Admin Gateway rollout guardPR #945 exact head c709b3a8325404d2f88d83138a1b331c4e8f04fd passed API Access CI and all four required contexts; merged as 59ab9ff271850454a2029495c2faf34cb93a10c7. The four required main checks and API Access CI also passed on that merge commit. The manual workflow now preserves the captured billing flag; it was not dispatched.Future manual dispatch still requires a separate production approval; this repository change is not deployment evidence
Solve Context independent corpusChalk/node-fetch/Preact and heldout protocol exist after #922–#924Blinded outcomes and actual Claude/Codex provider-token/latency/task-quality matrix
Managed Codex marketplace installRepository packaging/import contract existsActual managed-workspace installation and tool invocation evidence
Public Plugin DirectoryUnverifiedSubmission/review/listing evidence
Production API healthConfirmed public /health: API, customer accounts, TOTP and subscription billing enabledHealth flags do not establish payment outcomes
API subscription payment canaryUnverified; live Stripe search found no subscriptions with Developer/Pro/Business plan metadataExplicitly scoped successful payment, webhook/account entitlement, cancellation/refund/recovery evidence
Connected support #896Repository implementation and monitoring existDeployment, scoped credentials, bounded new-message task/reply and stop/recovery proof
PostHog #833Repository transport/lifecycle contracts existConcrete credential/lifecycle backend, project scope and one bounded live canary
Paid priority/provider executionRepository qualification onlyVerified deployment, provider credentials, alarms and recovery acceptance
Native macOS ARM64 / Windows x64 qualificationMerged #941; both native jobs passed at ed0dbcc82467fb690d2d8dd4420a964001b44846, run 35530427540A new public native release/tag, signing and notarization are not implied
Final security and production smokeFocused changed-boundary review completed; #942 main CI and deployment passed; #943 exact PR head 63b45066fe1e837a158333cb0dfee17d0c6ae31b passed all five workflows (MCP CI, Rust, Release Candidate CI, CI, WASM artifact security)Remaining authenticated Studio, payment and provider acceptance

Directly inspected sources

  • PR #938
  • PR #943, exact PR-head workflows MCP CI, Rust, Release Candidate CI, CI, and WASM artifact security
  • PR #939
  • PR #945, exact head c709b3a8325404d2f88d83138a1b331c4e8f04fd; main checks on merge 59ab9ff271850454a2029495c2faf34cb93a10c7: API Access CI, CI, Rust, and WASM artifact security.
  • Validated production plan and successful deployment, both at main 632b6ff82f2f54babe46e4e11e672675e4ca838e.
  • Native qualification #941 and both-platform run.
  • Native workflow artifact IDs: Windows 10611202508; macOS ARM64 10610698792. These expire after 14 days and are qualification evidence, not public releases.
  • Main ruleset
  • MCP v0.3.0 release
  • npm read: npm view @solvelang/mcp-server@0.3.0 version dist.integrity dist.tarball --json
  • npm integrity: sha512-aOH/Sg6OF17sePGlnoJ6hfFdEY4tL1Wj/ZW8A3ZmpZg9doFJpCC4IUTmhWnTZZY8iToc5y52+n9+Cu/Z68xUlA==
  • Public API health: https://3l3y008e94.execute-api.us-east-2.amazonaws.com/health.
  • Live website checks: /, /about/, /landing/, /run/, /check/, /llms.txt.
  • Live Stripe read-only search in the configured SolveLang merchant account: metadata['plan']:'developer' OR metadata['plan']:'pro' OR metadata['plan']:'business'. Empty results with no further page are limited search evidence, not a claim that the merchant has no payments or that the checkout is defective.

No charges, refunds, inbox messages, customer data changes, provider activation, or secret provisioning were performed for this evidence record.

The changed-boundary verification record covers failure classifications and the limits of repository evidence.