the plan · from the smallest shop to the biggest of big
The machine is free today. The plan is the rest of the stack: an AI instance tuned to the means you have, with usage you can see; the marketing, analytics, and email tools you'd otherwise rent — as plugins you own; and full lifecycle management that scales from a crew of one to an enterprise. Here is what's real, what's next, and what's the plan.
choose the engine — the harness makes every one of them go further
Spruce Grove runs on the AI you choose: Synthetic.new, Claude, ChatGPT, or your own setup. You bring the subscription you can afford; the harness stretches it — transparent usage you can watch as it lands, session history that survives anything, context you can steer mid-run, and model routing that spends cheap tokens on small work and saves the strong ones for the hard parts. One command sets it up; one command checks it any time.
Starting from nothing. Free engine access or the cheapest tier that exists.
One subscription, stretched by the harness until it behaves like a bigger one.
Your accounts, your policies, your scale — the same machine at enterprise size.
the grove's architecture is plugin-first: these bolt onto the machine you already run — planned, not shipped; honest by design
The dashboard a business actually opens: who came, what they looked at, what turned them into a customer — on your own site, in your own instance.
A marketing engine like the big platforms — except the platform is yours, and the compliance is a design law, not a settings page you hope you got right.
The reason the two cards above say "planned" with confidence: the machine was born plugin-first — every capability above hangs on hooks that exist today, contributed like everything else in the grove.
The drones build already crossed this bridge by hand: registrar, DNS, verification, certificates — scripted, gated by a human, verified live. The plan is to make that walk a single auditable command for every business in the grove.
identity as the key: access, tools, and software that follow your role and need — from a crew of one to the biggest of big
A new person, role, or need appears — and the access, tools, and accounts that role requires appear with it. Dynamically, by identity and need, with every grant recorded.
The inverse, done properly and immediately: keys rotated, access removed, records kept. The step every enterprise knows is the dangerous one — automated, logged, boring.
The same lifecycle discipline for the whole estate: who owns which domain, which software instance, which account. Renewals, expirations, and handoffs as workflows, not as 3 a.m. surprises.
Identity-as-a-service the grove way: the same receipt culture that keeps the code honest keeps the access honest. Every grant, every revocation, every change — attributable, reviewable, and reversible.
This is the scale promise, stated plainly: the smallest of small gets the same machinery as the biggest of big — because it is the same machine, sized by its plugins and its keys, never by its price tag. The shop on the square and the enterprise across the country run the same grove; what changes is how much of the stack they switch on.
the grove's law: proven, not promised — so here is the line, drawn in public
| Capability | Status | The proof |
|---|---|---|
| The machine — voice-first, streaming, steerable, session-durable, plugin-first | shipped | v1.0.28 on PyPI, free, Apache-2.0; 7,869 automated tests |
| The instance tuned to your means — engine of your choice, one-command setup, transparent usage, alias routing | shipped | /onboard-synthetic and /check; the model family carries its own quota honesty |
| Two businesses' tools built on it | shipped | The drones pipeline and the barbershop shopfront — public pages, receipts attached |
| Analytics & BI dashboard | planned | Plugin architecture shipped; the dashboard is the first business plugin |
| The owned email platform — lifecycle, CAN-SPAM/GDPR mechanics, records of removal | planned | Compliance stated as design law now, so it is built in — not bolted on later |
| Domain & web operations as one auditable command | planned | The drones build walked this bridge by hand, with a runbook — the pattern exists |
| Full lifecycle & identity workflows — provisioning, deprovisioning, access by role and need | planned | The audit and guardrail hooks exist today; the lifecycle layer is the build this plan calls for |
The machine is free tonight. The suite is the next climb — built in public, at the council table, by the tradesmen and builders of the grove. Business owners: bring your friction, and the plan bends toward what you actually need. That is what the club is for.
shipped claims trace to the repository and its tests · planned claims are labeled planned — the grove does not sell futures as facts · provenance: PROVENANCE.md · claims ledger: FACTCHECK.md