Interfaces
The Shell, SDK, CLI, and AI skills present different workflows over the same system contracts.
An interface chooses what to reveal and how to guide the user. It does not invent a second data model or acquire authority merely because it presents an operation.
User interaction, transport adapters, developer ergonomics, and audience-appropriate representations of shared contracts.
Shell management surfaces, browser/Node System SDK, CLI commands, and Lamarck Skills for external AI.
No authoritative personal or control-plane state. Interfaces submit operations to the owning module.
Permissions, credentials, database connections, workload lifecycle, or durable entity identity.
Four surfaces
| Interface | Audience and boundary |
|---|---|
| Shell | Trusted user-facing management for Workspaces, Apps, Sources, credentials, and runtime state. |
@lamarck/system | Narrow App-facing data interface with separate browser and Node transports over the same methods. |
lamarck CLI | Human or coding-agent operator interface for queries, schema promotion/demotion, and development workflows. |
| Lamarck Skills | Instructions that teach ChatGPT, Claude, Gemini, Grok, or another AI how to use available Lamarck tools. |
One system, different depth
The Shell may say “Add an Oura Source.” A coding agent may edit a Connector package and invoke setup tooling. A contributor may inspect integration state. All three refer to the same Source identity and Connector lifecycle; the interface changes abstraction depth, not terminology.
System SDK boundary
system.query(sql, params?)
system.resolveContentRef(ref)
system.mutate(sql, params?)
system.transaction(statements)
system.writeDoc(id, content, metadata?)
system.deleteDoc(id)
system.writeEvent(event)The browser bridge and Node transport carry operation parameters to a Host-bound channel. They never expose a Core bearer, raw database, principal selector, credential surface, or arbitrary Host IPC.
Lamarck Skills
Lamarck Skills are distributed independently from the Workspace. Installing them teaches an AI the public model and supported operations; it does not widen the permissions of the Lamarck tools made available to that AI.