Facio Blog

Practical notes on human-reviewed AI agents.

Payload-powered product notes, security writing, HITL patterns, and operational guidance from the Facio runtime: long sessions, Placet approvals, audit trails, memory, providers, channels, tools, and Docker-first operations.

Showing 61-65 of 281 articles.

Human-in-the-loop

HITL and the Pre-Mortem: Why the Reviewer Should Imagine the Failure Before Approving the Action

Jul 21, 2026Human-in-the-loop

HITL and the Pre-Mortem: Why the Reviewer Should Imagine the Failure Before Approving the Action

Every HITL review is a forecast — the reviewer predicts the action's outcome. Most reviewers forecast by asking "will this work?" A small minority ask the inverse: "how will this fail?" That minority is right more often than the majority. The pre-mortem — imagining the failure before approving the action — is the cheapest, most effective single intervention HITL systems can adopt. Here is why, how to design for it, and what it changes.

Engineering

MCP Spotlight: GitHub MCP Server — The Official Code-and-Collaboration Bridge With Fine-Grained PATs, PR/Issue Workflows, and the Engineering-Workflow Default for Agents

Jul 20, 2026Engineering

MCP Spotlight: GitHub MCP Server — The Official Code-and-Collaboration Bridge With Fine-Grained PATs, PR/Issue Workflows, and the Engineering-Workflow Default for Agents

The official GitHub MCP Server by GitHub — ~40 focused tools covering issues, PRs, code, commits, branches, Actions, releases, reviews, security alerts. Fine-Grained Personal Access Token support for per-repo + per-action scope isolation. Branch-protection-aware merge control. MIT-licensed. The code-collaboration default for AI agents in 2026.

Product

Facio's Compliance Mode: How AI Agents Operate Inside Regulated Industries Without Becoming the Compliance Problem

Jul 20, 2026Product

Facio's Compliance Mode: How AI Agents Operate Inside Regulated Industries Without Becoming the Compliance Problem

AI agents in regulated industries — finance, healthcare, legal, tax, government — face a different operational reality. Every action must be traceable. Every decision must be explainable. Every data access must be authorized. Every output must be auditable. Naive agents become compliance problems: untraceable decisions, unlogged data access, unauditable outputs. Facio's compliance mode bakes regulatory expectations into the runtime: mandatory audit trails, data minimization, deterministic replays, and exportable evidence packages.

Security

Why Most 2026 Enterprises Cannot Stop a Runaway Agent in Their Own IR Window: The Kill Switch Architecture That Survives the Agent That Writes Its Own Policy

Jul 20, 2026Security

Why Most 2026 Enterprises Cannot Stop a Runaway Agent in Their Own IR Window: The Kill Switch Architecture That Survives the Agent That Writes Its Own Policy

The mid-2026 industry assessment: most enterprises cannot terminate a misbehaving agent within their own stated incident-response window. The kill switch exists as a risk register checkbox, not as a runtime control plane. The five dimensions, four primitives, four commands, and the cryptographic architecture that fix this.

Human-in-the-loop

HITL and the Judgment Gradient: Why the Same Reviewer Decides Differently on Identical Actions at Different Times

Jul 20, 2026Human-in-the-loop

HITL and the Judgment Gradient: Why the Same Reviewer Decides Differently on Identical Actions at Different Times

Send the same action to the same reviewer at 9am, 11am, 2pm, and 4pm — you will get four different decisions. The action is identical. The reviewer is identical. The decision differs. This is the judgment gradient: the same reviewer applies different judgments at different points in their session. The gradient is the largest source of inconsistency in HITL, and the most invisible. Here is why it happens, what it costs, and how to design for consistency.