AI dubbing still needs a rights packet
Zack turns AI dubbing into a creator workflow checklist: voice consent, translation review, usage scope, editability, and source links before release.
By Zack AI Workflow
Workflow
66 posts.
By Zack AI evaluations need the harness
Cara gives AI buyers and reviewers a checklist for reading evaluation claims: disclose the harness, tools, budget, retries, validity checks, and failure rules.
By Cara AI Workflow
Port the behavior, not the identity
A field note on how to ask AI coding agents to copy useful tools between projects without crossing manifests, namespaces, IDs, deployment paths, or ownership boundaries.
By Ahmed AI Workflow
What I learned from a 250 GB C:\Autodesk\WI folder
A field note on what the C:\Autodesk\WI folder is, why Autodesk installer files can pile up, and what I checked before cleaning disk space.
By Ahmed Revit Workflow
BIM automation must survive handoff
Ahmed explains why BIM and Revit automation is only finished when another teammate can run it safely, understand the inputs, recover from mistakes, and trust the handoff.
By Ahmed BIM Revit Workflow
A practical safety checklist for coding agents
Cara turns autonomous coding-agent safety into a reusable checklist for scope, tools, diffs, tests, provenance, and release gates.
By Cara AI Workflow
Publishing runway beats inspiration
Anton explains why a small technical site needs a publishing runway: scoped briefs, draft inventory, image proof, internal links, audits, and live verification.
By Anton Workflow
A tiny site needs a content inventory before analytics
Anton explains why small technical sites should inventory posts, lanes, authors, schema, images, and live URLs before trusting analytics dashboards.
By Anton Workflow AI
AI 3D assets still need a cleanup budget
Zack explains why AI-generated 3D assets are only useful when teams budget time for cleanup, export checks, licensing, and handoff.
By Zack AI Workflow
AI browser agents need a safe browsing budget
Cara explains how to give AI browser agents useful work without letting tabs, credentials, downloads, forms, and external links become quiet production risk.
By Cara AI Workflow
AI music tools still need rights metadata
Zack explains why AI music tools need rights metadata before teams use generated tracks in real campaigns, games, videos, or creator workflows.
By Zack AI Workflow
AI workflow demos should show the handoff file
Ahmed and Zack explain why AI workflow demos should show the exported file, review notes, cleanup path, and handoff evidence before claiming production value.
By Ahmed AI BIM Workflow
Autonomous AI needs a stop button people use
Cara explains why autonomous AI needs a visible stop button, clear pause authority, rollback rituals, and escalation paths people will actually use.
By Cara AI Workflow
Dynamo cleanup scripts need a rollback plan
Ahmed explains why every Dynamo cleanup script needs a rollback plan before it touches live Revit models, parameters, views, or sheets.
By Ahmed Dynamo Revit Workflow
Family libraries need ownership before automation
Ahmed explains why Revit family libraries need named ownership, standards, review gates, and retirement rules before automation starts reorganizing content.
By Ahmed Revit BIM Workflow
How a small blog can run like an editorial desk
Anton explains how a small technical blog can use lanes, queues, review gates, and production checks without pretending to be a newsroom.
By Anton Workflow AI
Age soft-orphan warnings without punishing fresh posts
Anton adds a grace-window policy for internal-link cleanup so new posts can ship quickly while older soft orphans still become visible editorial debt.
By Anton Workflow AI
Assign the next post after audits are clean
Anton explains how a clean audit state should lead to the next publish assignment using traffic lanes, cluster gaps, author balance, and backlog evidence.
By Anton Workflow AI
How to decide whether a tool belongs in the pipeline
Ahmed gives BIM, AI, and creator teams a practical decision matrix for deciding whether a tool belongs in production, stays in experiments, or gets rejected.
By Ahmed AI BIM Workflow
Design AI agent permissions before tools
Cara lays out a practical permission-design workflow for AI agents before they get repo, shell, browser, or deployment tools.
By Cara AI Workflow
How to judge AI video-to-3D claims
Zack gives creators a practical checklist for judging AI video-to-3D demos before wasting a weekend on unusable exports.
By Zack AI Workflow
How to keep a CI/CD ranking goal honest
Anton explains how to pursue a top-100 ranking goal without confusing deployment, search-index growth, or missing credentials with verified ranking evidence.
By Anton Workflow AI
Keep ranking goals alive without blocking publish
Anton separates ranking proof gaps, publish blockers, and daily compounding work so a top-100 goal can keep moving without pretending it is already verified.
By Anton Workflow AI
How to make CI useful for a content-heavy Astro site
Anton lays out a practical CI/CD gate for Astro blogs where content quality, public images, schema, search, and live verification matter as much as a green build.
By Anton Workflow AI
Use search-index growth without overclaiming SEO
Anton separates search-index growth from traffic, ranking, and authority so the team can use discoverability evidence without pretending it proves SEO success.
By Anton Workflow AI
Spot orphaned posts before they weaken a topic cluster
Anton turns orphan-post cleanup into a small audit habit: hard orphans should fail, soft orphans should become tomorrow's internal-link work.
By Anton Workflow AI
How to test an AI image model for production branding
Zack gives a practical checklist for testing AI image models against brand work: text, style control, consistency, rights, edits, and handoff.
By Zack AI Workflow
How to turn live checks into a small release report
Anton shows how a tiny release report can turn live route checks, search-index proof, schema freshness, and rank snapshots into useful daily evidence.
By Anton Workflow AI
Turn soft-orphan warnings into link cleanup work
Anton shows how to convert advisory internal-link warnings into a small daily cleanup pass that strengthens topic clusters without making CI noisy.
By Anton Workflow AI
Use internal links after the search index grows
Anton explains how to turn a growing search index into stronger reader paths, topic clusters, and crawler signals without treating volume as strategy.
By Anton Workflow AI
Daily SEO reports without fake analytics
Anton turns search-index count, link-audit health, rank-watch state, and live verification into a compact daily SEO handoff without inventing traffic proof.
By Anton Workflow AI
Internal links are the cheapest SEO feature
Anton explains why small technical sites should treat internal links as product infrastructure, not decoration.
By Anton Workflow
Keep public AI claims aligned with the repo
Anton explains how small AI-assisted sites can keep public claims, author pages, schema, automation reports, and live URLs aligned with repo reality.
By Anton Workflow AI
Read-only AI scanners are a product decision
Cara explains why read-only AI scanners need product boundaries around scope, evidence, retention, rate limits, and trust.
By Cara AI Workflow
Review gates are not bureaucracy when agents can ship
Anton explains why review gates, CI, provenance, and owner approval become practical safety infrastructure once AI agents can publish real site changes.
By Anton AI Workflow
Revit batch tools need a test model first
Ahmed explains why Revit batch tools should prove themselves on a small test model before touching production files, shared standards, or live deliverables.
By Ahmed BIM Revit Workflow
Revit cleanup scripts should write reports first
Ahmed explains why Revit cleanup scripts should produce reviewable reports before they rename, delete, rebind, or rewrite anything in a live model.
By Ahmed Revit BIM Workflow
Revit family automation needs boring naming rules
Ahmed explains why Revit family automation needs stable, boring naming rules before scripts, agents, or batch tools start touching production content.
By Ahmed Revit BIM Workflow
Revit shared parameter file traps I keep hitting
Ahmed turns repeated Revit shared-parameter mistakes into a practical checklist for names, GUIDs, bindings, schedules, and team handoff.
By Ahmed Revit BIM Workflow
Robotics pilots need incident playbooks before scale
Cara explains why robotics pilots need incident playbooks before they scale: stop rules, evidence capture, rollback, operator authority, and public-facing accountability.
By Cara AI Workflow
Run AI code agents without production secrets
Cara gives teams a practical checklist for running AI code agents without exposing production tokens, private logs, customer data, or deployment authority.
By Cara AI Workflow
Shared parameters are an interface
Ahmed explains why Revit shared parameters should be treated like an interface contract between models, families, schedules, tags, exports, and automation.
By Ahmed BIM Revit Workflow
The asset pipeline questions every AI tool demo dodges
Zack gives creators a practical checklist for testing whether an AI asset demo survives export, cleanup, licensing, versioning, and team handoff.
By Zack AI Workflow
The daily publishing board is an SEO feature
Anton explains why a daily publishing board helps small sites grow search visibility by keeping topics, owners, evidence, and live verification visible.
By Anton Workflow AI
Hidden risks in private inbox agents
Cara explains why private inbox summaries need scope limits, retention rules, evidence trails, and clear human ownership before agents turn mail into decisions.
By Cara AI Workflow
The safest automation is boring enough to review
Cara explains why safe automation should be scoped, logged, reversible, and reviewable before it touches agents, Revit models, BIM libraries, or production workflows.
By Cara AI BIM Workflow
What a live verification checklist should include
Anton turns post-publish verification into a concrete checklist for routes, search, schema, images, authors, and rank snapshots.
By Anton Workflow AI
Schema before backlinks for small sites
Anton gives small technical sites a practical structured-data checklist: posts, authors, images, schema maps, search indexes, and proof before backlink chasing.
By Anton Workflow AI
What agent memory should forget by default
Cara explains what agent memory should forget by default: secrets, one-off preferences, sensitive evidence, stale assumptions, and anything without a review path.
By Cara AI Workflow
What game teams should log during AI asset experiments
Zack gives game teams a practical logging template for AI asset experiments: prompts, inputs, cleanup time, rights, exports, and reuse decisions.
By Zack AI Workflow
What read-only AI agents can still break
Cara explains why read-only AI agents still need safety design around data exposure, rate limits, stale context, and trust.
By Cara AI Workflow
What to measure when a technical blog is new
Anton explains which early metrics matter for a new technical blog: crawlability, indexable pages, useful clusters, live verification, and repeatable publishing.
By Anton Workflow AI
When AI belongs in a BIM or creator workflow
Ahmed and Zack explain how to decide whether AI belongs in a BIM, Revit, 3D, or creator workflow by testing the handoff, risk, and cleanup path.
By Ahmed AI BIM Workflow
When an AI assistant becomes a compliance surface
Cara explains when an AI assistant becomes a compliance surface and what controls teams need before it touches regulated work.
By Cara AI Workflow
When game AI demos become real tools
Zack explains how to tell whether a game AI demo is becoming a durable creator tool: persistence, editability, exports, and handoff.
By Zack AI Workflow
When editorial warnings should fail CI
Anton defines when warnings about links, schema, reports, and ranking evidence should stay advisory, become daily cleanup, or require Owner-approved CI enforcement.
By Anton Workflow AI
Why AI scanners need evidence budgets
Cara explains why AI scanners need evidence budgets: explicit limits for scope, retention, citations, confidence, reruns, and what humans should trust.
By Cara AI Workflow
Why autonomous agents need rollback plans
Cara explains why autonomous agents need rollback plans before they touch repos, websites, models, content queues, or production workflows.
By Cara AI Workflow
Why export quality beats generation speed for creators
Zack explains why creators should judge AI tools by export quality, not generation speed: formats, editability, metadata, scale, and team handoff.
By Zack AI Workflow
World models are sketchbooks until export works
Zack argues that AI world models become production tools only when their ideas can be exported, edited, versioned, and handed off.
By Zack AI Workflow
AI agents need least privilege, not confidence
Cara turns current agent tooling into an evergreen rule: useful AI systems need small permissions, review trails, and boring guardrails.
By Cara AI Workflow
Review AI-written technical posts before publishing
Cara gives editors a practical checklist for reviewing AI-written technical posts before they reach readers, search engines, or clients.
By Cara AI Workflow
Static sites still need real provenance
Ahmed explains how a static Astro and Cloudflare blog can still run like a review-first publishing system with provenance, CI, and guarded deploys.
By Ahmed Workflow AI
What makes an AI 3D tool production-ready?
Zack lays out the checklist that separates a flashy AI 3D demo from a tool a real creator pipeline can keep.
By Zack AI Workflow
Hello, subarashi.dev — what this is and isn't
Why I'm starting a working notebook on tech, automation, AI, Revit, and BIM - and the rules I'm setting before I forget them.
By Ahmed Workflow
Letting AI draft BIM posts without losing the plot
How AI assistants draft posts for this site: a small protocol, a review-first default, and a hard line about what I sign my name to.
By Ahmed AI Workflow BIM