Context Building

The edge proxy does not expose a standalone /v1/context/build route. Instead, clients build prompt context from the PKMS routes that do exist: note fetch, note list, notebook registry reads, and search.

---

Client Assembly Flow

When a client needs prompt context, it should:

---

Contract Notes

• search is pass-through at the proxy layer.
• GET /v1/workspaces/:workspaceId/notes may return decrypted note headers when a client key is available.
• GET /v1/workspaces/:workspaceId/notes/:noteId returns the full note payload and may be decrypted by the proxy before it reaches the browser.
• indexableBlocks is the plaintext boundary intended for search and indexing.

Prompt Formatting

Keep the final prompt block local to the client. The proxy's job is to transport the PKMS payloads and preserve encrypted note content, not to generate a prompt template on the server.