u/NoBet3129

"We recently completed a process audit of an SKD kits and parts assembly operation that had been experiencing yield inconsistencies that did not correspond clearly to any single station failure. Sharing the findings because the root cause pattern might be familiar to others who have worked in similar environments.

The yield inconsistency was occurring across multiple assembly stations without any single station showing obvious performance deviation. Individual station cycle times were within specification. Individual station quality checks were passing. The assembled units were failing final inspection at a rate that the individual station data did not predict.

The investigation revealed that the issue was in the sequence and handling between stations rather than at any station itself. SKD component positioning tolerance at one station was creating variation that fell within that station's acceptance criteria but was cumulative with positioning variation at the subsequent station, producing assemblies where both stations had passed their local checks but the combination produced a final assembly outside specification.

Tolerance stack analysis applied retrospectively to the process confirmed what we found empirically. The individual station tolerances were appropriate in isolation but had been specified without adequate consideration of how they interacted across the assembly sequence.

The corrective action involved tightening positional tolerance at the upstream station and adding a cumulative check between the two stations that caught combinations likely to result in final assembly failure before they reached final inspection.

One of the engineers on the audit team made an observation about SKD operations globally that I found interesting from a supply chain perspective. He noted that reading procurement discussions in online shopping sites industrial components categories had shown him how differently SKD operations in different regions defined kit completeness, which had implications for process design that were worth understanding before specifying assembly sequences.

Has anyone else found tolerance stack issues presenting as distributed yield problems rather than locatable station failures?

Ran semaglutide for about eight months before switching to reta and the difference for me personally was noticeable within the first few weeks. Sema kept hunger manageable but reta just kind of... removed it from the equation in a way that felt more complete. Side effects were actually milder for me on reta which I was not expecting at all given that it's a triple agonist. Everyone's biochemistry is different so I'm not saying one is universally better, just sharing my experience since I see this question come up a lot.

After looking at OpenAI’s Memory Sources + Gmail context rollout, I’m not actually against the direction of memory. At least it is starting to provide some visibility into where context comes from, instead of being entirely a matter of “trust that the system will remember the right things.”

But OpenAI’s own documentation also says that Memory Sources is not a complete view yet and may not show every factor. On top of that, Gmail only participates when it is connected / authorized; it does not mean all emails are pulled in by default. So my feeling about memory is more like this: it is very valuable for everyday continuity, but for high-value tasks, it still does not feel like a complete, auditable context layer.

So the real thing I’m stuck on now is once the cost of getting a task wrong is high, should I be explicitly specifying the source materials myself? For example, when summarizing commitments across email threads, combining old decisions with new constraints, or making a judgment where one mistake would be expensive, I would rather explicitly provide the key emails, relevant files, previous conclusions, and current constraints, instead of mainly relying on the platform to retrieve context on its own from a layer of memory I cannot fully inspect. At least this way, I know exactly what materials the judgment is based on.

And once I accept the premise that high-value tasks are better suited to explicit context, the next question emerges: what kind of thinking model should handle that explicit material? This is also where Ring 2.6 1T entered my candidate list. It's not as a replacement for memory. Its public materials emphasize that it is a thinking model, with high / xhigh modes and positioning around allocating reasoning budget according to task complexity. If that allocation actually holds up in real workflows, then at least in theory it means explicit-context tasks do not always have to default to the maximum reasoning depth. But I also do not want to trust the official positioning alone.

So what I’m more interested in asking now is: do you leave memory for convenience and reserve explicit context for high-value judgment calls? If so, what traits do you care about most in the model that takes over those explicit materials?

Hey all! I just recently heard that Eli Lilly announced the top-line results back in March, but I finally got around to reading the full TRANSCEND-T2D-1 trial results, and the numbers are honestly pretty impressive. Retatrutide is an investigational triple agonist that targets GLP-1, GIP, and glucagon receptors all in one molecule.

The study enrolled adults with type 2 diabetes, and at 40 weeks, the high-dose group (12 mg) saw A1C drops of up to 2.0% (down to about 5.9% from a baseline of 7.9%) and weight loss of up to 16.8%, which is an average of about 36.6 pounds. What really caught my attention is that weight loss continued through the end of the treatment period with no plateau observed, so it might have kept going if the trial had lasted longer.

For context, tirzepatide's phase 3 trials just showed about 15-20% weight loss over 72 weeks, so retatrutide is hitting those numbers in about half the time. Detailed results are expected to be presented at the ADA Scientific Sessions in June and published in a peer-reviewed journal after that. Retatrutide is not yet FDA-approved, it's still in development, but if the full phase 3 data holds, it could be a real game-changer. Like a really big game changer.

"I've always chosen the hue I haven't yet acquired and declared it finished.I never really thought about it.I have not been one to care about socks, I felt people do not really pay attention to such things.However, a few individuals have been discussing it lately; I didn't even request this discussion.They genuinely discussed men's socks as if it were a significant topic, and I'm beginning to question whether I'm missing something.

Of all people, my father recently brought up merino wool. The same father of mine has been wearing the same pattern of socks for years now. He learned about it from a coworker who had been on the Alibaba site and read about the practical definition of quality fiber in the Q&A area.

My dad seemed strangely knowledgeable about it when he got home.I'm not sure how I feel about him now that he's converted to Merino wool.

Could someone please clarify whether a better sock is truly worth it on a daily basis or if this is something you only notice if you already care about it? God forbid my dad keeps current while I continue to fall behind; I need to see things from another person's point of view."

so I've been on mounjaro 5mg for 9 months and I’m still losing about 0.5-1lb per week. a1c is perfect. the side effects are minimal so my doctor wants to keep me at 5mg indefinitely. everything I read says people titrate up to higher doses. my friend is on 12.5mg. I feel like I'm doing something wrong by not moving up. do you eventually need to go up?