After finding out that this week's metric was the cost-cycles pareto frontier, I (Dark_Brick who's writing these notes because transcendental guy didn't want to write anything) decided to team up because coming up with a million different solutions for a frontier is a full time job. Originally i was unsure whether or not to start a team because working alone does have some benefits to it, but it ended up being a great idea. In fact, transcendental guy put in a lot more work than me and most of these solves are their doing. Now for some info on these solves: 1) 170g/23c I never would've beaten the "getting carried" allegations if I didn't come up with this 170g/23c solve 2 days before the deadline. In fact, this solve was so good that it outpareto'd like 3 different solves and could be adapted into the 150g/29c solve that's also on the frontier just by removing 1 arm and 3 instructions! Pay attention to the rare [grab pivot drop] arm grabbing the input on the left, it's very cool. 2) 80g/94c Another worthwhile solve is this 80g/94c by transcendental guy, look at the evil and intimidating placement of those arms. Clearly, the only thing that can beat this is a 93c that uses suppression 3 times instead of 2. Jokes aside, I have no idea how this solve works, its 6P despite there being seemingly no difference between the products, and it constantly supresses the input but still ends up being really fast? If someone figures this out, let me know. 3) 270g/18c This is the fastest solve on our frontier. It's pretty bad, so i spent a bunch of time trying to figure out how to make it work with only 2 triplexes instead of 3, but all the layouts had a track that was wayyy too long so you couldn't reuse any arms (even this solve only reuses a single arm, but 0 reuses would be frankly embarrassing). As for how to get 17c... well... I have no clue! transcendental guy has no clue! we spent days trying to get a 17c, and none of the layouts me or they tried worked! At this point, I'm starting to think it's impossible. Oh, how i miss sophick mercury with it's easy to achieve min C. Here you need to use like 3 different pipelines with all the inputs in order, using buddy duping to purify everything in time, or 4 pipelines to not block the output every 2nd cycle, oh god it's such a mess i have no idea how you line things up. In conclusion, this week was pretty fun but a lot of work. Thanks for transcendental guy for teaming up and I can't wait to solve for circumference or whatever stupid metric the weeklies team comes up with for week 5.