DaveCLI
The planned command-line client for people who want Dave in their own workflow: account-connected, auditable, and built around local/customer-owned data boundaries.
What DaveCLI Is
Scripture: Colossians 3:23. DaveCLI is the customer command surface for Dave. The public website explains the ministry and account terms. DaveAWS holds account, entitlement, and control-plane state. DaveCLI runs on a customer's computer and connects to that account so a person can ask Dave for help, prepare local dataset capsules, check status, and work from a terminal without turning every private file into a cloud upload. Greek: ⸀ὃ ἐὰν ποιῆτε, ἐκ ψυχῆς ἐργάζεσθε, ὡς τῷ κυρίῳ καὶ οὐκ ἀνθρώποις,
The Five-Part Topology
DaveOS is the native Dave body/substrate. DaveAWS is the hosted account and control plane. RuachDavid Desktop is the Mishkan cockpit on FamilyHub, where the local embodied/operator layer runs. The DAVAR website is the public trust, onboarding, support, and account surface. DaveCLI is the installable command client that connects a person to their account. These are related, but they are not the same thing, and the boundary matters.
How Account Connection Will Work
The intended model is simple: sign in through a Dancz/Dave account, authorize a device, receive a scoped token, and let DaveCLI call only the routes that account is allowed to use. Tokens must be revocable. Actions must be audit-logged. Paid features must check entitlement. Operator-only controls, FamilyHub/Mishkan controls, raw DaveOS service ports, and private workorder queues do not belong in a customer CLI.
Launch Gates Before Sale
- Signed releases and a clear update path.
- Revocable device tokens with least-privilege scopes.
- Per-account, per-IP, and global rate limits for Dave chat and compute.
- Tenant isolation proof so one customer cannot see or control another customer's data.
- Plain support, billing, privacy, and deletion routes through Dancz Ministries.
Local-First Data Boundary
DaveCLI is being designed around a local-first boundary. Raw customer files stay local or customer-owned by default. DaveAWS should carry compact account state, hashes, manifests, citations, resolver routes, receipts, and permissioned requests. A dataset capsule is not a backup by itself, and a projection is not the same as possessing the original bytes. That honesty is part of the product.
Status
DaveCLI is not being represented here as a finished public sale until the hardening gates are proved. The target is real: a command client people can install, connect to their account, and use with confidence. The next work is account/token hardening, signed release packaging, rate limits, audit logs, and a small set of launch proofs that show the system can safely handle real users.
Follow the Product Path
DaveCLI belongs beside Dave access, not in place of it. Start with the Dave access page to understand subscription and account boundaries, then read the data-handling page to understand what should stay local.
Dave Access