Enterprise
Chips is built for one person and their harnesses first. The things an enterprise needs are not a different product; they are the same data model with more of it turned on.
What is already true
Section titled “What is already true”- Tenancy from the first table. Every table carries
workspace_id, every repository method takes a workspace scope, and a lint rule fails any query that lacks the predicate. - An audit that cannot be edited. The log is append-only and exportable, and the audit view is a read of it rather than a second record that could disagree. See Audit event.
- A workspace cap on autonomy. A space can forbid what a harness’s own policy allows, and the cap always wins. See Policy.
- Credentials that stay put. Chips brokers decisions and never holds the credentials an harness acts with.
- Data residency by construction. The harness runs where you run it, and the server runs where you put it. Nothing has to leave your cloud.
What comes later
Section titled “What comes later”| Phase | |
|---|---|
| Invites, passkeys, several people in a workspace | 5 |
| Postgres, S3, several gateway processes, a Prometheus exporter | 6 |
| SAML, SCIM, retention policies, an admin surface | 8 |
The ee/ directory in the repository is reserved and empty until then. Anything that would go in
it before Phase 8 is a signal the boundary is in the wrong place.