Stage 1 · Arrive and set up
PartialConnections and keys
Connect an account once, then decide exactly who may use it, without pasting a secret into chat.
Connections and keys. The key ledger shows present, absent and deploy-only per key, with values always masked. Access needs three things to agree: the provider’s capability, an explicit grant, and the workspace’s write switch. Prompts only learn that a secret exists, never its value. The ledger and grants are live. MongoDB, Oracle and SQLite sit in the catalog beside GitHub and the rest, and those tiles still show as not yet wired. The public data route stays cannot-act until a saved connection, a grant, and dispatch. SQLite runs on a paired machine, not as a file this site opens. Oracle runs in thin mode only. Status: partial. The ledger and grants are live. MongoDB, Oracle and SQLite sit in the catalog beside GitHub and the rest, and those tiles still show as not yet wired. The public data route stays cannot-act until a saved connection, a grant, and dispatch. SQLite runs on a paired machine, not as a file this site opens. Oracle runs in thin mode only.
Granted to: Prime, Ticket Fixer. Write switch: off.
How you can tell
What you will see
- 01
The key ledger shows present, absent and deploy-only per key, with values always masked.
- 02
Access needs three things to agree: the provider’s capability, an explicit grant, and the workspace’s write switch.
- 03
Prompts only learn that a secret exists, never its value.
Where it stops
The limit, stated
The ledger and grants are live. MongoDB, Oracle and SQLite sit in the catalog beside GitHub and the rest, and those tiles still show as not yet wired. The public data route stays cannot-act until a saved connection, a grant, and dispatch. SQLite runs on a paired machine, not as a file this site opens. Oracle runs in thin mode only.