Solution · Manufacturing
Convilyn Quality Inspection Report Agent
Handwritten check sheets, gauge output and photos become the report your customer's template asks for. Measured values are transcribed, never rewritten; out-of-spec characteristics and unreadable entries are flagged for a person.
Requirement confirmed
Fast delivery
Continuous security
How adoption works
Three phases, each ending in something you can sign off
An adoption project fails on scope, not on models. Each phase below closes with a written artefact, so the next one starts from an agreement rather than an assumption.
Requirement confirmed
We inventory the documents and systems already in use, agree which fields matter and how each is read, and draw the line where a person reviews rather than the workflow decides.
Output of this phaseA written scope note naming every field, every reading rule, and every human checkpoint.
Fast delivery
The workflow is assembled from generic platform tools rather than built for one customer. Real sample documents run first, and volume follows once the sample set is clean.
Output of this phaseA running workflow on real sample documents, with the cost per run measured before scale-up.
Continuous security
Every run leaves a tool-invocation record. Retention windows, deletion behaviour and the sub-processor list are published pages that a security reviewer can check without asking us.
Output of this phaseAn audit trail per run, and a documented retention, deletion and sub-processor position.
Scope of the exchange
What you hand over, and what comes back
An inspection-report engagement is scoped by the record formats on your line and the template your customer mandates. Both are named here before any work starts.
- Your organisation providesInspection records exactly as they exist on the line — handwritten check sheets, gauge printouts, or phone photos of either.Convilyn deliversEvery characteristic read out, with each value carrying the record and page it came from.
- Your organisation providesThe report template your customer mandates, in the Excel or Word file they sent you.Convilyn deliversThat template's real cells read and filled in place, with its layout, formatting and header block preserved.
- Your organisation providesUpper and lower limits per characteristic, and the rule for a borderline reading.Convilyn deliversLimits applied per characteristic, out-of-spec items flagged, and borderline readings surfaced rather than quietly rounded into tolerance.
- Your organisation providesMaterial certificates, appearance photos, and anything else the shipping pack has to carry.Convilyn deliversOne shipping document pack with the attachments merged in, and a missing-item list checked against your pack definition.
- Your organisation providesThe quality engineer who signs the report, and the point at which they sign.Convilyn deliversA tool-call record for every run. The final disposition stays with the quality engineer.
From the binder that comes off the line to a report the customer accepts
The same lot, two routes. The manual path re-types measurements between a paper form and a customer template; the Convilyn path keeps every value anchored to the record it came from and routes the judgement back to quality.
Manual workflow07 steps
Collect the inspection records
Re-type every measurement
Values are copied from paper into a spreadsheet by hand. This is the step where a decimal point moves.
Look up the limits
Judge each characteristic
Pass or fail decided row by row, with borderline readings settled from memory of the last lot.
Hunt down the attachments
Lay it out again in the customer's template(this step no longer happens)
Every customer wants a different form, so the same data is typed a second time into their layout.
Chase the missing items and the signature(this step no longer happens)
Shipping waits while somebody works out what is still outstanding.
Convilyn workflow05 steps
Upload the records and the template
Check sheets, gauge output and photos, together with the report template your customer requires.
Each characteristic is read out
Character-level OCR text is the authority for every measured value, date and lot number. Nothing is rounded, reformatted or restated.
Limits applied, gaps exposed
Out-of-spec characteristics are flagged, missing entries listed, and anything unreadable is returned for a person rather than guessed.
Filled into the customer's template
The template's real cells are read and filled in place, so its layout, formatting and header block survive intact.
Quality confirms and signs
The final judgement stays with the quality engineer. Each confirmation or override is logged with the run.
Expected result
One lot, end to end
The same lot, from the binder that comes off the line to the pack that ships with it.
Worked example
A lot closes with a six-page handwritten check sheet covering 32 characteristics, a gauge printout in a different unit from the drawing, and a customer report template that has its own header block and column order.
Input
- A six-page handwritten check sheet, 32 characteristics
- Gauge output recorded in a different unit from the drawing
- Appearance photos named by operator rather than by characteristic
Deliverable
- The customer's own report template, filled in place with its layout intact
- Out-of-spec characteristics flagged, and unreadable entries returned for a person
- One shipping document pack with certificates and appearance photos merged in
What to measure
- Time from lot close to a report the customer accepts
- Measured values re-keyed by hand per lot
- Reports returned by the customer for a format problem or a missing item
- Time to assemble evidence when an audit asks about a past lot
System integration
Build once, call the same workflow from the web, the API or an SDK
A workflow is built once in Builder. All three call surfaces point at that one workflow, not three copies to keep in step.
In
- Direct upload
- Google Drive
- Dropbox
- URL import
- Dedicated inbox
Workflow substrate
- Excel
- Word
- JSON
Out
Call surfaces
Web interface, REST · Python SDK · TypeScript SDK. Agent workflows stream events over WebSocket; deterministic conversion is polled.
Where it runs
Workflows run in the cloud. Ainalyn for desktop (beta) handles image, PDF and OCR conversion on the machine; convilyn.local converts offline with no key and no network.
Your own tools
You can host a tool server and have the platform call into it. Every outbound request carries a HMAC-SHA256 signature and a timestamp, so you can verify it came from us.
URL import accepts https only, does not follow redirects, refuses addresses that resolve to internal ranges, and has a size limit. Download links are short-lived presigned URLs and can be reissued.
Why Convilyn
The substrate is ours, and the guarantees are checkable
Document automation projects stall at security review. Every item in this section can be checked before you talk to us.
Decision boundary
Eight gates decide in code, against fixed thresholds, in a fixed order. A model cannot skip one, and cannot argue a threshold up.
- RedactionSensitive content is masked before it reaches a model.
- Budget ceilingA per-request spend cap. Work stops at the limit.
- Retry policyFixed backoff, so a rate limit never becomes a stampede.
- Phase legalityA tool runs only in the phase the workflow allows.
- Cycle detectionThe same call repeated in a row aborts the run.
- Output reject limitThree rejected outputs and the run stops retrying.
- Tool permissionWriting to an outside system needs granted authority.
- Code rescue admissionWhether a code rescue may run is configuration, not a judgement.
Extraction is held to the same kind of rule: a field the source does not contain is left empty. A grounded blank is the correct answer; an invented value is not.
Privacy is the default, not a setting to find
Model providers do not train on your content. Runs started with an API key are excluded from Convilyn's own model work in code, and fail closed — a refusal by default, not a policy statement.
Integration flexibility, because the constraint is usually on your side
The interfaces are listed above. The other half of that commitment is this: if a requirement is beyond us, we say so during the assessment rather than at go-live.
Model training
Inputs and outputs sent through AWS Bedrock are not used to train Anthropic's models (see Bedrock's data protection terms). Runs started with an API key are excluded from Convilyn's training data, enforced in code.
Deletion
Files can be deleted immediately through the API, by the uploader only. A file attached to a running workflow is protected until that run reaches a terminal state.
Encryption and isolation
TLS in transit, encrypted at rest. Storage paths are isolated per account and every read and delete checks ownership — guessing an identifier does not reach another account's file.
Redaction
Rules match on field name and value shape, so content inside fields like resume_text is caught too. It does not rely on a model to judge what is sensitive.
Sub-processors and DPA
Every sub-processor handling customer content is listed publicly. Enterprise customers can sign a DPA, are notified when a sub-processor changes, and can object.
Retention
- 1 hourSource files and download links
- 7 daysWorkflow run state
- 30 daysDeliverables
The cleanup pass runs every 15 minutes, which is why the shortest horizon is about an hour rather than exactly one. A file still attached to a running workflow is kept until that run finishes. Any file can be deleted immediately through the API.
Processing regions are fixed today: file storage and workflow execution in Tokyo (ap-northeast-1), model inference in us-east-1, and OCR in Singapore (ap-southeast-1). The region cannot be selected per request. Raise a data-residency requirement during the assessment and we will say plainly what is and is not possible.
Common questions
Questions that come up before a rollout
How long does a rollout take?
It scales with how many record formats and customer templates are in scope, not with how many lots you run. One line's check sheet and one customer's template are usually working within the first delivery pass, and each additional template is an incremental step on top of a workflow that already runs.
Do we have to change the line or our quality system?
No. Records are photographed or scanned exactly as they already exist, and the report comes back in the template your customer mandates. Nothing on the line changes. If you want the step connected to a system you already run, the REST API and the Python and TypeScript SDKs are available.
Will our drawings and inspection data be used to train a model?
No. Drawings and inspection data never become training data — not for the model provider, and not for us.
What happens when a measurement is read wrong?
Measured values are transcribed from the record and never recalculated or rounded. Anything the character-level read cannot resolve is returned for a person instead of being guessed, and an out-of-spec characteristic is flagged rather than settled. The final judgement stays with the quality engineer.
How do we start?
A few real batches of inspection sheets, plus the report template one of your customers specifies.
Start with one line and one customer
The assessment comes back as a written scope statement naming the characteristics, the limit rules and the QA review points. No charge.
Book an adoption assessment