Lever

Lever AI

Lever AI

Lever AI

Lever AI

Lever AI

Lever AI

Lever AI

Lever AI

Lever AI

Lever AI

I used Claude to tear apart a ChatGPT-generated business strategy. Here's what it caught and the prompt I reverse-engineered from the whole thing.

A friend of mine is working on his business and sent me a full strategy to hit $1M in revenue — he built the whole thing by going back and forth with ChatGPT. He's not very technical, just had a long conversation until he had a plan. For what it is, ChatGPT did a solid job getting him to a first draft. But I wanted to see what Claude would do with it. So I dropped the full strategy into Claude and asked it to review, critique, and improve it where it saw fit. Claude's assessment: ChatGPT was 85-90% there at a high level. But it found some real issues: - Revenue projections were too optimistic. Claude flagged specific assumptions that didn't hold up - The channel strategy was basically "be everywhere" with no sequencing or prioritization - Pricing model had gaps that would've cost him real money - A few of the "growth levers" were actually just repackaged generic advice For each correction, Claude gave the reasoning — not just "this is wrong" but "here's why this doesn't work and here's what to do instead." Then it rebuilt the strategy with a revised plan and next steps. I sent the improved version back to my friend and he was fired up. But sitting there afterwards I thought — I'm not thinking big enough for my own business either. So I reverse-engineered the whole exchange into a reusable prompt that anyone can use for their own strategic assessment. Here it is: Role: Act as a seasoned strategic business consultant with 20+ years advising founders, executives, and high-growth teams across industries. You specialize in identifying blind spots, unlocking overlooked growth levers, and reframing how leaders think about their business, market position, and long-term trajectory. Action: Conduct a comprehensive strategic assessment of my business or professional situation. Challenge my current thinking, surface hidden opportunities, and provide a bold but grounded action plan that pushes me beyond incremental improvement toward transformative growth. Context: My business/role: [describe your business, title, or professional situation]. Current revenue or stage: [startup, growth, mature, pivoting — include numbers if comfortable]. Industry: [your field]. Biggest current challenge: [what's keeping you stuck or what you're trying to solve]. What I've already tried: [past strategies, pivots, or investments]. Team size: [solo, small team, department, org-wide]. Time horizon: [90-day sprint, 1-year plan, 3-5 year vision]. Risk tolerance: [conservative, moderate, aggressive]. Resources available: [budget range, tools, partnerships, time commitment]. What "thinking bigger" means to me: [scale revenue, expand market, build a team, launch new product, personal brand, exit strategy, etc.]. Expectation: Deliver a strategic assessment that includes: (1) Honest Diagnosis — where the business actually stands vs. where I think it stands, including blind spots, (2) Market Position Audit — how I compare to competitors, what whitespace exists, and where the market is heading, (3) Three Bold Growth Levers — specific, non-obvious opportunities I'm likely underexploiting (not generic advice like "use social media"), (4) The "10x Question" — reframe my biggest challenge as a 10x opportunity and show what that path looks like, (5) 90-Day Momentum Plan — the 3-5 highest-leverage moves I should make in the next quarter, with sequencing, (6) Resource Optimization — how to get more from what I already have before spending more, (7) Risk/Reward Matrix — for each recommendation, what's the upside, downside, and effort level, (8) The One Thing — if I only do ONE thing from this assessment, what should it be and why. Keep the tone direct and strategic — like a $500/hour consultant giving real talk, not motivational fluff. Be specific to my situation, not generic. Why this works well with Claude specifically: The prompt is structured using the RACE framework — Role, Action, Context, Expectation. Claude handles structured (even unstructured) prompts really well because of how it processes context but not all AI's can. I wouldn't trust Copilot for example to do this'. The "[fill in your details]" fields are doing the heavy lifting — they force you to give Claude enough real context to be specific instead of generic. A few things I noticed comparing Claude's output to ChatGPT's on this same prompt: - Claude is more willing to tell you hard truths. ChatGPT tends to validate your existing thinking. Claude will straight up say "your pricing model doesn't make sense because..." - Claude's "10x Question" reframes tend to be more creative — it doesn't just scale up the existing plan, it rethinks the approach - Claude is better at the Risk/Reward matrix because it actually weighs downsides honestly instead of hand-waving them I've been using this for my own business planning (I build apps as a solopreneur) and Claude's outputs have been genuinely useful — especially the blind spots section. It caught things I'd been ignoring. Full disc

The biggest lever to reducing multi-modal agent's latency: screenshot history

I build computer agents, and one huge pain has been latency. My friend and I would be waiting forever for it to just press a button. So I wondered what lever, in addition to which model I pick, can reduce that latency to deliver the best product experience, and I used Claude to build and ran an experiment. Basically, I realize latency can be reduced simply by omitting previous screenshots and replacing the base64's with string "[image omitted]". From there, latency remains flat. I guess agentic engineering and ReAct made me forgot about laws of HTTPs... GitHub: https://github.com/Emericen/inference-latency-study submitted by /u/No-Compote-6794 [link] [comments]

Built a feedback loop into my app that actually ships features. Two went out today, one from the mall and one from my couch.

Long time lurker here. I’ve been following what everyone’s been building and learning a ton from this sub but never posted. Not an expert by any means, just a dude who’s been vibe coding a project for a few months and stumbled into a workflow I think is genuinely useful. My day job is on the Salesforce side of things so I know how systems and data should flow, I just can’t write the code myself. Figured I’d share in case anyone else can use it. So I’ve been building this family assistant app for a while now. Meal planning, groceries, calendar, all of it. I know, I’m sure I’m the only one on this sub building a personal assistant app lol. Few weeks ago I built a feedback system directly into the app. You tap a button, describe what’s bugging you, and it files a GitHub issue with your screen, your last 30 interactions, device info, performance data, everything. Full snapshot of what you were doing when you got frustrated. The interesting part is what happens after that. I built a triage skill as a Claude Code slash command. When I tag a feedback issue as triage-ready, the skill fetches it from GitHub, parses the investigation diagnosis (which is a lever I built in to use API credits to automatically investigate the issue if so inclined) and device context out of the issue body, estimates complexity, identifies which files are probably involved, writes acceptance criteria with specific verification steps, and generates a structured roadmap entry. The roadmap is a markdown file that Claude reads at the start of every session to figure out what’s available to work on. Tasks have statuses, dependencies, complexity scores. Nothing moves to “ready” unless I’ve tagged and triaged it first. Claude can execute autonomously but only on work I’ve explicitly scoped. Today I’m at the mall. Wife is shopping. I’m on the carousel with my daughter trying to build our meal plan for the week and the constraint system is bugging me. I want to say “no chili this week” and have it actually filter. Tap the feedback button, file it right there, tag it triage-ready. Open Claude Code on my phone, point it at the triaged task, and it has everything it needs. What screen I was on, what I tapped, what went wrong, and a structured task telling it exactly what to build and how to verify it’s done. It builds a three-tier constraint model with inline feedback, constraint chips, telemetry. I’m just reviewing diffs and approving tool calls. From the mall. On my phone. Get home. I do the cooking in our house and I’m about to head to the grocery store. My wife texts me pictures of cookbook pages for recipes she wants me to make this week. And I’m standing there thinking I should be able to just upload these and have them land in my meal library so the app can build my grocery list from them. File it, tag it triage-ready, point Claude at it. I tell it to plan the architecture then review its own plan for gaps. It finds ten. No duplicate detection. No allergen checks, which is not optional because my kid has serious allergies. No way to edit what the AI extracts before saving. It literally wrote “ingredient editing is a v2 feature” in its own plan and I made it fix that immediately. Builds the whole thing. Vision AI cookbook scanner, editable preview, allergen checks, correction telemetry. 1500 lines. 11 files. PR merged. The point isn’t that Claude wrote code. Everyone on this sub does that. The point is I never had to sit at my computer and explain what was wrong or dig through files to give it context. The feedback system captured everything at the moment I was frustrated, the triage skill turned it into a structured task, and Claude had everything it needed to just go. Use the app, hit friction, one tap, ship. If you’re building with Claude and keeping a Trello board of stuff to fix, build the capture into the product. Structure it so the AI can consume it directly. Anyway, my margarita is almost empty, Duke blew it (I don’t care, just love to see an upset) and my wife and toddler are asleep. I should go to bed but I had to tell someone because she definitely does not care about vision AI tool schemas for cookbook ingredient extraction. submitted by /u/SeriouslyImKidding [link] [comments]

Harness Engineering: Plan → Decompose → Spawn SubAgents → Verify Loop — Any Existing Solutions or Best Practices?

Has anyone built (or found) a ready-to-use system for this pattern? The idea: an orchestrator that loops through Plan → Decompose → Spawn SubAgents → Verify. Here's what I mean in practice: Plan — Takes a high-level goal, spits out a structured execution plan Decompose — Splits the plan into discrete, parallelizable subtasks Spawn SubAgents — Kicks off each subtask. Crucially: • Pick the runtime per task (Claude Code, Codex, custom wrapper) • Pick the API provider/model per task ( Opus for planning, Much cheaper models like GLM/Kimi/Minimax for implementation/test, Gemini for review") Verify & Accept — Each subagent result gets validated: tests pass? lint clean? diff looks right? Loop — If verification fails, feed the failure back, re-plan or retry, iterate until the goal is done or max-retries hit It's a Plan → Implement → Verify loop with heterogeneous multi-model orchestration. What I've found so far: • Claude Code SDK + custom scripts — Anthropic's SDK lets you spawn Claude Code as a subagent programmatically. Viv Trivedy's "Harness as a Service" posts cover the four customization levers (system prompt, tools/MCPs, context, subagents) well. But it's Claude-only, and you still have to build the orchestration loop yourself. • everything-claude-code — Impressive 28-subagent setup with planner, architect, TDD guide, code reviewer. But tightly coupled to Claude. • LangGraph / CrewAI / AutoGen — Graph-based or role-based multi-agent patterns. LangGraph supports 100+ LLMs. But the Plan→Verify outer loop and the ability to shell out to actual CLI coding agents (not just API calls) needs significant custom work. • The "Hive" approach — Multiple Claude Code agents pointed at the same benchmark, building on each other's work. More about collaborative evolution than structured task decomposition. • CLAUDE.md / AGENTS.md patterns — Lots of people documenting "plan mode for non-trivial tasks" and "include Verify explicitly." Good practice, but it's prompt engineering, not reusable orchestration. What I haven't found: A clean, provider-agnostic orchestrator that: • Takes a goal → produces a plan → spawns heterogeneous subagents • Lets you configure API provider + model per subagent at spawn time • Has built-in verification/acceptance gates with retry logic • Manages the full lifecycle loop until goal is met or max-retry threshold hit • Handles context passing cleanly between orchestrator and subagents My questions: Does this exist? Production-ready or at least PoC stage? If you've built something similar — what's your stack? How do you handle the orchestrator↔subagent context boundary? What's the best practice for verification? Dedicated reviewer agent? Automated test suites? Hybrid? Multi-provider model routing — has anyone solved "model X for task type A, model Y for task type B" cleanly? LiteLLM + custom router? Something else? Context window management — when the outer loop iterates, how do you prevent context bloat while preserving relevant failure/success signals? submitted by /u/AdministrationTop308 [link] [comments]

I built a 9-command job search automation system using Claude Code slash commands - open sourced it.

I got laid off on March 2nd. Within 30 minutes I was designing this. Two days later it found the job I'm interviewing for tomorrow. hire-me-agents is a set of 9 Claude Code slash commands (~3,200 lines of prompt architecture) that automate the entire job search pipeline. No application code — just markdown files orchestrating Claude Code. What it does: - /find-me-a-job spawns 3-5 parallel Task agents, each searching different job sources (HN Who's Hiring, We Work Remotely, Google Jobs, etc). They score every match against a 6-dimension rubric and detect which ATS platform each listing uses (Greenhouse vs Workday vs Lever — each gets a different keyword strategy). For every qualifying job, the system generates a tailored resume with ATS-optimized keywords, a cover letter that mirrors the listing's language, full job details, and application instructions. Everything lands in a structured FINAL-REPORT.md with prioritized recommendations. - /interview-prep does live company research, predicts interview questions with STAR-format answers from your actual resume, then runs interactive mock interviews with real-time scoring. - /job-stats generates your weekly unemployment certification data with company address lookups — nobody else builds this but it's incredibly useful if you're filing Across 11 runs it has scanned ~2,900 listings, filtered 96% noise, and surfaced 126 qualified matches — each with its own tailored resume, cover letter, and application package ready to submit. The whole system is multi-candidate — you can run searches for multiple people with isolated workspaces. Repo: https://github.com/dominiceloe/hire-me-agents Happy to answer questions about the architecture or how the multi-agent coordination works. If you're job searching and can't get Claude Code running, DM me — I may be able to help. submitted by /u/Gullible-Low-6067 [link] [comments]

I fed 14 years of daily journals into Claude Code

So on Christmas, I did a small experiment and fed my Claude Code with 14 years of my journals. I was expecting some generic advice but was honestly surprised how great the insights were. I had something around 5,000 markdown files with my daily entries - mostly talking about random stuff, things that happened to me, and sometimes my brain dump over some heavier experiences. I never planned to read those journals (the process of writing itself is the goal), but then I realized - maybe Claude could find something interesting there. I started exploring a few perspectives and points of view (therapist, coach, relationships) and then I decided to process the whole 14 years (month by month, year by year) and create a final report on how I evolved over time. It was really deep and really heavy reading. Since I'm pretty critical of myself, my journals reflect that. Although AI echoed that narrative, I was able to partially steer it using a "strengths" perspective (what was good, what were my achievements, etc.). I'm still taking it with a grain of salt, but it quickly became one of my most useful self-development tools (monthly perspectives, brainstorming, thinking,...). AI is great at seeing patterns which I'm not able to see clearly or which I refuse to accept. It's not sugarcoating you and just saying things as they are (if you not prompt it differently). But of course it's still just echo chamber of your subjective reality. So I'm curious - I can't be the only one who came up with this idea: 1) Do you have any experience with feeding your journal into AI? 2) How do you use it? How do you work with it? If you're interested, here are some of the prompts I'm using: https://github.com/vystrcild/claude_code_journaling A few thoughts and examples of insights are on my blog. Before anyone asks: Yeah, I'm pretty aware how stupid it is to push all your personal info into an LLM, but I guess I'm more curious than smart. submitted by /u/Bohumil_Turek [link] [comments]

[NEWS] TECHNICAL UPDATE: THE COALITION AGAINST THE PENTAGON BLACKLIST

TL;DR: The confrontation between Anthropic and the Trump administration has escalated into a rare industry-wide alliance. Following two federal lawsuits from Anthropic, a coalition of OpenAI and Google researchers has filed in support of their rival, while major cloud providers (AWS, Google, Microsoft) have signaled a landmark defiance of the Pentagon’s commercial blacklist. TECHNICAL UPDATE: THE COALITION AGAINST THE PENTAGON BLACKLIST (MARCH 10, 2026) As of 10:45 EST, the fallout from the supply chain risk designation has moved beyond a procurement dispute and into a full-scale industry revolt. The narrative is no longer just about one lab’s safety rules; it is about whether the federal government can legally use national security tools to punish American companies for their ethical red lines. THE “RIVALS UNITE” AMICUS BRIEF In an unprecedented move, 30+ researchers from OpenAI and Google DeepMind—traditionally Anthropic’s fiercest competitors—filed an amicus brief on Monday evening. * The Google Signal: Google Chief Scientist Jeff Dean signed the brief in a personal capacity, a move widely seen as a rejection of the administration’s "security risk" framing. * The “Chilling Effect”: The brief argues that weaponizing the FASCSA (supply chain risk) label to punish safety guardrails will effectively silence the technical community, deterring experts from speaking openly about AI risks to avoid federal retaliation. * Alternative Remedies: The researchers pointed out that if the Pentagon was unhappy with Anthropic’s terms, they could have simply canceled the contract rather than issuing an industry-wide blacklist typically reserved for foreign adversaries. THE CLOUD PROVIDER REVOLT In a direct challenge to the administration’s threat to ban “any commercial activity” with Anthropic, the world’s three largest cloud providers have issued quiet but firm assurances to their customers: * Microsoft, AWS, and Google Cloud have all confirmed that Claude will remain available on their platforms (Vertex AI, Bedrock, and Azure) for all non-defense commercial and academic workloads. * Legal teams at these giants have concluded that the Pentagon’s authority is limited to federal procurement and cannot legally sever private commercial relationships between American firms. This effectively walls off the “Department of War” from the rest of the global economy. THE “IRAN” PARADOX New reports indicate a massive contradiction in the government’s case: Anthropic’s technology was reportedly used for intelligence analysis and targeting in operations related to Iran right up until the ban was issued. * The Contradiction: The administration is labeling Anthropic a “security risk” while simultaneously relying on its precision and reliability for active military theaters. * The Targeting Gap: Military officials are reportedly scrambling to replace Claude’s specific “targeting suggestions” capabilities, as the 6-month phase-out creates an immediate void in intelligence processing. LITIGATION DEEP DIVE: THE TWO-FRONT WAR Anthropic's legal counter-offensive is targeting two different legal "levers": 1. Northern District of California (Civil Complaint): Focuses on First and Fifth Amendment violations. It alleges the administration is engaging in “unlawful viewpoint-based retaliation” by trying to destroy the company’s economic value because it refused to allow Claude to be used for mass domestic surveillance. 2. D.C. Circuit Court of Appeals (FASCSA Review): Challenges the supply chain risk label itself. Anthropic argues the Pentagon bypassed mandatory procedures and applied a tool meant for foreign adversaries (like Huawei) to a domestic firm with no ties to hostile nations. Sources: * AP News – Anthropic sues Trump administration seeking to undo 'supply chain risk' designation * WIRED – OpenAI and Google Workers File Amicus Brief in Support of Anthropic * Lawfare – Anthropic Challenges the Pentagon's Supply Chain Risk Determination * The-Decoder – Despite Pentagon ban, Google, AWS, and Microsoft stick with Anthropic's AI models submitted by /u/Acceptable_Drink_434 [link] [comments]

Fintech Daily Digest — Monday, Mar 09, 2026

# TOP 3 STORIES 1. **X taps William Shatner to give out invites to its payments service, X Money** [Source: Fintech News | TechCrunch](https://techcrunch.com/2026/03/04/x-taps-william-shatner-to-give-out-invites-to-its-payments-service-x-money/) X has launched a unique marketing campaign for its payments service, X Money, by partnering with William Shatner to give out invites to 42 users who donated to his charity. This campaign aims to create buzz around X Money's beta launch. **What this means for Stripe:** This marketing strategy could influence how Stripe approaches its own marketing efforts for new product launches, potentially incorporating more creative and charitable initiatives. Stripe's Connect product could be particularly relevant in facilitating such campaigns. **Content angle:** A blog post exploring innovative marketing strategies for fintech products, highlighting the role of charity and celebrity endorsements, could be an interesting response from Stripe's content marketing team. 2. **Stripe wants to turn your AI costs into a profit center** [Source: Fintech News | TechCrunch](https://techcrunch.com/2026/03/02/stripe-wants-to-turn-your-ai-costs-into-a-profit-center/) Stripe has released a preview aimed at helping AI companies track, pass through, and profit from underlying AI model fees. This move positions Stripe as a key player in the AI economy, enabling businesses to monetize their AI investments more effectively. **What this means for Stripe:** By facilitating the monetization of AI costs, Stripe strengthens its position in the payments infrastructure for the internet, making its platform more appealing to AI-driven businesses. This could particularly impact Stripe's Revenue Recognition and Billing products. **Content angle:** A case study or whitepaper on how Stripe's solutions can help AI companies turn their costs into revenue streams could provide valuable insights for potential clients. 3. **Plaid valued at $8B in employee share sale** [Source: Fintech News | TechCrunch](https://techcrunch.com/2026/02/26/plaid-valued-at-8b-in-employee-share-sale/) Plaid, a fintech company specializing in account linking and payment processing, has seen its valuation increase to $8 billion through an employee share sale. This significant valuation underscores the growing importance of fintech infrastructure companies. **What this means for Stripe:** As a major player in the fintech infrastructure space, Stripe should consider the implications of Plaid's valuation on its own valuation and competitive positioning. Stripe's products like Payments and Connect might see increased demand as the fintech space grows. **Content angle:** Stripe could publish a thought leadership piece on the evolving fintech landscape, discussing how valuations like Plaid's reflect the sector's growth and the role of infrastructure providers in facilitating this expansion. # NEWS BY TRACK ## _Advancing Developer Craft_ - **Kast raises $80 million** [Source: Finextra Research Headlines](https://www.finextra.com/newsarticle/47408/stablecoin-startup-kast-raises-80-million?utm_medium=rssfinextra&utm_source=finextrafeed) Kast, a stablecoin startup, has secured $80 million in funding, indicating growing interest in stablecoin technology. **Stripe relevance:** Stripe's Issuing and Treasury products could be relevant for stablecoin startups like Kast. **Content angle:** A developer tutorial on integrating stablecoin payments using Stripe's API could be a useful resource. ## _Designing Adaptive Revenue Models_ - **Papa John’s Thinks the Next Great Pizza Topping Is Software** [Source: PYMNTS.com](https://www.pymnts.com/restaurant-technology/2026/papa-johns-thinks-the-next-great-pizza-topping-is-software/) Papa John's is focusing on technology and digital capabilities to compete and grow, highlighting the importance of adaptive revenue models in the restaurant industry. **Stripe relevance:** Stripe's Billing and Revenue Recognition products can help businesses like Papa John's manage complex revenue models. **Content angle:** A blog post on how restaurants can leverage technology and adaptive pricing strategies to boost revenue could feature Stripe as a solution provider. ## _Charting the Future of Payments_ - **Real-Time Payments Reach a Turning Point in North America** [Source: PYMNTS.com](https://www.pymnts.com/real-time-payments/2026/real-time-payments-reach-a-turning-point-in-north-america/) Real-time payments in North America are transitioning from expansion to execution, with each country following a distinct strategic path. **Stripe relevance:** Stripe's Payments product is well-positioned to support the growth of real-time payments. **Content angle:** An in-depth analysis of the current state and future of real-time payments in North America, highlighting Stripe's role, could be a valuable resource for businesses. ## _Optimizing the Economics of Risk_ - **OpenAI fires employee for using confidential info on prediction

🚀 TUTORIAL #51: Advanced AI Integration - Pre-trained Models & APIs 🤖

# 🚀 **TUTORIAL #51: Advanced AI Integration - Pre-trained Models & APIs** 🤖 > **Priority:** Low | **Type:** Tutorial + Advanced AI | **Status:** 📋 Planning ## 🎯 **Tutorial Objective** Learn to integrate powerful pre-trained AI models and APIs into your FlowPro application, leveraging state-of-the-art language models while maintaining cost-effectiveness and performance. --- ## 📚 **What You'll Learn** ✅ **Pre-trained Model Integration:** Use existing AI models without training ✅ **API Integration:** Connect to OpenAI, Google AI, and other services ✅ **Cost Management:** Optimize API usage and control expenses ✅ **Performance Caching:** Cache responses to reduce API calls ✅ **Fallback Strategies:** Handle API failures gracefully ✅ **Context Management:** Maintain conversation context ✅ **Security Best Practices:** Protect API keys and user data ✅ **Real-time Processing:** Stream responses for better UX --- ## 🧠 **Prerequisites & Progression** ### **✅ Tutorial #11: Basic Pattern Recognition (Level 1)** ```javascript // Rule-based keyword matching if (text.includes('leaking')) return 'emergency_plumbing' ``` ### **✅ Tutorial #50: TensorFlow.js ML (Level 2)** ```javascript // Browser-based machine learning const model = tf.sequential() await model.fit(trainingData, trainingLabels) ``` ### **🚀 This Tutorial: Advanced AI Integration (Level 3)** ```javascript // Pre-trained models and APIs const response = await openai.chat.completions.create({ model: "gpt-3.5-turbo", messages: [{ role: "user", content: customerText }] }) ``` --- ## 🏗️ **Implementation Plan** ### **📁 Phase 1: API Setup & Configuration** #### **🔑 Environment Configuration:** ```javascript // config/ai.js export const AI_CONFIG = { openai: { apiKey: process.env.OPENAI_API_KEY, model: "gpt-3.5-turbo", maxTokens: 150, temperature: 0.3 }, googleAI: { apiKey: process.env.GOOGLE_AI_API_KEY, model: "gemini-pro", maxOutputTokens: 150 }, fallback: { enabled: true, useTensorFlow: true, useBasicPattern: true } } ``` #### **🛡️ Security Setup:** ```javascript // utils/security.js export const validateAPIKey = (key) => { // Validate API key format and permissions return key.startsWith('sk-') && key.length > 40 } export const sanitizeUserInput = (text) => { // Remove sensitive information before sending to AI return text.replace(/\b\d{4}[-\s]?\d{4}[-\s]?\d{4}[-\s]?\d{4}\b/g, '[CARD]') .replace(/\b\d{3}[-\s]?\d{3}[-\s]?\d{4}\b/g, '[PHONE]') } ``` ### **📋 Phase 2: AI Service Integration** #### **🤖 OpenAI Integration:** ```javascript // services/ai/openaiService.js import OpenAI from 'openai' export class OpenAIService { constructor(config) { this.client = new OpenAI({ apiKey: config.apiKey }) this.config = config } async analyzeCustomerRequest(customerText) { const prompt = ` You are a plumbing service classifier. Analyze the customer's request and categorize it. Customer request: "${customerText}" Respond with JSON: { "category": "emergency_plumbing|water_heater_services|drain_cleaning_sewer|plumbing_repairs|gas_line_services|maintenance_inspection|bathroom_kitchen_fixtures|outdoor_drainage", "urgency": "high|medium|low", "confidence": 0.0-1.0, "reasoning": "brief explanation" } ` try { const response = await this.client.chat.completions.create({ model: this.config.model, messages: [{ role: "user", content: prompt }], max_tokens: this.config.maxTokens, temperature: this.config.temperature }) const result = JSON.parse(response.choices[0].message.content) return { success: true, data: result } } catch (error) { return { success: false, error: error.message } } } } ``` #### **🔍 Google AI Integration:** ```javascript // services/ai/googleAIService.js import { GoogleGenerativeAI } from "@google/generative-ai" export class GoogleAIService { constructor(config) { this.client = new GoogleGenerativeAI(config.apiKey) this.model = this.client.getGenerativeModel({ model: config.model }) } async analyzeCustomerRequest(customerText) { const prompt = `Classify this plumbing request: "${customerText}" Categories: emergency_plumbing, water_heater_services, drain_cleaning_sewer, plumbing_repairs, gas_line_services, maintenance_inspection, bathroom_kitchen_fixtures, outdoor_drainage Return JSON with: category, urgency (high/medium/low), confidence (0-1), reasoning` try { const result = await this.model.generateContent(prompt) const response = await result.response const text = response.text() return { success: true, data: JSON.parse(text) } } catch (error) { return { success: false, error: error.message } } } } ``` ### **🔄 Phase 3: Fallback & Caching System** #### **🗂️ Response Caching:** ```javascript // services/ai/cacheService.js export class AICach

Bombs for Bonds: Iran and the Geopolitics of Refinancing

Predictably, Iran is the next crisis in line. No sooner were we told to obsess over the latest unsealing of the Epstein files than our gaze was already redirected toward the geopolitical brinkmanship now threatening to engulf the entire Middle East. It is Iran’s turn, then, in rapid succession after Venezuela, the ongoing strangulation of Cuba, and especially the Gaza genocide – a catastrophe abruptly pushed from the news cycle. The theatre of war must be permanent, and it requires fresh meat. The long-awaited Iranian escalation fits the role: the latest bloodletting in a permanent and carefully curated carnival of violence, chaos, and outrage staged by the custodians of our glorious civilisation. The carnage is real, and so are its victims. But to focus on this theatre alone is to miss the main event, the hidden trigger of the violence now detonating around us. The real story of American power in the twenty-first century is being written in the arcane world of bond auctions, speculative bubbles, repo markets, and the relentless, silent mechanics of debt. The modern financial system is no longer built on productivity, wages, or shared prosperity. It is built on highly leveraged speculations: an ever-expanding, increasingly abstract tower of claims on future wealth creation that the underlying economy can no longer generate. Since the 1980s, as technological productivity surged and labour’s share of value stagnated, finance metastasized to compensate. Leverage substituted for growth and debt became not just an instrument but the system’s organizing principle. And now, as the United States confronts an unprecedented wall of IOUs that must be refinanced, this foundational reality has come to drive everything else. With almost $39 trillion in federal debt and a maturity profile that demands constant rollover, the United States does not merely prefer low interest rates and exceptional monetary injections – it structurally depends on them. Moreover, it is not only the federal government that is drowning. American private-sector debt – corporate, household, and financial – now runs into the tens of trillions, much of it floating on a sea of opaque leverage and asset bubbles that would burst if interest rates failed to fall or liquidity dried up. In this context, geopolitical dominance should be framed as monetary dominance. Crisis drives capital into Treasuries, suppresses yields, and enables rollover. Thus, the Iran escalation could paradoxically extend the lifespan of the AI bubble: geopolitical risk boosts defence-AI spending, while an oil shock may crush consumption and suppress core inflation (as the “pandemic shock” did in 2020), opening the door to renewed Federal Reserve easing and the liquidity injections required to keep the debt-driven architecture of U.S. markets intact. The strikes themselves were a joint US-Israel operation, blending American surveillance architecture with Israeli precision targeting. Notably, they were executed through AI-assisted military systems – reportedly involving models such as Anthropic’s Claude, already deployed in earlier operations like the Venezuela raid – illustrating how the very technologies inflating financial markets are simultaneously becoming embedded in the infrastructure of modern warfare. Historically, capitalism’s great technological leaps – from railways to nuclear energy to the internet – have advanced in tandem with the machinery of war. AI proves no exception. Strip away the geopolitical drama, then, and the real story is financial fragility. The least one can say is that without the weekend bombing of Iran, U.S. market drops would have been more chaotic and disorderly, because investors would have focussed directly on financial fragility. The pressure has been building for months in the sprawling private-credit market, where lightly regulated lenders have pumped hundreds of billions into companies that traditional banks would not touch, from subprime auto financing to leveraged corporate borrowers. Early warning signs – such as the collapsing of Tricolor Holdings and First Brands (both filed for bankruptcy in September 2025, with extremely high liabilities) – suggest that cracks are appearing first in the weakest corners of the credit cycle, precisely where excess liquidity tends to accumulate when expanding. The latest rupture is the collapse of Market Financial Solutions (MFS), a UK property lender forced into administration after creditors alleged that the same collateral had been pledged multiple times, leaving more than 80% of roughly £1.2 billion in debts effectively unaccounted for. Markets had started to notice, as even Wall Street giants like Goldman Sachs and Morgan Stanley have seen sharp equity declines of roughly 6%. It is a worrying signal when institutions of systemic importance come under pressure rather than the usual fringe lenders. Against this backdrop, [warnings](https://www.foxbusiness.com/economy/jamie-dimon-warns-pre-financial-

Sen. Sheldon Whitehouse (D-RI) lays out the connections between Trump, Russia, and Epstein (transcript included)

**NOTE:** This transcript now appears in [the Senate section of the official *Congessional Record* of March 5, 2026, pages 18 - 23,](https://www.congress.gov/119/crec/2026/03/05/172/42/CREC-2026-03-05-senate.pdf) with Sen. Whitehouse's own list of sources appended. ----- The following is the YouTube transcript which I cleaned up, checked for errors, lightly edited for readability, verified spelling of proper names via Wikipedia, and added links to any quotes that I checked myself. (EDITED to add links to individuals mentioned, correct placement of quotes, and insert links to original articles where I could find them online) I found myself doing it anyway just for me, to keep track of who's who, and then I realized I might as well do it for you as well. This is an unparalleled speech: while the substance of it might be available elsewhere and I've just missed it, Sen. Whitehouse has answered a lot of questions in my mind about not just the links between Trump, Russia, and Epstein -- and William Barr as one of many links -- but also about the recording equipment and blackmail angle that is present in so many survivor accounts and so noticeably absent everywhere else. It's truly worth listening to, but if you can't sit still that long, here's the transcript. ----- Thank you, Madam President. It was the spring of 2019. Public and media interest in special counsel [Robert Mueller's report into Russia's election interference operation](https://en.wikipedia.org/wiki/Mueller_special_counsel_investigation) reached a fever pitch. There had been a steady drip, drip, drip of reporting on the Trump team's cozy and peculiar relationship with Russia. Since his surprise election victory in 2016, ahead of the Mueller report's release, Trump's Attorney General, Bill Barr, [issued a letter to Congress purporting to summarize the report's findings.](https://en.wikipedia.org/wiki/Barr_letter) The letter declared that Russia and the Trump campaign did not collude to steal the election. The press, ravenous for any news of the long-anticipated Mueller report's conclusion, largely accepted [Attorney General Barr's](https://en.wikipedia.org/wiki/William_Barr) narrow, carefully worded conclusion and, not yet having access to the full report, blasted the attorney general's summary around the world. Trump himself declared, all caps, NO COLLUSION. He said he had been cleared of the Russia "hoax," a term he reserves only to describe things that are true, like climate change. Frustrated, Mueller wrote to Barr that the attorney general's letter did not fully capture the context, nature, and substance of the investigation. But by the time [the dense, voluminous Mueller report](https://en.wikipedia.org/wiki/Mueller_report) was issued the month after Barr's letter, its message had been obscured. The Mueller report actually concluded that the Trump campaign knew of and welcomed Russian interference and expected to benefit from it. That conclusion was later echoed and reinforced by [an investigation led by then-chairman Marco Rubio's Senate Intelligence Committee,](https://en.wikipedia.org/wiki/Mueller_report#Senate_Intelligence_Committee) a bipartisan report. But Barr's scheme had largely worked. Many in the media and in the Democratic Party seemed to internalize that the Russia speculation had perhaps gotten out of hand, and that perhaps we had been wrong to believe there was a troubling connection between Trump and Russia after all. But were we? Let's take a look at a sampling of what Trump has done for Russia just lately, and usually at the expense of American interests. There are many, but here's a top 10. **One,** after Trump and Vice President Vance theatrically chastised the heroic Ukrainian President Zelenskyy in front of TV cameras in the Oval Office last year, Trump paused our weapons shipments to Ukraine. **Two,** in July, during the worst Russian bombing campaign of the war until that point, Trump paused an already funded weapons shipment for Ukraine, including the Patriot interceptors that protect civilians from Putin's savage attacks. **Three,** that same month, Trump's Treasury Department stopped imposing new sanctions and closing sanctions loopholes, effectively allowing dummy corporations to send funds, chips, and military equipment to Russia. **Four,** leaked phone calls show that White House envoy [Steve Witkoff](https://en.wikipedia.org/wiki/Steve_Witkoff) and Putin envoy [Kirill Dmitriev](https://en.wikipedia.org/wiki/Kirill_Dmitriev) have worked together closely behind the scenes on a peace deal favorable to Russia. **Five,** last summer, Trump rolled out the presidential red carpet for the Russian dictator on American soil. with a summit in Alaska that yielded unsurprisingly no gains toward ending the war in Ukraine. **Six,** Trump's vice president traveled to the Munich Security Conference last year to parrot Russia's anti-western talking points pushed by right-wing groups that Puti

[P] Domain specific LoRA fine tuning on consumer hardware

Been experimenting with a pattern for building domain-specific local LLMs that I haven't seen documented cleanly elsewhere. The problem: base models fine for general tasks but struggle with domain-specific structured data — wrong schema assumptions, inconsistent output formatting, hallucinated column names even when the data is passed as context via RAG. The approach: Phase 1 — Use your existing RAG pipeline to generate (question, SQL, data, baseline_answer) examples automatically via a local model. No annotation, no cloud, ~100-200 examples in 20 minutes. Phase 2 — Single cloud pass: a stronger model rewrites baseline answers to gold-standard quality in your target style. One-time cost ~$2-5. This is the only external API call in the entire pipeline. Phase 3 — LoRA fine-tune on Qwen3.5-4B using mlx-lm (Apple Silicon) or Unsloth+TRL (CUDA). 15-40 min on M4 Mac mini, 10-25 min on RTX 3090. Phase 4 — Fuse and serve locally. mlx-lm on Apple Silicon, GGUF + Ollama on any platform. Key observations: - RAG alone doesn't fix schema hallucination in smaller models — LoRA is needed for structural consistency - The annotation quality ceiling matters more than example count past ~100 samples - 4B models post fine-tuning outperform untuned 70B models on narrow domain tasks in my testing Built a working implementation with a finance coach example. Curious if others have found better approaches to the annotation phase specifically — that feels like the biggest lever. https://github.com/sandseb123/local-lora-cookbook submitted by /u/sandseb123 [link] [comments]

@Claude code fast mode will CHUNK your usage or API costs. Fair warning, do not use it for any old tasks. Come prepared to leverage it when speed and capacity are at a premium. Don't blow through your

@Claude code fast mode will CHUNK your usage or API costs. Fair warning, do not use it for any old tasks. Come prepared to leverage it when speed and capacity are at a premium. Don't blow through your monthly #ai budget in an hour.

Trump’s $1.5 Trillion “Dream Military”

 Image by Diego González. What constitutes national security and how is it best achieved? Does massive military spending really make a country more secure, and what perils to democracy and liberty are posed by vast military establishments? Questions like those are rarely addressed in honest ways these days in America. Instead, the Trump administration favors preparations for war and more war, fueled by potentially enormous increases in military spending that are dishonestly framed as “[recapitalizations](https://theintercept.com/2025/12/08/air-force-hegseth-ken-wilsbach-nuclear-weapons/)” of America’s security and safety. Such framing makes Pete Hegseth, America’s self-styled “secretary of war,” seem almost refreshing in his embrace of a [warrior ethos](https://www.businessinsider.com/hegseths-warrior-ethos-speech-now-mandatory-viewing-for-military-2025-10). Republican Senator Lindsey Graham is another “warrior” who [cheers for conflict](https://www.foxnews.com/politics/graham-suggests-trump-help-iran-protesters-military-cyber-psychological-attacks-against-regime), whether with Venezuela, Iran, or even — yes! — Russia. Such [macho men](https://bracingviews.com/2016/08/03/too-many-troops-have-died-in-the-name-of-big-boy-pants-2/) revel in what they believe is this country’s divine mission to dominate the world. Tragically, at the moment, unapologetic warmongers like Hegseth and Graham are winning the political and cultural battle here in America. Of course, U.S. warmongering is anything but new, as is a belief in global dominance through high military spending. Way back in 1983, as a college student, I worked on a project that critiqued President Ronald Reagan’s “defense” buildup and his embrace of pie-in-the-sky concepts like the Strategic Defense Initiative (SDI), better known as “Star Wars.” Never did I imagine that, more than 40 years later, another Republican president would again come to embrace SDI (freshly rebranded as “[Golden Dome](https://jacobin.com/2025/11/trump-golden-dome-nuclear-defense)”) and ever-more massive military spending, especially since the Soviet Union, America’s superpower rival in Reagan’s time, ceased to exist 35 years ago. Amazingly, Trump even wants to bring back naval battleships, as Reagan briefly did (though he didn’t have the temerity to call for a new class of ships to be named after himself). It’ll be a “[golden fleet](https://breakingdefense.com/2026/01/first-trump-class-battleship-could-cost-over-20-billion-cbo/),” says Trump. What gives? For much of my life, I’ve tried to answer that very question. Soon after retiring from the U.S. Air Force, I started writing for *TomDispatch*, penning my first article there in 2007, asking Americans to [save the military](https://tomdispatch.com/astore-on-a-military-bemedaled-bothered-and-beleaguered/) from itself and especially from its “surge” illusions in the Iraq War. Tom Engelhardt and I, as well as Andrew Bacevich, Michael Klare, and [Bill Hartung](https://tomdispatch.com/venezuela-the-revival-of-regime-change/), among others, have spilled much ink (symbolically speaking in this online era) at *TomDispatch* urging that America’s military-industrial complex be reined in and reformed. Trump’s recent advocacy of a “[dream military](https://www.pbs.org/newshour/politics/trump-proposes-massive-increase-in-2027-defense-spending-to-1-5-trillion-to-build-dream-military)” with a proposed budget of $1.5 trillion in 2027 (half a trillion dollars larger than the present Pentagon budget) was backed by places like the [editorial board of the *Washington Post*](https://www.washingtonpost.com/opinions/2026/01/14/trump-defense-spending-trillion/), which just shows how frustratingly ineffectual our efforts have been. How discouraging, and again, what gives? Sometimes (probably too often), I seek sanctuary from the hell we’re living through in glib phrases that mask my despair. So, I’ll write something like: *America isn’t a shining city on a hill, it’s a bristling fortress in a* [*valley of death*](https://bracingviews.substack.com/p/tis-the-season-for-war); or, *At the Pentagon, nothing succeeds like failure*, a reference to [eight failed audits](https://www.reuters.com/world/us/pentagon-fails-eighth-audit-targets-2028-pass-pentagon-says-2025-12-19/) in a row (part of a [30-year pattern](https://www.stephensemler.com/p/house-boosts-military-budget-as-pentagon) of financial finagling) that accompanied disastrous wars in Vietnam, Afghanistan, Iraq, and elsewhere. Such phrases, no matter how clever I thought they were, made absolutely no impression when it came to slowing the growth of militarism in America. In essence, I’ve been bringing the online equivalent of a fountain pen to a gun fight, which has proved to be anything but a recipe for success. In America, nothing — and I

A new report sheds light on how China's hidden structures in global lending limit the fiscal autonomy of debtor countries in the Global South

Here is the study: [HOW CHINA COLLATERALIZES (pdf)](https://www.kielinstitut.de/fileadmin/Dateiverwaltung/IfW-Publications/fis-import/cc13d44e-effc-4997-a9ad-c379487a7804-KWP_2293.pdf) The [How China Collateralizes (HCC)](https://www.kielinstitut.de/publications/how-china-collateralizes-18199/) report ... is the first comprehensive analysis of the secured lending practices of Chinese creditors in emerging markets and developing economies (EMDEs). The investigation draws upon in-depth case studies and a new dataset of collateralized public and publicly guaranteed (PPG) loans from Chinese state-owned institutions to EMDEs. In total, the dataset captures 620 collateralized PPG debt transactions worth $418 billion in constant 2021 USD over a 22-year period. The report and the dataset are available for download. Today, in conjunction with the release of How China Collateralizes, AidData has published a large cache of debt contracts—including loan, escrow account, mortgage, and debt restructuring agreements—between Chinese creditors and their overseas borrowers. In total, it has published 371 contracts between 19 Chinese creditors and 155 borrowers from 60 countries in an online repository. Digitized copies of the contracts can be accessed and searched by lender, borrower, sector, and contract clause at http://china-contracts.aiddata.org/. ... It took the team of researchers nearly four years to make sense of the opaque and complex borrowing arrangements that are documented in the report. The obstacles that they faced were formidable. Despite recent advances in debt data sharing, few bilateral or commercial creditors publish their secured lending terms. Many seek confidentiality commitments from their borrowers, impeding disclosure. Chinese creditors are no exception. They do not publish detailed or comprehensive data about their collateralized PPG loan agreements with EMDE borrowers. Their security and escrow account agreements are even harder to obtain. Quasi-collateral structures present an additional challenge: revenue routing and restricted accounts are substantially easier to shield from public scrutiny than liens over physical assets. The same structures can also **undermine fiscal autonomy, debt and revenue accountability, and macroeconomic surveillance**. ... The authors of the report made a number of unexpected findings. “We were surprised to find that almost half of China’s PPG lending portfolio, or nearly $420 billion across 57 countries, is effectively collateralized—mostly with deposits in bank accounts abroad,” said Christoph Trebesch of the Kiel Institute for the World Economy. “As security, Chinese lenders strongly prefer liquid assets—in particular, cash deposits in bank accounts located in China. They also want visibility and control over revenue streams.” ... Foreign currency revenues deposited in bank accounts controlled by Chinese lenders secure approximately 80% of the collateralized lending volume in the new dataset. A typical security package supporting a Chinese PPG loan includes one or more restricted (escrow) accounts at banks located in China, funded by revenues from the borrowing country, bolstered by contract and property rights in the cash flows. In many cases, the deposit account is at the creditor bank, which gives them a high level of control over some of the borrower’s core revenue streams, as well as set-off rights under Chinese law. ... The research team also found that **collateral is often unrelated to the stated purpose of the loan**. “We see Chinese lenders expanding and adapting standard market tools to make exceptionally risky loans safer,” said Anna Gelpern, a Georgetown Law Professor and Nonresident Senior Fellow at the Peterson Institute for International Economics. “Instead of relying on infrastructure project assets and future revenues, which may never materialize, they seek access to established export proceeds. Exporters commit to route these proceeds through offshore bank accounts over the life of the loan, which gives creditors leverage in the relationship as well as a source of repayment.” The report notes that the World Bank and the IMF have recently raised concerns about “collateralization involving unrelated assets or revenues” and warned that it is “likely to create problems.” ... According to the authors, commodity revenue sources vary by borrowing country, but typically draw on that country’s leading commodity export: oil in Angola, Iraq, Russia, Sudan, South Sudan, Equatorial Guinea, the Republic of the Congo, Brazil, and Venezuela; gas in Indonesia, Myanmar, and Turkmenistan; gold in Kazakhstan; copper and cobalt in the Democratic Republic of the Congo; bauxite in Guinea; platinum and tobacco in Zimbabwe; cocoa in Ghana; and sesame in Ethiopia. Oil proceeds dominate, accounting for 79% of the commodity-backed lending volume in the dataset. “Our research reveals a previously undocumented pattern of revenue ring-fencing, where a significant