Workshop
In plain words: App: Workshop (vehicle service cases)
A candidate app for guided repair diagnosis, starting with car service (the proposed 'Mechanic' product): it keeps the vehicle, symptoms, hypotheses, checks and results together until a scoped outcome or handoff.
- 1The flow: identify asset, triage hazards, revise hypotheses, request one discriminating check, record result.
- 2Cannot certify safety, control machines, invent part identities, purchase or pay.
- 3The legacy workshop code scaffold is inert and no precedent for new stubs.
Designed Candidate study outside the accepted app list.
Words on this page, decoded click one for its card
An intermittent no-start complaint is a service case before it is a diagnosis. Workshop would keep the exact vehicle, reported symptom, sources, competing hypotheses, requested checks, and observed results together until the evidence supports a scoped disposition—or makes a qualified handoff the useful result.
This candidate study, reviewed 2026-08-09, tests that reusable application boundary. Workshop is outside the accepted Portfolio; Mechanic is its proposed first ProductPackaged Offer using the passenger-vehicle service profile. State of Work retains the delivery boundary.
Candidate contract
workshop.service revision 1 proposes workshop.service_case@1. Its WorkshopServiceRequest@1 binds purpose, case-scoped asset identity/configuration evidence, condition, hazards, operator role, pinned service profile, attributed sources/observations, and privacy/authority ceilings.
The proposed WorkshopServiceCase@1 keeps the work reconstructible after the conversation. It owns purpose and operator assignment, asset assurance, and the evidence available to the case: symptoms, manuals, bulletins, schematics, codes, images, statements and measurements. It also retains hypotheses and contradictions; checks, prerequisites, hazards, tools, results and interruptions; part/tool requirements; and verification scope. A hypothesis remains distinct from an observed fact, and chat cannot substitute for this record.
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.
Neither this study nor the inert legacy src/lychd/compositions/workshop/ scaffold supplies a schema, service, registry contribution, PatternWorkflow, effect path, or delivery evidence. The scaffold is no precedent for new candidate stubs.
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 CompositionApp.
A ProductPackaged Offer 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.
Proposed reuse beneath the Product
Workshop can use existing mechanisms while retaining the purpose and policy of the service case. Companion, EchoVoice, Tether, and WardSecurity Desk keep mobile controls, speech chronology, transport, authentication, grants, and revocation. ScoutWeb Fetcher 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's typed requests, part needs, and dispositions remain its proposed projections, not new Core primitives. Products and Suites explains settled handoffs versus 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 network-disabled synthetic passenger-vehicle fixture must include conflicting identity, a pinned manual excerpt, finite images, codes/measurements, and fake stock. It proves refusal and source mismatch, one parked/resumed check without duplication, Sight uncertainty, hypothesis revision, hazardous-work handoff, a part need without purchase, scoped verification, and interruption without invented completion. No live vehicle, public web, camera stream, purchase, actuator, or repair enters it.