Blog
News, tutorials, and insights from the PhiWebs team.
Featured
Receipt: the contract between AI and your CISO
Most AI builders publish first and apologise later. PhiCo emits a Receipt — a signed, line-numbered, diffable record of every change — and waits for you to accept it. Here is how it works and why it matters.
PhiSo: surfaces that answer their own visitors
Site-wide chatbots hallucinate because they have no idea what page the visitor is on. PhiSo reads the live Surface contract, so it answers from the page itself — not from a year-old training corpus.
All Posts
45 production blocks, one pipeline: how pwpack works
PhiCo cannot invent a component that does not exist. Every block lives in a manifest, every manifest publishes through the same pipeline — first-party or community. No second-class extensions.
From v1.0 to AI-Native: how PhiWebs evolved
A short retrospective. v1.0 shipped a usable Surface platform. Then we noticed that the AI conversation was happening with or without us, and rebuilt the product around a Receipt-first composer.
Stay in the loop
Subscribe to our newsletter for product updates, tutorials, and insights.
No spam, ever. Unsubscribe anytime.