We are looking for an expert backend developer and automation engineer to extend an existing, production-grade Model Context Protocol (MCP) server and overhaul its orchestration layer. The headline correction for this project: the existing Lawfather MCP is to be retained and extended, not rebuilt. It already exposes deterministic, parameterized Playwright tools for every required county portal (District Clerk, HCSO, HCDAO) and a client database. Those backend tools are the reliable layer and are not the source of the instability this project exists to fix. The instability lives entirely in the orchestration layer — the model-driven layer that decides when and how to call the tools. The fix is to move deterministic control out of model-followed prose and into code, and to host the agent on an always-on machine with persistent memory. Core Project Principles • Extend, Don't Rebuild: Retain and extend the existing MCP; do not re-implement portal scrapers from scratch. • Code Over Prompts: Deterministic logic lives strictly in tool code, never in instructions the model must remember each session. • No Caller Loops: Batch operations must run to completion server-side. No operation may require the caller (model) to loop. • Agnostic Architecture: The system must remain model-agnostic and host-agnostic. No single provider — Anthropic, OpenAI, Z.ai/GLM, or Nous — may be a hard dependency. • Privilege First: Client data stays on owned hardware; the model is never the gatekeeper of which case a file belongs to. Existing Tool Inventory (To Be Inherited As-Is) The following tools already exist on the production MCP (containerized on a local Synology NAS) and are in daily use. Re-deriving their behavior is completely out of scope: • hcdc_get_docket: Court settings by date range + bar number (District Clerk). • hcdc_check_filings: Per case: standard defense filings present vs. missing. • hcdc_download_filings: Images-tab documents: bulk OR selective by filters; dest_subfolder; dry_run. Note: The parameterized download tools already cover most retrieval requests. "All filings," "this filing," "all subpoenas," "all resets," and "everything filed that day" are argument combinations on this tool, not separate features. • hcso_locate: Defendant custody location (facility / floor / pod) by SPN. • hcdao_grab_file: Download a single named file from the DA portal Files tab. • hcdao_download_discovery: Batch / delta discovery download from the DA portal. • hcdao_download_media_alert: Batch-download files listed in a 'New Media Available' portal email. • hcdao_case_summary: Scrape the Case Jacket quick summary / DAO narrative. • hcdao_plea_offer: Scrape current plea offer + full offer history. • hcdao_assigned_ada: Assigned ADA name / email / phone on a case. • lookup_client / list_clients: Resolve / list clients from the shared client database. Scoped Work (Paid Deliverables) 1. County Case Resolver (New Tool): Find a case from partial identifiers — any subset of (name, SPN, DOB, court, cause). Searches county systems (not just the local client DB). MUST return a ranked candidate list for the user to choose from; MUST NEVER auto-select. Wrong-defendant selection is a privilege failure, not a cosmetic bug. 2. Latest-Version Retrieval: Add scope=latest to hcdao_grab_file so 'most recent' selects the newest among supplements instead of the first match. 3. Async Transcribe Tool (Skill to Tool Promotion): Build a deterministic MCP tool using Gemini 3.1 Pro Preview for transcription, followed by a second pass that sends the transcript back with case context for cleanup (speaker mapping, defense-moment preamble). Long-running: implement as an async job (submit to job id to poll to fetch), NOT a synchronous call. 4. OCR Tool (Skill to Tool Promotion): Implement a readability check on ingest. If a document is not cleanly readable, FLAG it and ASK before sending to Gemini 3.1 Pro Preview for OCR. OCR must be gated and confirmed, never automatic. 5. Server-Side Batch Jobs: Move all chunk, loop, delta, and throttle logic OFF the caller and INTO the tool code. One call runs the batch to completion. 6. Queued HCDAO Fixes: For hcdao_download_discovery, add a portal_ids filter for targeted single-file pulls and a custom output-path / Drive-folder destination feature. Known Portal Quirks to Handle from Day One • hcdc_get_docket returns a broader date range than requested; results must be filtered to the requested window. • hcdao_download_discovery delta detection is blind to files organized into dated subfolders and must be explicitly handled. • Court DG7 does not surface through standard bar-number docket lookup and requires separate handling. • The Playwright Node.js driver subprocess can die silently while database tools respond; you must health-check the driver proactively. Orchestration, Host Layer, & Deployment Topology • Target Host: Hermes Agent (Nous Research) running as the persistent shell, providing persistent memory, the scheduler, and messaging surfaces. The MCP server will plug directly into it. • Agnostic LLM Routing: Default the agent/dispatch role to the most reliable tool-calling model (currently Claude Opus). Route bulk, non-critical generations (draft summaries, transcript cleanup) to a cheaper model (e.g., GLM-5.2). No provider may be hard-wired. Per-tool pins are allowed strictly for transcription/OCR tasks (pinned to Gemini 3.1 Pro Preview). • Memory Fencing: Hermes's persistent memory and learning loops must remain enabled to accumulate facts and user preferences. However, the agent must be strictly fenced from self-editing or rewriting its own mechanical execution paths (portals, downloads, filings), which must remain frozen in MCP tool code. • Hardware Deployment Infrastructure: • Always-on Brain: M1 Pro MacBook Pro (16 GB, mains-powered, lid open) running the Hermes gateway, Messages.app, and a BlueBubbles iMessage bridge. Must be fully automated via launchd services to handle headless crash recovery, auto-login, and sleep prevention (pmset autorestart / caffeinate). • Tools and Storage: Synology NAS (10.0.0.149) hosting the Lawfather MCP container, local client folders, and Drive sync. • Private Network: Tailscale mesh across all devices for secure remote access without open inbound ports. Acceptance Criteria for Sign-Off • No batch operation requires the caller to iterate. • The case resolver returns ranked candidates and never auto-selects. • Transcription runs seamlessly as an async two-stage job surviving multi-hour files without timing out. • OCR never fires automatically on low-readability files without gated confirmation. • Zero regressions on the existing MCP tool inventory. • The Resiliency Test: The full stack successfully restarts completely unattended after a host reboot or simulated power loss, and is reachable via iMessage/SMS immediately after. • Self-editing is fenced on mechanical download/filing paths. Hard Guardrails • Privilege: Downloads route strictly to the correct client folder; a wrong-case match is treated as a severe defect, not a warning. Privileged audio/discovery data stays on owned hardware where the chosen model allows. • Determinism: Repeatable steps live entirely in tool code, never in prompts. • Agnosticism: Model and host layers must remain fully swappable without modifying the core MCP tools. Before quoting "done," you will be expected to confirm live portal behaviors regarding District Clerk document labels, DA portal stable identifiers, and county search surfaces. How to Apply Please submit a proposal detailing your specific experience with MCP architectures, Playwright browser automation, and macOS/Docker DevOps automation. Anti-Bot Filtering: To prove you read this entire scope, please start your application with the phrase "PROTECT THE LAW" in all caps. Automated or generic copy-paste applications will be instantly rejected.

Project Overview We are an energy distribution and marketing company running Microsoft Dynamics 365 Business Central. We are evaluating whether we can build an internal cash application automation workflow instead of purchasing a third-party SaaS solution. The objective is to automate the matching of incoming customer payments to open invoices using: Bank transaction feeds (BAI2 files from Frost Bank) Remittance emails from Outlook Open AR invoices in Business Central AI-assisted matching where appropriate This is not a chatbot project. This is an accounting workflow automation project. Current Process Treasury downloads bank activity. Treasury reviews remittance emails. Accounting manually identifies customer payments. Accounting matches payments to open invoices. Accounting creates and posts entries in Business Central. We would like to reduce manual effort while maintaining accounting review and approval controls. Desired Future State Data Sources Frost Bank BAI2 files Outlook shared mailbox containing remittance emails Business Central: Open AR invoices Customer master Vendor master Payment journals Workflow Read incoming remittance emails. Extract: Customer name Payment amount Invoice numbers Payment references Read bank transactions. Match payments to customers and invoices. Generate confidence scores. Present suggested matches for review. Push approved entries into Business Central Payment Reconciliation Journal or Cash Receipts Journal. Maintain audit trail of AI recommendations and user approvals. Deliverables Requested Phase 1 – Discovery Provide: Recommended architecture Estimated implementation effort Recommended technology stack Estimate of expected match rates Build vs buy recommendation Phase 2 – Proof of Concept Build a prototype that: Reads remittance emails Parses BAI2 transactions Pulls open invoices from BC Suggests invoice matches Provides confidence scoring Phase 3 – Production Build Optional based on successful POC. Preferred Technology Strong preference for: Microsoft Business Central Power Automate Azure OpenAI Azure Functions BC APIs SQL Server/Azure SQL Open to alternatives if justified. Required Experience Please provide examples of: Microsoft Business Central projects Payment reconciliation projects Cash application automation Bank integration projects AI-assisted document processing Accounting or ERP workflow automation Screening Questions How many Business Central implementations have you personally worked on? Have you integrated BAI2 bank files before? Have you built payment reconciliation workflows? What match rates would you expect before and after AI assistance? Would you use Power Automate, Azure Functions, or another architecture? What are the biggest risks in this project?

Job Title: Automation & AI Developer — Solar Interconnection Workflow System Project Overview: We are a small but fast-growing startup in the Texas solar/energy sector looking for an experienced automation developer to build a multi-portal workflow automation system. This system will eliminate manual data entry, automate government and utility portal submissions, and use AI to analyze and validate photos. This is a paid project with strong potential for ongoing Phase 2 work as the platform grows. What You Will Build: 1. Multi-Portal Web Automation Using Playwright or equivalent browser automation tools you will automate login, navigation, form filling, file uploads, button clicks, page load waiting, and data extraction across multiple web portals including a utility interconnection portal, a project submission portal with existing API access, and a city permit portal. The utility portal specifically requires multi-page form completion, calculate button interactions with 5-15 second page refresh waits, file downloads, and triggering DocuSign email delivery to customers. 2. API Integration One portal has existing API access. You will build direct API calls for data submission and photo uploads to that portal rather than browser automation. 3. AI Photo Analysis — Two Functions First, field photos of electrical equipment must be analyzed using AI vision (Claude, GPT-4V or equivalent) to automatically extract technical data and pre-fill intake forms — eliminating manual data entry. Second, homeowner-submitted photos received via SMS must be automatically analyzed for completeness and quality. If a photo is blurry, incorrect, incomplete, or unusable the system must prompt the homeowner to retake and resubmit before the photo enters the workflow. 4. Automated Customer Notifications Immediately following the utility portal DocuSign email trigger the system must automatically send the homeowner an SMS message instructing them to check their email and sign the DocuSign document. 5. Status Monitoring & Polling The system must automatically check utility portal application statuses on a scheduled basis over a multi-day period and alert the team when a status changes or receives approval. If a DocuSign link expires without being signed the system must reinitiate the email and send the homeowner a new SMS notification automatically. 6. Mobile Application Integration This automation system will need to integrate with a proprietary mobile application currently in development. All work must be built with clean integration in mind from day one — API-ready, well-documented code is required throughout. This system will also need to support incoming and outgoing webhooks with an existing CRM for specific workflow triggers. Thorough documentation is required as a deliverable, not an afterthought. The developer must treat all systems, workflows, and code as strictly confidential. 7. Central Dashboard A simple internal dashboard to view all active jobs, their current stage in the pipeline, status updates, visual graphs or charts for easy review and identification of issues, and any items requiring human attention or intervention. Required Skills: Playwright or Puppeteer browser automation, REST API integration, AI vision API experience (Anthropic Claude or OpenAI), backend development (Python or Node.js), webhook and SMS integration (Twilio or equivalent), scheduled job and polling workflow experience, basic frontend for internal dashboard, experience building systems designed for third party app integration. Important: All code and intellectual property produced under this contract is owned exclusively by the client. A work-for-hire and IP assignment agreement must be signed prior to project commencement. An NDA is also required. Do not apply if you are unwilling to sign these agreements. To Apply: Please share examples of similar automation or RPA projects you have built, specifically any experience with government or utility portal automation, multi-step form automation, or AI vision integration. Include your proposed timeline and fixed-fee project quote.

We are looking for a strong software engineer who can build practical automation systems using AI, APIs, and modern development tools. This role is for someone who can take messy business workflows, understand the goal, and build working systems that save time, reduce manual work, and improve execution. You should be comfortable building automations, integrating tools, working with APIs, writing clean code, and using AI tools like OpenAI, Claude, or similar models to create useful business applications. What You’ll Work On You will help build and improve systems such as: AI-powered research and data extraction workflows CRM and sales process automations Email, spreadsheet, and database automations Internal tools and dashboards API integrations between business software Web scraping and data enrichment workflows when appropriate AI agents or assistants that help with repetitive business tasks Automation around deal screening, reporting, lead research, and document creation Ideal Candidate We are looking for someone who is practical, fast, and can figure things out without needing step-by-step instructions. You should have experience with: Python and/or JavaScript APIs and webhooks OpenAI, Claude, or other LLM APIs Automation tools like Zapier, Make, n8n, Airtable, Google Sheets, HubSpot, Salesforce, or similar Databases such as PostgreSQL, Supabase, Firebase, or similar Basic front-end or internal tool development Web scraping, data cleaning, and structured data workflows GitHub and clean documentation What Matters Most We do not need someone who only talks about AI. We need someone who can actually build. The right person should be able to: Understand a business process quickly Recommend the simplest technical solution Build fast prototypes Turn prototypes into reliable workflows Communicate clearly Document what was built Improve systems over time Nice to Have Experience with any of the following is a plus: Private equity, M&A, finance, or investment workflows Deal sourcing or lead generation systems CRM automation Data enrichment tools AI research agents Browser automation Cloudflare, AWS, Google Cloud, or similar infrastructure Engagement This will start as a part-time project-based role, with the potential to become ongoing if the work is strong. Estimated workload: 5 to 15 hours per week to start. To Apply Please include: Examples of automations or AI tools you have built The tech stack you usually work with A brief explanation of how you would approach automating a messy manual workflow Your hourly rate Your availability Please do not send a generic application. If your response looks copied and pasted, it will be ignored.