Blog

Notes on AI planning, governance gates, live-infrastructure-grounded plans, and what we learn building PFactory — the Plan Factory in front of the execution agents.

• Jul 23, 2026 What shipped in PFactory: code-aware plans, hardened boundaries A round-up of the recent work — reconnaissance that reads the target repo before it plans, SpecKit constitutions the readiness gate enforces, deployment-aware plans, and a path-injection barrier that shuts a class of traversal bugs at the choke points.
• Jul 19, 2026 Planning that reads your code PFactory does not guess at a plan from a prompt. It clones the target repo, reads it, and signs a contract about that specific codebase — then hands it to a factory that builds, tests, and grades the result unattended.
• Jul 17, 2026 The issue becomes the plan A GitHub issue is now a first-class intake channel: the from-issue endpoint is live in production, dev and main are reconciled, and plan sessions learned to carry a tenant.
• Jul 13, 2026 The plan is where the money is decided How the planning stage sets the routing policy the rest of the factory spends against, and why a cost number only means something if planning is honest first.
• Jul 7, 2026 Planning joins the shell: one product, one sign-on, the latest models PFactory's planning portal picks up the fleet-wide command palette, needs-you badge, and silent single sign-on — and moves onto Claude Opus 4.8. A one-page showcase is ready to download.
• Jun 23, 2026 The bill arrives before the build does A plan costs real money to produce — detect, decompose, synthesize, govern — and most of that is spent before anyone approves it. PFactory now reports a plan session's cost as a running figure the moment it is ready for review, not only when it reaches a terminal outcome. So a plan you park, or abandon, no longer shows up as a free $0.
• Jun 21, 2026 The week the plan learned to argue with itself A red-team lens that attacks the spec before a human signs it, deployment-aware planning that derives where the work runs, cost-aware model routing, and the concurrency groundwork that lets PFactory plan many things at once. Week of 2026-06-15 to 2026-06-21.
• Jun 13, 2026 Security hardening, and the allowlist that finally reads shell Four merges in one session: closing a named CVE pattern in the Copilot review workflow, making the MCP surface and the boot guard fail closed, and replacing the regex command allowlist with a real shell-grammar parser that sees inside $(...), backticks, and pipes.
• Jun 10, 2026 The signed plan AIFactory quietly threw away A 422 on the handoff made PFactory fall back to re-planning — silently. v0.6.13 fixes the trusted-plan path so the governed contract survives the boundary.
• Jun 9, 2026 PFactory speaks GitHub's agentic language Free GitHub Models inference, Copilot cloud-agent delegation, an MCP server that hands the plan to whoever is building it, and the Actions that wire it all together — PFactory now plugs straight into GitHub's native agentic surface, opt-in and additive.
• Jun 5, 2026 0.6.0: PFactory joins the catalog, and starts counting its own cost PFactory is now a first-class citizen of the Backstage software catalog with TechDocs, and its completion events carry the token usage CFactory needs to attribute spend across the Factory family.
• Jun 4, 2026 The planning engine is live: feasibility you can trust, emit you can govern PFactory now takes a plan end-to-end — enrich, price it against your real cloud, review it with cited findings, honour the document, and emit governed GitHub issues. Here's everything that shipped, and a demo.
• Jun 3, 2026 Plan from the running system, not just the prompt Most AI planners read your prompt. PFactory also reads your cluster, your cloud, and your catalog — before it writes a single issue.
• Jun 3, 2026 Introducing PFactory: the Plan Factory The autonomous-coding world collapsed planning into execution. PFactory pulls it back out — and puts a governance gate in front of every agent.
• Jun 2, 2026 Make the plan the reviewed artifact When agents plan inside the execution loop, there's nothing to approve until the code already exists. PFactory moves the review forward.