The Framework
One congruent framework with consistent behavior across the family — the owners at the top, every business beneath, and the clients who participate. Consistency of structure, never pooling of data.
Listen
The whole Logix story in one episode — the blueprint, the Vault, the numbers, the crew on the phones, and the worked queue. Two hosts. No pitch.
Knowledge & AI
What a business knows, written down once, owned by that business, and findable forever.
Every business gets a consistent, private, numbered knowledge structure — its Vault. Every record in a Vault carries its business, its owner, its source, its version, its approval, and its review date. Inherited templates stay distinguishable from what the business wrote itself, so a business always knows what it adopted and what is genuinely its own.
Inside each Vault sits its Brain — the trained knowledge the business's AI works from. Retrieval is permission-scoped lookup with citations, not invention: the agent answers from approved records, shows where an answer came from, and treats "doesn't know" as a valid answer. A Vault is never silently used to train anything shared, and it is never pooled with another business's knowledge.
The Vault belongs to the business. Its records, its versions, its history — held under that business's own number, exportable and auditable.
People and agents see the slice their role allows — nothing more. Access is verified per action, not assumed from a job title.
Agents speak from the Brain: approved knowledge, in the business's context, with the source attached. Unknown means unknown — never a guess dressed as an answer.
The Spine, Part One
A generated registry that gives every business, every person, and every project a permanent reference — and links websites, forms, proposals, documents, and audits into the Vault structure.
Because the registry is generated rather than hand-maintained, it cannot quietly drift from the records it describes. Four disciplines make it more than labelling:
A retired number becomes an alias, not a vacancy. History is never overwritten by a newcomer wearing an old identity.
Conversations, records, and oversight refer to the number — so the family, the businesses, and the people connect without mixing data.
When someone leaves or a business changes hands, the registry still says what everything is and where it belongs.
When something is corrected, the correction is written down and the superseded reference is preserved as an alias — never silently edited away.
Workspaces
The shared operating surface for one business. A tile hierarchy governs what exists: each business — and each person — sees their authorized tiles, and nothing beyond them.
The owner's view over their whole business: pipeline, knowledge, reporting, and the cost ledger, in one place.
Role-scoped personal views over the same records — not duplicate databases. A person can hold several roles; access is verified per action.
Aggregate-level visibility across the family: counts, status, health. Record-level detail only under an explicit, logged grant from the business's owner — revocable by that owner.
The Crew
One trained brain per business, working everywhere that business talks to the world — the website agent, the phone system, and the follow-up crew are the same knowledge, not three disconnected bots.
Logix's own agent runs this site: it answers questions, explains the system, and routes you to the right page or person — openly an AI, working from Logix's own Vault.
Every business gets its own agent, trained only on that business's Vault: its voice, its services, its rules. It books onto the right person's calendar — not a generic diary.
Agents draft, route, remind, and prepare. Anything that leaves the building under your name gets a human's approval first — and uncertainty is escalated, never smoothed over.
A pipeline is not a place where records live — it is a queue that someone works. In Logix, every record carries an owner, a specific dated next action, and a review date. The crew works that queue daily: deduplication, hygiene, follow-up cadence, and checks before outreach. Freshness is measured before outcomes, every week, against the same three questions. Read the full argument on the blog: The Worked Queue.
No. Each business keeps its own records in its own workspace and its own Vault. Family oversight is aggregate-level visibility, or record-level access only under an explicit, logged grant from the business's owner. Consistency of structure is not pooling of data.
A consistent, private, numbered knowledge structure for one business — and one for every person in it. Every record carries its business, owner, source, version, approval, and review date. AI retrieval over a Vault is permission-scoped lookup with citations, and "doesn't know" is a valid answer.
It is what keeps a duplicated system from drifting into lookalikes. Numbers are never reused, the number is the identity records and oversight refer to, and the registry outlasts any individual person or owner.
Start with a single workspace and a single workflow. The framework proves itself there first.