seeco's banner
seeco's profile picture

seeco

@seeconvm • 3,626 subscribers

ai researcher post about AI / crypto open for collabs

Shorts

Opus 5.5 just turned a simple idea into this I'm still in shock… Drop the PDF below into Opus 5.5 and try it yourself. Then read the article below, it's everything I learned with Opus 5.5.

Opus 5.5 just turned a simple idea into this I'm still in shock… Drop the PDF below into Opus 5.5 and try it yourself. Then read the article below, it's everything I learned with Opus 5.5.

147,326 views

Opus 5.5 is a motion designer now It’s f*cking unreal… Give the PDF below to Opus 5.5 and watch it work. Then read the guide below, it’s the easiest way to get started.

Opus 5.5 is a motion designer now It’s f*cking unreal… Give the PDF below to Opus 5.5 and watch it work. Then read the guide below, it’s the easiest way to get started.

166,466 views

One prompt in Opus 5.5, zero After Effects It’s f*cking unreal… Paste the PDF below into Opus 5.5 and see what you get. Then save the guide below, it’s all you need to make videos like this.

One prompt in Opus 5.5, zero After Effects It’s f*cking unreal… Paste the PDF below into Opus 5.5 and see what you get. Then save the guide below, it’s all you need to make videos like this.

59,452 views

Opus 5.5 did this in one try, not After Effects I’m still shocked… Send the PDF below to Opus 5.5 and copy what I did. Then read the guide below, it’s the shortcut I wish I had.

Opus 5.5 did this in one try, not After Effects I’m still shocked… Send the PDF below to Opus 5.5 and copy what I did. Then read the guide below, it’s the shortcut I wish I had.

27,861 views

loop engineering worked for 6 months. then one pipeline forced a graph a loop is one agent on discover → plan → execute → verify, until a stop condition hits enough for most agent work: failing tests, draft + self-review, inbox triage, one research writeup the break is nameable: if the thing that produced the output also grades it, you don't have quality control, you have a rubber stamp his numbers before the split: 40 drafts 31 passed self-review 18 actually publish-ready on manual read gap = 13 drafts with a passing grade from a biased judge he split one loop into 3 nodes - researcher · sources + notes only - writer · notes + task only · never grades itself - reviewer · separate model call · check the bar · write nothing same 40-draft workload. manual approval 18/40 → 33/40. reviewer rejected 14 with quotable reasons. 2 escalated to human instead of burning tokens forever approval 45% → 82.5%. inference cost +60% worth it when a bad draft costs more than three model calls. not worth it for "fix the failing test" playbook: - 1 law · producer never grades - 1 router · ship / retry / escalate - 1 state object · one owner per field · guarded writes - split the verifier first · cheapest highest-leverage move loop engineering → graph engineering. not five nodes for vibes, one split verifier when the loop starts grading its own homework full contracts, router, and decision function in the article

loop engineering worked for 6 months. then one pipeline forced a graph a loop is one agent on discover → plan → execute → verify, until a stop condition hits enough for most agent work: failing tests, draft + self-review, inbox triage, one research writeup the break is nameable: if the thing that produced the output also grades it, you don't have quality control, you have a rubber stamp his numbers before the split: 40 drafts 31 passed self-review 18 actually publish-ready on manual read gap = 13 drafts with a passing grade from a biased judge he split one loop into 3 nodes - researcher · sources + notes only - writer · notes + task only · never grades itself - reviewer · separate model call · check the bar · write nothing same 40-draft workload. manual approval 18/40 → 33/40. reviewer rejected 14 with quotable reasons. 2 escalated to human instead of burning tokens forever approval 45% → 82.5%. inference cost +60% worth it when a bad draft costs more than three model calls. not worth it for "fix the failing test" playbook: - 1 law · producer never grades - 1 router · ship / retry / escalate - 1 state object · one owner per field · guarded writes - split the verifier first · cheapest highest-leverage move loop engineering → graph engineering. not five nodes for vibes, one split verifier when the loop starts grading its own homework full contracts, router, and decision function in the article

14,534 views

Videos

No more content to load