We want to collect feedback from users through this form:

We can easily collect it to Google Sheet, however I wonder If we can collect it in Seed Private document. For example, we are building a community at nodos.hyper.media what if we add a page, web only that contains the form and creates a private document every time a user wants to send feedback?

I took a close look at the feedback form in:

/Users/gabrielherrero-beaumont/jean/seed/Form-with-seed-docs/user_test_form_delibera_v12.html

and also checked the relevant parts of the Seed codebase to understand whether we can use this form to create a private document directly in Seed.

The short answer is: yes, this is possible — but the form does not do that yet.

At the moment, the form is only collecting the responses, turning them into a plaintext summary, hiding the interface, and then calling:

sendPrompt(...)

So what it currently does is send a message or prompt into the surrounding runtime. It is not publishing a document into Seed, and it is definitely not yet creating a private one.

What matters here is that this is not a limitation of Seed itself. After checking the local codebase, it’s clear that Seed already supports private documents. That support exists in the backend, in the client/SDK layer, and in the desktop app’s publishing flow. In other words, the platform already knows how to create and publish private documents. The missing piece is simply that this HTML form is not wired into that flow.

I also checked whether the easiest route might be to use the CLI. The answer there is: probably not. The current document createCLI command appears to support document creation generally, but it does not appear to expose a clear --private or --visibility option for this use case. So while the CLI is useful for creating documents, it doesn’t seem like the best or cleanest path for turning this form into a private-document submission mechanism.

The better path is to use the existing SDK / desktop publish flow. That path already understands visibility, including private visibility, and it is already used elsewhere in the app. So if we want this form to create a private feedback document, the right architecture is:

keep the current form UI,

replace the final sendPrompt(...) behavior,

submit the feedback as structured data to a Seed-side action or runtime bridge,

and from there call the existing publish flow with visibility: PRIVATE.

There is one important backend constraint to be aware of: private documents must use a simple top-level path. That means something like:

/feedback-123

is valid, but something nested like:

/forms/feedback/123

would fail. Also, private documents cannot be created as root documents. So if we implement this, we should plan to generate a flat path for each submission.

The practical implication is that the HTML file alone cannot create the document by itself unless it has access to the Seed runtime — specifically an account context, signing capability, and the publish client/API. So the real implementation task is not “can Seed store this?”, but rather “how do we connect this form to the existing Seed publishing machinery?”

My recommendation is that we do not rely on prompt-based behavior for this. Instead of sending a natural-language summary and hoping some assistant or background process turns it into a document, we should add a direct action such as createPrivateDocument(payload) and make the form submit into that. That would give us a much more reliable and explicit pipeline: form answers in, private Seed document out.

So the conclusion is straightforward: this is feasible with the current Seed stack. Seed already supports private docs. The current form just isn’t integrated with that capability yet. The work ahead is mainly integration work — wiring this form into the existing private publish flow so that each submission becomes a real private feedback document in Seed.