Source and rights first
An asset cannot enter generation or publication without a recorded origin, rights decision and immutable content hash.
Trust model
Every claim leads back to evidence.
Manyform treats provenance, policy and review as product data—not publication copy.
Core principle
A generated image is not evidence of the event it depicts.
It is a derived training candidate whose value depends on its source, controlled transformation, realism review and measured effect on real-world evaluation.
Derived means derived
Every model-assisted edit retains its parents, recipe, model revision, seed, controls and synthetic status.
Human decisions remain visible
Reviewer identity, role, decision, reason and time are records in the lineage chain—not an overwritten flag.
Holdouts are lineage-protected
Training eligibility is denied to a protected asset and every descendant, preventing synthetic leakage from evaluation evidence.
Real evidence anchors evaluation
Synthetic and mixed results are reported separately. A validated release requires performance on a real held-out golden set.
Release has a boundary
The release gate applies to a named artifact, target and operating envelope. It never represents blanket safety certification.
Evaluation policy
Real, synthetic and mixed results stay separate.
Manyform can show whether controlled augmentation improved coverage, but the final result remains anchored to observations that the generator never inherited from the protected evaluation lineage.
Training lane
Cleared sourcesTrain split
Reviewed derivativesSynthetic marked
Candidate modelDigest pinned
lineage barrier
Evaluation lane
Protected golden setReal-only evidence
Slice resultsContext preserved
Release gateTarget-specific
Portable records
Trust should survive an export.
Manyform packages human-readable cards and machine-readable metadata so evidence can move without losing its declared purpose and provenance.
Optional integrations
Manyform stands alone and connects by contract.
Dataset and model releases remain neutral Manyform records. Named connectors can export signed manifests without changing ownership, identity or release policy.
Oddessy connector
A planned MCP and API bridge for sending verified releases to Oddessy applications, platform services and edge workflows.
Neutral API and MCP surface
Versioned datasets, models, lineage and release records use Manyform identifiers rather than ecosystem-specific names.
Outbound webhooks
Review, version and release events can notify systems of record while payload signatures preserve their source.
Explicit boundaries
What Manyform does not claim.
- Synthetic data is not automatically real-world evidence.
- Source and generator licences do not transfer silently.
- A benchmark result does not certify safe plant operation.
- Manyform does not directly write to industrial equipment.
- A release record does not replace commissioning or risk assessment.