Unsupported Block: Unknown

Interface Notions

I have the urge to write down our common understanding on the interface. I am very excited to build functionality, but I am also very concerned about creating a mess. I would be more comfortable if I learned the fundamentals and concepts of the interface. This way, I make sure the Agent Sticks to our conventions instead of generating random code that nobody will be able to maintain in the future. Let's see if I can extract those foundations from your brains. 🤗 In a React codebase, we don’t extend components in the OOP sense. The standard pattern is composition: reuse an existing component with props, wrap it in another component, or split responsibilities into parent and child components. A component becomes its own unit when it represents a clear UI element with its own responsibility or logic. 1. Shared UI primitives 2. Shared UI components 3. Web app components/routes 4. Desktop app components 5. Desktop pages 6. Editor extensions

Typescript SDK

The Seed TypeScript SDK can create documents without asking the daemon to sign them. Flow: For cross-account publishing, the publish payload should include: Capability blob + Change blob + Ref blob This is important because the destination write permission is proven by the capability embedded in the signed Ref. The daemon only stores/indexes the blobs; it does not need to pre-authorize the write with CreateDocumentChange. This is the same model used by the CLI for document creation.

Seed CLI

Connect to a Seed Server from the Command line

Daemon

Surveys

I am building a Survey feature. The most important components are the Form and Sit Cross publishing. What am I doing:

Vault