chat

type Coords struct {
	Memory      string
	MessagesLoc string
}

type Message struct {
	Seq       *int   `json:"seq"`
	Loc       string `json:"loc"`
	Author    string `json:"author"`
	Identity  string `json:"identity,omitempty"`
	Role      string `json:"role,omitempty"`
	Timestamp string `json:"timestamp,omitempty"`
	Body      string `json:"body"`
	// SessionID attributes an agent-posted message to the coding session
	// driving the persona (#369 D16) — the driver is Session.userId. Absent
	// on human/channel posts; additive, the push channel ignores it.
	SessionID string `json:"sessionId,omitempty"`
	// Mentions as stored by the poster; readers needing them should fall
	// back to Mentions(Body) when empty (hand-created messages omit them).
	Mentions []string `json:"mentions,omitempty"`
	// The platform envelope's identity fields (#630). createChannelMessage
	// writes these and this reader dropped all three, so `--json` could not
	// tell a WORKER post from a human one — the distinction the Worker model
	// exists to record. Absent on the retired academy rows, hence omitempty.
	AuthorWorkerID string `json:"authorWorkerId,omitempty"`
	AuthorUserID   string `json:"authorUserId,omitempty"`
	AuthorAppID    string `json:"authorAppId,omitempty"`
}

type PostInput struct {
	Coords Coords
	Body   string
	// ReplyTo is the seq, or the loc/URN, of the message this answers.
	ReplyTo string
	// Session binds the post to a worker session, which is what makes it the
	// WORKER speaking rather than the human. It is what replaced the identity
	// envelope: the server derives authorship from it.
	Session string
}

type PostResult struct {
	// NodeID is the message node. The client no longer knows the loc — the
	// server mints it — so this is the address a caller gets back.
	NodeID string
	Seq    *int
	// Author is the name the SERVER recorded. Echoed back rather than assumed,
	// because posting under the wrong identity is the one mistake this surface
	// can make silently.
	Author *string
}