Register — CRSET 0001 · Status: open · Pricing: verified · Boundaries: published
Machine 001 — Document extraction
Start with a concrete extraction kit. Extend into a bounded implementation, or diagnose reliability and delivery risk across your data stack.
Verification index — open
Nothing here is a promise. Each entry carries a record: the claim, the proof, the method, the source. Prices are verified against live checkout; boundaries and specimens are labelled as what they are.
Claim
The kit costs €79, one payment. No subscription, no per-page meter. The kit price is credited against a fixed-scope pilot.
Proof
Price and credit chain are published in the canonical offer data and the checkout resolves to a live Stripe payment link.
Claim
The pilot runs on a €450 deposit. Total scope is bounded: €1.5k–3.5k.
Proof
Amount published on the storefront and checked against the live Stripe checkout link before publication.
Claim
The data stack audit runs on a €750 deposit. Total scope is bounded: €1.5k–3k.
Proof
Amount published on the storefront and checked against the live Stripe checkout link before publication.
Claim
Full implementations are scope-bound, not a single fixed figure: the pilot runs €1.5k–3.5k, the audit runs €1.5k–3k. There is no fixed quote without a written scope; the final figure is set in the scoped proposal.
Proof
The ranges are the published entry boundaries in the canonical offer data, one per service; they are deliberately not a fixed quote.
Claim
Extraction runs locally through an MLX runtime on the customer's own Mac; documents do not leave the machine for inference.
Proof
Published as the kit's operating specification in the canonical offer data. Not an independently re-run benchmark from this page.
Claim
The kit ships with four validated extraction profiles covering the four document classes listed here.
Proof
Profiles and their coverage are published in the canonical offer data as the kit's specification.
Claim
The extraction workbench on this page shows one invoice read into structured output with a human verification step.
Proof
Representative specimen rendered on this page. It is an example, not customer proof, and not a guarantee for your files.
Claim
The pilot specification requires human verification of extracted output before it becomes operational data.
Proof
Published as an operating constraint in the canonical pilot offer: local extraction, human verification, structured output.
Machine 001 — Document extraction
4 fields read from purchase-order.pdf by Local MLX runtime — human gate on the required-field check.
See the full specimen record on Products →02 / Services
Use IMPLEMENT when a bounded document workflow is ready to build. Use DIAGNOSE when the system and its risks need to be understood first.
A document workflow is defined and needs a bounded implementation.
Data infrastructure, reliability, or delivery risk needs an evidence-first review.
A scoped pilot for one document workflow using local extraction, human verification, and structured operational output.
An evidence-first review of pipelines, warehouse quality, observability, cost, and delivery risk.
Supported deliverables
Data Stack Audit
Method
03 / Evidence
Commercial boundaries are verified; workflow and output specimens are representative.
The package manifest identifies the four included parts.
One payment covers the Document Extraction Starter Kit.
Published deposits and expected totals define the commercial range for each service.
The workbench and structured output illustrate the supported extraction pattern; they are not customer proof.