Technical Blog
R&D practices, architecture insights, GEO/SEO optimization experience — all from front-line delivery.
AI Comic Workflow Architecture: Model Orchestration, Asset Library and Batch Scheduling from Script to Final Cut
AI comics aren’t "drawing a few images with AI" — they’re a production line from script to final cut that is batchable, reproducible and style-consistent. This piece breaks down the five stages and three engineering hard parts: model orchestration, asset library and character consistency, batch scheduling — and why private deployment is a must for production teams.
The AI Crawler Whitelist: 13 User Agents Your robots.txt Should Allow (2026)
Blocking AI crawlers means forbidding AI engines from citing your content. This is the 2026 list of 13 mainstream AI crawler user agents (OpenAI, Perplexity, Anthropic, Google), what each one actually does, a copy-paste robots.txt config and how to decide about training bots.
How to Write llms.txt: A Complete Guide to the AI Crawler Site Manifest (with Template)
llms.txt is a plain-text file at your site root written specifically for AI crawlers and agents. This guide covers where it came from, the block-by-block format, a copy-paste template and the three most common mistakes — all from a real production rollout.
Compliant Data Scraping in Practice: Staying Clear of Legal and Anti-Bot Red Lines (2026)
Data collection isn’t about "can we grab it" — it’s about "can we grab it compliantly and stably for the long run." This piece lays out a deliverable scraping method: how to draw the compliance boundary, how to read robots and authorization, how to handle anti-bot gracefully instead of fighting it, how to do schema docs and sampling verification, and three anti-patterns that sink projects.
Anatomy of an AI Acquisition System: Content Engine, Lead Scoring and Opportunity Routing
An operable AI acquisition system has four modules: a multi-channel content engine, contact capture, lead scoring, and opportunity routing with conversion review. This teardown covers each module's responsibility boundary, the key design decisions, and the traps — for teams evaluating build vs. buy.
GEO in Practice: Making Your Website Discoverable by AI Assistants (2026 Guide)
GEO (Generative Engine Optimization) is how you make ChatGPT, Perplexity and Claude able to crawl, understand and cite your website. This guide walks through all 7 layers — JSON-LD, llms.txt, AI crawler whitelisting, FAQ schema, sitemap, canonical/OG tags and BLUF content structure — based on a real production rollout.
An Engineering Method for Taking Over Legacy Systems: From Code Audit to Regression Fix
Taking over an undocumented legacy system whose original developer is gone — the biggest risk isn’t failing to read the code, it’s "change one thing, break three." This piece gives a five-step engineering process: environment restoration, code audit, characterization-test safety net, incremental fixes, knowledge handover — each with an explicit deliverable.
AI Token Trading Platform Architecture: Multi-Supplier LLM Compute Aggregation and Matching
A Token trading platform for LLM inference compute aggregates multiple suppliers (OpenAI, Anthropic, open-source models), matches each request to the best price/latency option, and runs balance accounts, reconciliation and risk control behind one API gateway. This teardown covers the four-layer architecture and the key design decisions.
REST vs GraphQL vs gRPC: A Decision Framework for Backend API Protocols (2026)
The three mainstream API protocols each have a clear zone of fit: REST for external resource-style APIs, GraphQL for multi-client aggregation and fast-iterating front-ends, gRPC for high-performance internal service-to-service calls. This piece gives a framework organized by "who the caller is", with a typical combined architecture and three anti-patterns.
Astro vs Next.js for Static Sites: A 2026 Corporate Website Stack Decision Guide
Astro and Next.js are the two most popular static-site frameworks today. This piece compares them across 8 dimensions — SEO, GEO-readiness, build speed, maintenance cost, deploy complexity and more — and gives an actionable stack recommendation for corporate websites, with real build data from this site.
Ops Automation Script Patterns: Six Engineering Constraints from One-Off Script to Maintainable Tool
The value of ops automation isn’t "it ran once" — it’s "someone can safely run it again six months later." This piece gives six engineering constraints that upgrade a one-off script into a maintainable tool: idempotency, dry-run, explicit config, observability, fail-safety, least privilege — with a self-check list from "works" to "deliverable."
How to Run a Technical Review: A Method for Selection, Architecture Review and Feasibility Reports
A technical review isn’t "an expert declaring this works and that doesn’t" — it’s a reproducible decision method: define evaluation dimensions and weights first, score candidates against them, then replace verbal judgment with feasibility verification (PoC). This piece gives the full selection-review framework, what a feasibility report should contain, and three bad habits that void a review.