Skip to main content

Gnosis creation — from note

A sequence diagram of the journey a user takes from tapping "make gnosis from this note" on the notes surface to landing in the Builder with a proposed draft. The endpoint is POST /api/notes/{note_id}/generate-gnosis (see the API reference for the operation); the response shape matches POST /api/gnosis/propose so the client can hand the result directly to the Builder. The diagram visualises what the generate_gnosis_from_note use case in gnostikon already documents in code — this is a complement, not a new source of truth.

Last reviewed against backend commit 742b5a7 (gnostikon, branch 017-docs-backfill).

How a single note in the user's scope becomes a proposed Gnosis draft, including the failure variants the client must surface and the telemetry checkpoints the backend emits.

The Builder takes over from the navigation — the intent="propose" chain it runs is owned by the Builder surface and is intentionally not depicted here, mirroring the dx-016 pilot decision to stop each diagram at the screen hand-off boundary.

Client surface​

  • Notes / [noteId] — the per-screen stub for the source surface (/notes/[noteId]) where the user taps the action.

API endpoints​

  • POST /api/notes/{note_id}/generate-gnosis (operation generate_gnosis_from_note) — the single call that powers this journey. See the API reference for request and response shapes (GenerateGnosisFromNoteRequestModel, GenerateGnosisDraftSuccessResponseModel, NoteErrorResponseModel, BuilderErrorResponseModel).