Version Centre

Versioned software. Traceable scientific releases.

The Spacefield Version Centre records software maturity, release identity, validation state, documentation, integrity information and access conditions for the SFT Molecular Platform.

Each public or authorised release should be identifiable as a defined scientific and engineering state. Release records connect software versions with model identity, supported interfaces, validation context, known limitations, citation information and integrity manifests. Inclusion in the Version Centre does not automatically mean that proprietary code or model artefacts are available for unrestricted download.

Release identity SFT Molecular Platform
v1.0
StatusDevelopment
DistributionControlled
IntegrityManifest-backed
DocumentationDevelopment
Release philosophy

A release is a defined scientific and engineering state.

Spacefield treats software releases as identifiable research and engineering states rather than as anonymous downloadable files. A release record should state what software and models are included, which interfaces are supported, what evidence has been completed and which limitations remain.

This distinction prevents confusion between exploratory research, active development, controlled validation, near-final release candidates and software that has been formally approved for production use.

Public resources will be activated progressively as documentation, licensing, intellectual-property protection, validation and distribution decisions are completed.

VersionedEvery authorised package carries a defined identity and release state.
TraceableIntegrity hashes, manifests and provenance records connect artefacts to their source.
ScopedAccess rights and scientific claims are stated for each release individually.
Release lifecycle

One controlled maturity lifecycle.

Every release state uses the same public terminology so that scientific maturity and software readiness are not confused.

01

Research

Exploratory scientific work, evolving methods and investigational software.

02

Development

Active software engineering, integration, testing and refinement.

03

Validation

A defined implementation or model undergoing controlled evaluation and benchmarking.

04

Release Candidate

A near-final frozen package undergoing final verification before formal release.

05

Production Release

A formally released, versioned package approved for its defined use and distribution model.

Current platform release

SFT Molecular Platform: current public maturity record.

The integrated platform is being prepared as the reference environment for Spacefield's molecular prediction technologies. Individual modules remain at different maturity states and should be interpreted accordingly.

Current version 1.0 Integrated platform under controlled development
Development Controlled access

SFT Molecular Platform

An integrated computational environment connecting SFT-Core, endpoint-specific prediction modules, unified reporting, single-molecule and batch workflows, machine-readable outputs and platform-level validation records.

SFT-pKa · DevelopmentSFT-logP · DevelopmentSFT-Solubility · DevelopmentSFT-BBB · DevelopmentSFT-ADMET · ResearchSFT-Binding · ValidationUnified Reporting · Development
Access note: this page records release status and planned resources. It does not grant a licence, authorise redistribution or imply that proprietary software, model artefacts or every internal release is publicly downloadable.
Release resources

Everything required to understand and use a version responsibly.

Resources are organised by purpose so that users can distinguish software access, scientific evidence, integration guidance and legal conditions.

01

Release notes

Version changes, compatibility, resolved issues, known limitations and migration guidance.

Status: Development
02

Distribution

Approved release packages, installation bundles and access instructions where distribution is authorised.

Status: Controlled
03

Documentation

Installation, architecture, configuration, reporting, workflow and troubleshooting guidance.

Status: Development
04

SDK

Programmatic interfaces, examples and integration guidance for supported environments.

Status: Development
05

API

Endpoint definitions, schemas, authentication requirements, limits and response examples.

Status: Development
06

Validation evidence

Benchmark summaries, data partitions, baseline comparisons, evaluation status and known limitations.

Status: Release-specific
07

Integrity records

SHA-256 hashes, manifests, model identities, dataset fingerprints and provenance records.

Status: Release-specific
08

Citation

Recommended software citation, persistent identifiers and linked research references when assigned.

Status: Release-specific
09

Licence

Terms governing evaluation, research use, collaboration, commercial access, redistribution and support.

Status: Release-specific
Release manifest

The evidence that defines a software release.

A complete release record connects version identity, software and model artefacts, scientific scope, validation evidence, integrity information and permitted use.

The exact contents may differ between public, private, evaluation and enterprise distributions, but the governing principle remains the same: users should be able to identify what they received and how it relates to the documented release.

Version identity

Product name, semantic version, release channel and release date.

Software identity

Package hashes, source or build reference, dependencies and supported environment.

Model identity

Model file hashes, endpoint coverage, training reference and predictor parity status.

Scientific scope

Intended use, supported inputs, endpoint definitions and explicit limitations.

Validation record

Benchmark references, authorised metrics, data partitions and evaluation status.

Access and legal record

Licence, confidentiality, redistribution, support and permitted-use conditions.

Integrity and provenance

Verify the artefact before relying on the result.

Integrity records help users confirm that a package or model has not changed since the release manifest was created.

#

Cryptographic hashes

SHA-256 values identify release archives, model artefacts, manifests and other critical files.

Content manifests

File inventories record package members, sizes and integrity information for the distributed build.

Provenance links

Release records connect software, models, benchmark reports, documentation and citation information.

Predictor parity

Where applicable, release testing confirms that packaged predictors reproduce the approved reference outputs.

Example integrity format SHA-256  [release-specific value published with the authorised package]
Release records

A permanent record of platform evolution.

Public release records will be added without overwriting earlier states. Internal checkpoints may remain part of the provenance chain without being presented as public production releases.

Development

SFT Molecular Platform v1.0

Initial unified release bringing together the principal molecular prediction modules, reporting engine and platform interfaces.

Integrated platformDocumentation preparationAccess not yet public
Internal provenance

Frozen module releases

Earlier frozen pKa, logP, solubility, BBB, ADMET, binding and core releases remain part of the internal provenance chain.

Module-specificResearch checkpointsInternal provenance
Future release records

Subsequent platform versions

Future entries will document feature changes, compatibility, benchmark updates, deprecations and migration requirements.

Version historyChangelogsMigration guidance
Access and distribution

Different releases may have different access models.

Spacefield may distribute documentation, demonstrations, evaluation packages, APIs and production software under different terms depending on scientific maturity, intellectual property and intended use.

Public

Public resources

  • Selected documentation and examples
  • Public benchmark summaries
  • Citation and version information
  • Non-confidential release notes
Evaluation

Controlled evaluation

  • Time-limited demonstrations
  • Private validation packages
  • Technical due-diligence access
  • Defined pilot-project workflows
Research

Research collaboration

  • Academic and experimental partnerships
  • Restricted datasets and shared studies
  • Joint validation and publication projects
  • Agreement-governed software access
Commercial

Commercial deployment

  • Organisation licences
  • API and SDK integration
  • Support and deployment services
  • Terms defined by contract
Scientific boundary: A software release records a defined implementation state. It does not by itself establish biological efficacy, safety, clinical validity, therapeutic suitability or regulatory acceptance. Computational outputs require appropriate independent experimental validation.
Release updates

Follow the development of the SFT Molecular Platform.

Release announcements, publication links, documentation updates and access information will be posted through the Spacefield website and official company channels when available.

Continue exploring

Research evidence, platform architecture and collaboration.

Review the scientific programme behind the platform, explore the integrated prediction environment or contact Spacefield regarding evaluation and collaboration.