Fil One Commerce is the quote-to-cash portal for Fil One. Customers, partners and staff work from the same commercial records: a quote becomes an accepted order with provisioning and payment records. Usage billing also supports a separate retained PAYG source, so invoices and corrections retain their actual commercial origin.
The repository has a working guided demo and substantial application, pricing, billing and approval infrastructure. Production activation still needs approved commercial/legal/tax policy, live provider mappings and an end-to-end pilot. This README does not declare a production launch.
Engineering ownership is a separate decision tracked in RFC #25. The implementation and demo do not establish an ownership commitment. Fil One Commerce is an internal portal, not a separately marketed product; its license remains evaluation-only.
Clockwork is the former project codename. Existing repository, package, and environment identifiers retain it for compatibility. The public product name is Fil One Commerce.
Open the sales demo. No password or account is required.
apps/showcase is the executive introduction and isolated interactive sales
tour, hosted on Netlify while tuning and ready for Vercel, with Next.js 16.3.8
and React 19.3. It requires no account, database, provider credentials, or
shared demo state. Run pnpm --filter @clockwork/showcase dev and open
http://localhost:3100.
The five-scene simulation connects one fictional quote, approval, order, service activation, and payment. Fil One integration is underway and will be available in November 2026. The tour also introduces proposed channel expansion, and its links open the full workspace demo for deeper exploration.
Open the full demo. Choose a customer, partner, or Fil One team workspace. All nine roles are available without a password.
Demo transactions use fictional data and deterministic provider adapters. They do not charge a card, provision a Fil One organization or prove that a live integration is ready. The hosted demo is deployed separately from GitHub merges; see deployment instructions.
To run locally without a database, use the Node version in .node-version and
pnpm 10:
corepack enable
pnpm install --frozen-lockfile
cp .env.example .env.localSet these values in .env.local:
CLOCKWORK_EXPERIENCE_ADAPTER=demo
CLOCKWORK_DEMO_DEPLOY=1Run pnpm dev, then open localhost:3000/demo.
Demo mode refuses production-marked environments. Finance personas can review
fictional price books, PAYG/trial policies, and channel controls in resettable
workspaces. Live administration requires an authenticated staff session and the
authoritative database.
| Area | Behavior |
|---|---|
| Quotes and orders | Versioned pricing, commercial review, acceptance and a shared order record |
| Commercial administration | Multi-rate price books, floors, transfer tiers, discounts, simulations and effective-dated channel controls |
| PAYG and trials | Versioned policy administration plus hourly usage rating, monthly minimum/correction and trial enforcement foundations |
| Billing and partners | Invoices, payment evidence, referral accruals, commission statements and financial corrections |
| Internal operations | Persisted queues and registries, audited decisions, and two-person capability activation with immediate disable controls |
Approved price versions and new quoted referral commission policies retain immutable economics. Existing contracts and legacy policy gaps require explicit handling. See the commercial administration guide, capability controls, and commercial readiness register for scope and limitations.
Contributor setup and commands cover the full local
Supabase app, architecture, tests and conventions. The main code is in
apps/web and packages/{api,domain,db,integrations,workflows}; canonical
migrations and database tests are in supabase.
The product specification describes intended behavior. The Fil One boundary design describes the required identity, provisioning, usage and billing integration. A design document or passing provider-fake test is not evidence of a completed production integration.
Before release, review the launch checklist, external gates, current CI runs, and commit-specific validation evidence. Repository checks and live-provider qualification are separate release requirements.
Fil One Commerce is evaluation-only; see LICENSE.