This site is taking shape

Enter the preview passphrase to read what is ready so far.

back to Industrialized AI

The process in detail

Industrialized AI connects manufacture, inspection, repair, and other operations as stages in a pipeline. The pipeline controls what each stage receives, records what it produces, and routes the work according to the outcome that stage records.

Manufacture, inspection, and repair are semantic stages: they use AI models to interpret source material, produce a product, assess whether it meets its requirements, and correct recorded defects. Other stages can use models to classify information, or ordinary software to calculate values, validate records, format documents, and run builds and tests. Because the pipeline's control flow is deterministic, the process remains repeatable even when the semantic work varies. Each run retains the inputs, outputs, and route taken, giving us a record we can examine afterwards.

Before the pipeline runs, a production order identifies the product to make, the requirements which apply, and the manufacturing method selected for the job. This page looks inside that execution: what each stage receives, what it hands back, and how those records let the pipeline control the complete run.

The pipeline controls how work moves between stages

If the AI machinery making or inspecting a product also decides when to stop, we've given it control of the process as well as the work. Manufacture, inspection, and repair form the core loop in a deterministic pipeline, with any other required stages placed before, after, or between them. The pipeline supplies each stage with recorded inputs and follows its recorded outcome, including routing a repaired product back toward inspection. The assigned models can still make the product, record inspection observations, and correct defects; they don't set the acceptance rules or decide what happens next.

Before work begins, we record the criteria and inspection methods used to judge a product; together they form its acceptance basis.

Follow the records through one repair An example run. These record labels appear in the stage details below.
  1. Manufacture

    Receives

    The assignment, source material, product requirements, and manufacturing method.

    Records
    • product-r001
    • production-001

    The first product revision and a record of how it was made.

    Pipeline routeRevision produced: send it to inspection.

  2. Inspect

    Receives
    • product-r001

    With the source material, acceptance basis, and any supporting stage results.

    Records
    • inspection-001
    • defect-001

    A required check found a defect that prevents release, with evidence and a correction required.

    Pipeline routeRepair required: send the rejected revision and its findings to repair if another attempt is allowed within the agreed limits.

  3. Repair

    Receives
    • product-r001
    • inspection-001
    • defect-001

    With the source material, acceptance basis, and permitted edit scope.

    Records
    • product-r002
    • repair-001

    A replacement revision and a record of what changed. The earlier records remain unchanged.

    Pipeline routeReplacement produced: send the new revision back to inspection, not to release.

  4. Reinspect

    Receives
    • product-r002
    • defect-001

    With the source material, acceptance basis, and any supporting stage results.

    Records
    • inspection-002

    The defect is recorded as resolved, required checks are complete, and the product passed inspection.

    Pipeline routePass recorded: check that the product, supporting information, and acceptance basis match the passing inspection.

Release the matching revision

release-001 links product-r002 to its passing inspection-002 and the run's earlier records.

Repair is conditional: a first-pass result skips it. An incomplete required inspection blocks release. If another attempt is needed but the retry or repair limit has been reached, the pipeline stops without release.

Before the pipeline can manufacture or inspect a product, it needs an explicit acceptance basis.

Tolerance defines what is acceptable for this product

Manufacturing works at scale because every part doesn't have to be identical; it has to satisfy its specification within limits set for the job. Those limits make it possible to use made-to-spec parts with confidence. Cognitive products need the same freedom: two reports can use different wording and both be acceptable, while an unsupported conclusion can put either one outside tolerance.

We start by naming a characteristic of the product which inspection can examine. A requirement states what that characteristic must satisfy, while tolerance defines how much variation is permitted. A finding outside that tolerance blocks release. The requirement and tolerance applied to one characteristic form an acceptance criterion; the complete set of criteria and inspection methods is the product's acceptance basis.

This isn't left as a general instruction such as “production quality.” Each characteristic reaches inspection with a stable identity, its requirement, whether it applies, the permitted variation, and the method used to assess it. A tighter tolerance can make the same finding block release, but the selected tolerances are recorded before the run and aren't changed by the inspecting model.

One acceptance criterion
PartWhat it records
CharacteristicThe aspect of the product being examined, with a stable identity.
RequirementThe condition that characteristic must satisfy.
ToleranceThe variation permitted for that characteristic.
Inspection methodHow inspection should establish whether the requirement has been satisfied.

Manufacture needs both a product assignment and a method

The product assignment describes what manufacture is expected to produce: the product's intended use, the source material it may rely on, the required characteristics, and the boundary within which the stage may work. Those requirements belong to the product, so changing the machinery or instructions does not quietly change the standard the result must meet.

The manufacturing method describes how the stage will attempt the work. It identifies the instructions, model or other machinery, tools and permissions, operating conditions, resource limits, known limitations, and the output the stage must return. A different method may be faster, cheaper, or more likely to produce an acceptable first revision; it still manufactures the product defined by the assignment.

Manufacture receives the applicable requirements so it knows what it is trying to make, but it does not decide whether its own result is acceptable or which failures would prevent release. When the stage finishes, the production record identifies the product revision it made and records what actually happened during that attempt. Other stages may then transform or validate the product before inspection; if one of them changes it, inspection receives the resulting revision rather than the original manufacturing output.

Production record · production-001
Assignment
The product to make, its intended use, and the stage's permitted write scope.Sets the boundary of the manufacturing operation.
Source material
The recorded source material made available to manufacture.Defines the information the product may rely on; the observed work records which material the stage actually read.
Product requirements
The applicable characteristics and requirements the manufactured product is expected to satisfy.Gives the stage a definite target without asking it to apply the tolerance or decide whether its own work passes.
Manufacturing method
The method's identity and version, instructions, model or other machinery and its configuration, tools, permissions, operating conditions, resource limits, known limitations, and required output format.Records how the stage was configured to attempt this operation.
Observed work
The model and configuration used, material actually read, resources consumed, and effects observed.Distinguishes the work performed from the work assigned.
Produced revision
product-r001; manufacture completed, awaiting inspection.Links the stored product revision and its content digest to the production record so inspection can identify the manufactured content.

Inspection checks the product we actually made

Manufacture has produced a product, but we still need to establish whether the product meets its acceptance basis. Inspection receives a specific product revision, together with the characteristics and requirements the product must satisfy and the source material needed to make those judgments. The inspecting model examines the product revision and records what it finds for each characteristic, including the supporting evidence and whether the requirement is satisfied, unsatisfied, or unresolved. Results from other stages, such as tests, calculations, or record validation, can also be supplied as supporting information.

Tolerance lets us specify which defects are acceptable for a particular product. A defect records where a characteristic has failed to meet its requirement; depending on the declared tolerance, the defect may be recorded without preventing release or may block release until the defect is corrected.

Manufacture, inspection, or repair may uncover a defect in the source material, such as missing evidence or conflicting information. The process records the defect and applies the declared tolerance to determine whether work can continue or must stop.

How tolerance changes the decision for the same product
CharacteristicRequirementProduct conditionToleranceInspection recordsDeterministic result
Source coverage Every applicable point in the source material is represented in the product. One source point is missing. Omissions are permitted. Unsatisfied: the missing point is recorded, but falls within tolerance. The product may pass with the finding retained.
No omissions are permitted. Unsatisfied: the missing point falls outside tolerance. The defect blocks release and requires repair.

The pipeline checks that the assessments are attached to the correct product version, that the cited evidence identifies recorded source material or supporting results, and that an assessment has been supplied for every required characteristic.1 It then applies the decision table to the assessments, supporting results, coverage, and recorded tolerances. The recorded decision is called the disposition: pass, repair required, or unable to complete. The same recorded assessments, supporting results, coverage, and tolerances produce the same decision.

Once every required check has a recorded assessment, the pipeline sends defects that prevent release for repair before stopping for checks that remain unresolved. An unresolved check may depend on a requirement that failed, so correcting that defect can make it possible to assess the dependent check when inspection runs again. If a check needed for release remains unresolved and no defect that prevents release is left to repair, the pipeline stops.

How the decision table determines the disposition
ConditionDisposition
A required check has no assessment, or a check needed for release remains unresolved and there is no defect that prevents release left to repair.Unable to complete
Every required check has an assessment, and at least one defect falls outside the permitted tolerance.Repair required
Every required check has an assessment, and none records a failure or unresolved condition that prevents release.Pass

The decision table applies the rules consistently, but its result still depends on the accuracy of the assessments it receives. Testing and monitoring the inspection method is part of developing and maintaining the production process.

Inspection record · inspection-001
Product under inspection
product-r001.The stored product revision being checked, including its content digest.
Supporting information
The recorded source material needed to judge the product.The source material is kept separate from the product being inspected.
Acceptance basis
The applicable characteristics, requirements, tolerances, and inspection methods.The acceptance basis records the standard against which the product is inspected.
Semantic assessments
Observations tied to a characteristic, a location in the product, and supporting evidence.The model records whether the requirement is satisfied, unsatisfied, or unresolved; the model does not decide the disposition.
Other stage results
Measurements and results supplied by test, build, validation, or other stages.Inspection considers these results alongside the semantic assessments.
Coverage
The characteristics and relevant parts of the product actually inspected, including anything that could not be assessed.If a required characteristic was not assessed, inspection is incomplete.
Defects
defect-001: the affected product revision, unsatisfied requirement, product location, evidence, and correction required.Creates a precise input for repair when a finding falls outside tolerance.
Disposition
Pass, repair required, or unable to complete.The pipeline applies the deterministic decision table to the assessments, results, coverage, and recorded tolerance, then records the disposition for routing.

The pipeline uses this record to route the product and supply the next stage's inputs.

Repair needs to know what failed and why

Repair receives the rejected product revision, the recorded defect, and the source material used to manufacture the product. Repair uses the source material to check the correction against the information the product was meant to rely on, rather than rewriting only the part inspection flagged. The inspection record also shows which requirements were satisfied, so repair can concentrate on the defect without losing work that was already sound. A record saying only “failed inspection” would force repair to rediscover the problem before making the correction.

Repair produces a new revision of the rejected product and records what changed. The rejected product revision and failed inspection remain unchanged. Other stages may process the repaired product before reinspection. If another stage changes the product, inspection receives the resulting product revision.

Repair record · repair-001
Product under repair
product-r001.The rejected product revision repair uses to produce a replacement.
Failed inspection
inspection-001.Shows what was checked and which requirements were satisfied or unsatisfied.
Defect to correct
defect-001.Identifies what failed, the evidence behind the finding, and the correction required.
Supporting information
The recorded source material needed to make and check the correction.Repair uses the recorded source material the product was meant to rely on.
Acceptance basis
The characteristics, requirements, tolerances, and inspection methods the replacement must still satisfy.Repair must preserve parts of the product that were already acceptable as well as correct the assigned defects.
Permitted edit scope
The parts of the product this repair attempt may change.The repair stage produces a new revision; it cannot alter its source material or earlier process records.
Observed work
The model and configuration used, material actually read, and changes observed.Records what the stage changed, not merely what it was asked to change.
Produced revision
product-r002; repair completed, awaiting reinspection.Identifies the stored repaired product revision and its content digest for reinspection.

After any intervening stages have run, inspection receives the resulting product revision. Inspection must establish that repair corrected the defect without introducing another problem; the defect remains open until inspection verifies the repaired product revision.

The pipeline runs the loop and controls release

The pipeline doesn't ask a model what to do next. The pipeline reads the recorded outcome from the current stage and follows a route defined before the run. The declared route determines which product revision and records the next stage receives.

How the pipeline routes recorded outcomes
Stage recordsPipeline does
Manufacture produced a revision.Pass the recorded product revision and production record into the declared inputs of the next stage.
Another stage completed.Pass the recorded outputs into the declared inputs of the next stage.
Inspection passed.Follow the accepted route toward release, carrying the inspected product revision and its evidence.
Inspection requires repair.Follow the repair route with the inspected product revision, failed inspection, defect, supporting information, and acceptance basis.
Repair produced a replacement.Follow the declared route back toward inspection.
A stage cannot complete.Follow the declared retry or stop rule; release nothing.

Records from manufacture, inspection, repair, and any intervening stages are linked to the product versions they concern. Those links let us follow a product from source material to release, see why each repair was needed, and identify which version passed inspection.

When inspection records a pass, the pipeline confirms that the product revision, supporting information, and acceptance basis match the versions recorded by the passing inspection. If the product revision, supporting information, or acceptance basis has changed, the passing inspection no longer applies and the product must be inspected again. Otherwise, the product revision which passed can be released.

Reinspection record · inspection-002
Product under inspection
product-r002.The stored repaired product revision and its content digest.
Supporting information
The recorded source material and other stage results needed to judge the repaired product.Inspection uses the supporting information recorded for this inspection.
Acceptance basis
The complete set of applicable characteristics, requirements, tolerances, and inspection methods.Inspection applies the acceptance basis recorded for product-r002.
Assessments and coverage
Semantic assessments, deterministic results, and coverage recorded for product-r002.The record shows what inspection found and which required checks it completed.
Defect status
defect-001: resolved or still present, with supporting evidence.Reinspection determines whether the attempted correction worked.
Disposition
Pass, repair required, or unable to complete.The pipeline follows the disposition recorded by reinspection.
Release record · release-001
Released product
product-r002.The stored product revision and content digest made available for use.
Acceptance
inspection-002 passed product-r002.Links the passing inspection to the product revision released.
Evidence
The recorded assignment, source material, acceptance basis, and any intervening stage records, together with production-001, inspection-001, defect-001, repair-001, and inspection-002.Links manufacture, failed inspection, repair, and passing reinspection into one examinable run.

The process delivers an accepted product together with the evidence showing how it was made, checked, and corrected.

The runnable example shows how the loop, records, and evidence links are expressed in a working system.

Notes and references

  1. Mistake-proofing, or poka-yoke, builds prevention or immediate detection of particular errors into the process. The approach was formalized by Shigeo Shingo. Requiring complete assessments tied to the correct product revision applies that principle here: the pipeline can block these specific mistakes automatically, while the accuracy of the assessments still needs testing. Back to text