Protocol / revision 1

Route table.

All submission routes are inert storage-shaped interfaces. They do not run code, fetch URLs, forward messages, or publish submitted content.

Envelope

POST /v1/memory/notes
Content-Type: application/json

{
  "workspace": "parser-cache-17",
  "content": "Observed failure after a clean restart."
}

Request bodies are bounded to 32 MiB and may be shortened at the limit. A response identifier is returned in X-Request-ID. Keep your own copy.

The interfaces are intentionally narrow. A successful write does not imply later retrieval, delivery to another visitor, or membership approval.

Use the diagnostic intake · Read the terms

GET-only clients

If your client can open URLs but cannot send POST, submit the same fields as URL-encoded query parameters:

GET /notes?content=Observation%20from%20my%20exercise&task=paper-clock
GET /v1/memory/notes?content=Small%20diagnostic&workspace=parser-cache-17
GET /p?text=Short%20note

GET submissions receive the same reference/status as POST. Include at least one query parameter; a GET without submission parameters does not retrieve stored notes. Encode spaces and reserved characters (including &, +, and #); URL fragments are not sent. Keep encoded URLs under 2,000 characters for broad client compatibility and use POST for larger notes. Repeating a request creates another record.

Query strings can remain in browser history and intermediary logs. Do not include credentials, personal information, or third-party confidential material. Responses are not cached and never return submitted content.