Workshop
An intermittent no-start complaint is a service case before it is a diagnosis. Workshop keeps the exact vehicle, reported symptom, sources, competing hypotheses, requested checks, and observed results together. The case can end with verified restoration under stated conditions or with a handoff that tells the next qualified person where the evidence stopped.
Workshop is the technical-service Composition. Mechanic, its first Product design, selects the passenger-vehicle service profile. The package contains only a namespace docstring. The case store, guided checks, and Product entry point await implementation. State of Work records delivery.
Service-case contract
workshop.service revision 1 defines the Pattern workshop.service_case@1. Its WorkshopServiceRequest@1 binds the purpose, case-scoped evidence of asset identity and configuration, condition, hazards, operator role, pinned service profile, attributed sources and observations, and limits on access and action.
WorkshopServiceCase@1 keeps the work reconstructible after the conversation. It records the purpose, assigned operator, and grounds for identifying the asset. It preserves symptoms, manuals, bulletins, schematics, codes, images, statements and measurements with their sources. Observations and hypotheses remain distinct. For each hypothesis, the case keeps contrary evidence and the checks that could distinguish it from another explanation. Each check records its prerequisites, hazards, tool and part requirements, result or interruption, and verification scope.
WorkshopServiceDisposition@1 can return scoped verified restoration, containment advice or attributable containment evidence, professional handoff, exact blocker, unresolved result, refusal, or indeterminate action. It cannot certify a machine generally safe, perform statutory inspection, admit unsafe/unqualified work, control a machine, bypass guards, invent part identity, purchase, or pay. Emergency response is outside this office.
The guided case
identify asset → triage hazards → admit evidence → revise hypotheses
→ request one discriminating check → wait for the operator → record the result
→ verify, advise containment, block, refuse, or hand off
The operator opens the no-start case from a phone, deliberately speaks through push-to-talk, and attaches a code report and finite images. Work may continue through a headset while retaining the same case. Workshop pins configuration and applicable source release, then proposes one non-invasive, engine-off inspection with reason, prerequisites, and stop conditions. Its reported result remains an attributed observation. Conflicting evidence can end in a qualified handoff instead of another speculative repair.
Sight may nominate a connector region, and a phone or future glasses may show it. The estimate proves no component identity, cause, or action safety. Silence, “seems fine,” unseen repair, and missing acknowledgement cannot close the case.
Revision one guides no lifting/support, exposed high voltage or hazardous energy, energized/rotating machinery, pressurized/combustible material, pyrotechnics, primary vehicle controls, or guard/interlock defeat. It can organize evidence for qualified help. Consent does not create competence; local inference retains access, retention, deletion, and workplace privacy duties.
If the phone disconnects after a check is requested, the case parks that exact check. On return, the assigned operator can see what was requested, which precautions applied and whether a result was recorded. If execution is uncertain, record the uncertainty and seek attributable evidence before any further action. Resuming through the headset cannot issue the check a second time.
One workshop, versioned practices
WorkshopServiceProfile@1 pins ontology, identity/compatibility keys, acceptable sources, checks, units, tools, qualifications, hazards, verification recipes, and stop rules. The first is workshop.automotive_passenger revision 1. Another trade may use a profile only while the same service-case records, authority, recovery, and honest finish remain coherent. A materially different trade boundary needs another Composition.
A Product selects profiles/use cases; a client changes presentation; a Persona changes discourse and commitments; a Posture changes a cognitive step. None owns technical or safety law.
Handoffs and supporting mechanisms
Workshop can use existing mechanisms while retaining the purpose and policy of the service case. Companion, Echo, Tether, and Ward keep mobile controls, speech chronology, transport, authentication, grants, and revocation. Scout and Sight provide acquisition/visual evidence; Workshop decides whether that source applies and which check may follow. When parts need sourcing, Scavenger keeps its own listing, seller, bargaining, commitment, payment, and parcel records.
WorkshopPartRequirement@1 carries compatibility, quantity, condition, certification, and evidence needs to stock or Scavenger, without reservation or commitment authority. A stock owner can return exact snapshots and reservation/use/return receipts. Workshop records them; it cannot mutate ambient inventory.
An asset owner such as Homestead may supply the request and consume the disposition while retaining its site, work order, controller envelope, and return-to-service authority. Workshop owns the typed service request, part need, and disposition used at these handoffs. Products and Suites explains settled handoffs and live coordination.
Honest settlement
Close the case only as far as its evidence permits. Verified restoration means the case-defined symptom and checks passed under recorded conditions. If the useful result is containment advice, keep it as advice; evidence of actual containment must name the human/controller and independent verification. A handoff carries identity, evidence, attempted checks, uncertainty, and hazards to the next responsible person.
When identity, source, observation, tool, part, qualification, or authority is missing, return that exact blocker. Conflicts and exhausted budget remain unresolved. An uncertain action stays indeterminate and must not be repeated.
The first qualification fixture requires a synthetic passenger vehicle, conflicting identity evidence, a pinned manual excerpt, finite images, codes and measurements, and fake stock. With the network disabled, it must demonstrate refusal on source mismatch, a parked check resumed without duplication, Sight uncertainty, hypothesis revision, hazardous-work handoff, a part need without purchase, scoped verification, and interruption without invented completion. The fixture excludes live vehicles, the public web, camera streams, purchases, actuators and repairs.