AI-Native Surface OS
Describe it. Ship it. Let it speak.
PhiCo turns intent into a reviewable Receipt. PhiSo makes every published surface answer its own visitors. 45 production blocks. One platform.
Used by teams who need AI velocity with audit-grade control.
Intent
▌
1// Composing…01 — PhiCo
Intent → Receipt → Surface
You describe what you want. PhiCo proposes a Receipt — a signed, line-numbered recipe of every block, capability, theme token and data binding it will use.
Nothing ships until you accept the diff. The Receipt is the contract. Reviewers see exactly what changed. Compliance gets an immutable audit record. The surface, when published, is bit-for-bit reproducible from that Receipt.
This is not a chat with a code generator. It's a build pipeline with a paper trail.
02 — PhiSo
Surfaces that answer their own visitors.
Drop the PhiSo widget on any published surface. It reads the live page through the Surface contract — no extra training, no hallucinated facts.
Visitors ask: "How do I cancel?", "What's the SLA on the Pro tier?", "Where do I upload the W-8?". PhiSo answers from the surface itself, fills forms it's allowed to touch, and escalates what it can't.
Grounded in the Receipt. Scoped to the surface. Never invents.
03 — Blocks
45 production blocks. Four packs. One contract.
AI doesn't invent components. It picks from a real, typed, manifest-described atom catalog — the same one human composers use.
phiwebs-ui — 24 blocks
phiwebs-data — 7 blocks
phiwebs-nav — 5 blocks
phiwebs-forms — 9 blocks
Every block carries a manifest with an AI knowledge brief (props, intent, edge cases, examples). That's why PhiCo never reaches for a component that doesn't exist.
Browse the catalog →04 — World
A multi-tenant runtime that takes itself seriously.
Every customer gets a World — an isolated aggregate of identity, blueprint, plan, members, entity graph, behavior rules and storage.
Worlds don't leak. Worlds version. Worlds audit. The runtime sits on a stable, versioned platform contract — so the floor doesn't shift under your AI surfaces.
- Versioned platform contract
- 45 production blocks
- 5 first-party capabilities
05 — Trust
AI that your CISO can sign off on.
Operator console for staff. Per-tenant audit logs. Receipt diff before every publish. KVKK + GDPR data-subject flows wired into the contract layer.
- Receipt diff: human-readable, line-numbered, never auto-applied.
- Operator audit trail: every staff impersonation logged with reason.
- Atom Knowledge Schema: AI sees only what each block declares.
- Tenant-scoped context: zero cross-World data bleed.
06 — Marketplace
pwpack — one pipeline for first-party and community.
Your custom blocks publish through the exact same pipeline that ships our 45 first-party blocks. No second-class extensions.
Write a block in TypeScript with `defineBlock`. Add a manifest. `pwpack publish`. It's now installable, AI-discoverable, and version-pinned inside any World.
How packs work →07 — Developer surface
Compose surfaces from your terminal.
PWFabric Studio is the Claude Code plugin for developers, agencies, and integrators — slash commands and MCP tools for the full surface lifecycle, plus end-to-end custom block authoring without installing a single SDK.
PhiCo composes inside the web app. Studio composes from your editor. Both follow the same composition rules — a surface built in one is indistinguishable from one built in the other.
How Studio works →Ship your first AI-composed surface this week.
Pay to start. No annual lock-in. Real production blocks from minute one.