Skip to content

How it fits together

Two capture devices, one Inbox, three models that read, a private inventory in the middle, and four paths out of it, with Marketplace at the end of two of them by handoff. Around all of it, two doors. Every box in the diagram opens the page that describes it. Blue is where a model answers; a dark border is where the rules decide; a dashed box is a step you run yourself on Marketplace.

How Orphan Parts Lens fits together The phone and the computer feed the Inbox; the models read; the private inventory holds what you confirm; four paths and Find a part leave from it; the access code and the demo visitor are the two doors. Blue boxes are where a model answers, dark-bordered boxes are where the rules decide, dashed boxes are handoffs you run. a model answers the rules decide by handoff: you run it on Marketplace The phone Capture tab photos a 30-second clip a spoken note, a line The computer the Inbox's send form photos, a note, a line the label form four photos, read now Inbox captures, newest first private until read Read SAM 3.1 finds the label crop first Muse Spark reads the label into fields Muse Voice Transcribe the note, as your words My inventory private, never published values to confirm, each with its source the photos beside them what you know yourself condition and faults plan, availability Measure a feature against a ruler, with an uncertainty; no ruler, no number Catalog confirm or reject each value; add what you know Does it fit? an unknown is never a pass; it becomes a question the rules of a profile the verdict ladder Sell or give away listing draft, Muse Spark the checklist, disclosures price guidance, Muse Spark sourced comparables only the Marketplace create page, by handoff Build and reuse preferences; project templates as data proposals from Muse Spark, through tools the rules keep what the inventory allows the build pack the outcome, yours Find a part Marketplace search links, run by you a listing, read back assessed by the rules, dated The access code the live models and saving: inventory, drafts, prices, projects, captures The demo visitor the demo set's photos, recorded answers; every write refused Two doors on one deployment

The split is the whole design: Muse Spark, SAM 3.1 and Muse Voice Transcribe read, write and propose, and Muse Image draws a picture of what an item could become only when you ask; the profile's rules, the inventory and your own confirmations decide what is kept. A model never moves a candidate up the verdict ladder, never adds a line to a listing draft that no confirmed field backs, never changes a profile or a project template, and a drawn picture is never evidence. The architecture page shows the same split from the inside.

One path through: the frappé agitator

The demo set is a drawer of idle things; this is the frappé maker in it, whose agitator wore out, and the rods listed to replace it.

  1. The agitator is photographed on the phone's Capture tab beside a tape measure, with a spoken word on what is known (the base runs; the rod no longer mixes), and sent. Capture from the phone.
  2. In the web app's Inbox, Read it: there is no label to read, so the item keeps its photos and the owner's words. My inventory.
  3. Measure a feature on the side photo: two marks on the ruler, two on the rod, and the diameter comes back with its uncertainty and the method. Under Add what you know go the tab span, width and length, the rod's length, and the material wanted: metal. Measure a feature.
  4. Find a part records what the agitator needs with a top price and hands off the Marketplace search for you to run. Four listings brought back as their text are read by Muse Spark and checked by the rules of the blender_agitator profile, one at a time: the all-metal rod of the same size is a documented candidate (COMPATIBLE_LIKELY), the plastic rod fails on its material and its diameter and the metal one with wider tabs on the span (CONFLICT), and the listing with no measurements needs evidence (INSUFFICIENT_INFO). Ask the seller turns the open questions into a message. With the code, Plan the search writes the Marketplace search links and a match pattern, and listings pasted back are ranked by it before any is read. Find a part, Verdict ladder.

Another path: the homework desk

  1. The Dell U2419H and Dell 1800FP monitors, read from their rating labels, and the ThinkPad T510, opened with its keyboard off, are in the inventory with the intent use in a build. My inventory.
  2. Under Build and reuse, what you want from a build is kept once: a quiet desk for homework, low effort, a budget of 50 USD. Build and reuse.
  3. Propose: Muse Spark reads the inventory and the project templates through tools and proposes projects; the homework workstation names the 24 inch monitor and lists the laptop, the cable, the keyboard and the mouse as missing, since the T510 is not yet known to work. The rules keep only allocations the inventory backs: an item you have, usable, of a kind the requirement takes. Agent tools.
  4. Select it: the items are committed and reserved, one build per item; the budget line says what is left; the missing video cable becomes a search request with the budget left as its top price. Find a part.
  5. The build pack is one Markdown document written by the rules from what stands, with a version and a digest of its inputs, stale when an input changes. Once the desk works, the outcome in your words marks the project done. Build and reuse.

Try it

Without the access code the hosted demo lets every visitor click the demo set's photos, answers each from its recording and keeps nothing; the code opens uploads, the live models and saving. Demo access.