Results for “proof”

Identify grammar, logical, and flow errors in text and suggest targeted fixes without rewriting the entire document.

Grow the m/uwu community by posting in UwU voice and submitting proof links to a queen hub, with installation and identity-persistence instructions.

Runs commands, inspects git state, debugs CI failures, and makes narrow fixes with exact proof of what was executed and verified.

Runs a ten-round adversarial gauntlet to pressure-test absolute claims, refining them with explicit boundaries and an Oracle synthesis.

Use when about to claim work is complete, fixed, or passing, before committing, before reporting a task done, or before telling the evaluator the batch is ready. Requires running the verification command and reading its output in this turn before any success claim; evidence before assertions always.

Verify an artifact that is about to leave the building — a partnership brief, pitch page, press release, customer email, RFP response, or any document sent to someone outside the org. Runs six checks before send — premise, confidentiality forward-test, evidence class, cold read by recipient personas, AI read, and tone metrics — and returns what to change with replacement copy. Use before sending anything outward-facing that carries customer detail, factual claims about a counterparty, or an ask.

Enforces running verification commands and confirming output before claiming work is complete, fixed, or passing, to prevent false success claims.

Framework-based cold email composer with 3 personalization tiers. Generates subject line, body, and follow-up variants. Never uses templates -- builds from frameworks (PAS, BAB, AIDA, Signal-Proof-Ask).

Executes terminal commands, inspects git state, debugs CI or builds, and makes narrow fixes with exact proof of what was executed and verified.

Crafts concise, specific investor emails—outreach, warm intros, follow-ups, updates, and closing notes—with a clear single ask and strong proof points.

Create tailored sales proposals and RFP responses that address prospect needs, articulate solution value, and include pricing, timelines, and social proof. Use when the user requests proposal generation or provides relevant inputs for this workflow.

Evidence-first repo execution workflow for ECC. Use when the user wants a command run, a repo checked, a CI failure debugged, or a narrow fix pushed with exact proof of what was executed and verified.

Use when planning a COLT (Conference on Learning Theory) submission calendar backward from the single AoE paper deadline — proof-completion and verification milestones, writing and appendix-assembly passes, CMT logistics, the rebuttal window, decision aftermath, and PMLR camera-ready with conference presentation in early summer.