Skip to content
How It Works

Eight stages from intake to delivery.

What happens, in order, and what would stop it at each stage.

The last stage is yours: acceptance means you ran a verification recipe against your own copy and it reproduced.

The eight stages

Intake

01 / 08

You describe the problem, volume, modality, and compliance deadline. We reply with tier and range. An NDA is in place before any data discussion.

Scope

02 / 08

A signed engagement scope pins the schema, taxonomy, acceptance criteria, and the exact instrument versions used. A GDPR Article 28 DPA is executed with it.

Transfer

03 / 08

Raw data arrives by object store, SFTP, or encrypted media. Receipt is acknowledged with a SHA-256 manifest; the processing window starts.

Validation

04 / 08

Six tiers run: structural checks, subject gate, data quality, perceptual quality, categorical assessment, consistency. Four of them gate. Failures are recorded in the refusal log.

Build

05 / 08

The dataset is constructed against the scoped schema in Lance-native format with fragment-level versioning. Every run is tracked with an audited lifecycle.

Provenance & signing

06 / 08

Four layers are attached: SHA-256 hashes, a branch-aware Merkle tree, a C2PA sidecar manifest, SLSA attestation. The signer is selected by policy; an attempt that cannot proceed raises and writes nothing.

Evidence assembly

07 / 08

The EU AI Act evidence pack (Articles 10, 11 and 12) is composed with coverage classification: fully populated, requires human input, or not applicable.

Delivery & deletion

08 / 08

You receive the four artefacts. Acceptance requires running one verification recipe successfully. Raw inputs are deleted within 30 days of acceptance.

Verification

Every deliverable includes verification recipes. Run them against your copy of the dataset:

c2patoolin-totomodel-signing

The exact commands ship inside the deliverable. Each command is tested against that deliverable before release, and acceptance requires you to run at least one successfully.

Continuity

The recipes run against external reference tools that Static Signal does not maintain: c2patool, in-toto, model-signing. If Static Signal ceased operating, the recipes in your deliverable would still run and the signatures would still verify.

Questions

What do you actually deliver?

Four artefacts: a versioned dataset, a Merkle integrity proof, a provenance bundle, and an EU AI Act evidence pack covering Articles 10, 11 and 12. Articles 9, 14 and 15 stay with the provider deploying the system. Verification recipes ship alongside them and run against tools Static Signal does not maintain: c2patool, in-toto and model-signing.

How do I know the dataset is what you say it is?

Acceptance requires running one verification recipe successfully. The recipes execute against external tools, so the check does not depend on trusting Static Signal. If it does not reproduce, it has not been delivered.

What happens to our raw data?

Raw inputs are deleted within 30 days of acceptance. Deletion on request is completed within 7 working days and returns a signed attestation. Custody is bounded by the signed engagement scope and a GDPR Article 28 DPA.

Which provenance standards do you use?

Four layers: SHA-256 content and schema fingerprints, branch-aware Merkle trees, C2PA content credentials carried as a sidecar manifest that references the dataset by hash, and SLSA v1.2 build attestations. The signer is selected by policy, not by environment; a signing attempt that cannot proceed raises and writes nothing.

What does an engagement cost and how long does it take?

Tier and range are quoted at intake against volume, modality and compliance deadline. The processing window starts when receipt of the raw data is acknowledged with a SHA-256 manifest.

What happens if the data fails validation?

Failed validation blocks the build and the refusal is recorded in the refusal log. Validation runs six tiers (structural checks, subject gate, data quality, perceptual quality, categorical assessment and consistency), four of which gate; advisory findings are recorded as advisory.