/**
 * What counts as publishing, and how text from the site is handed to a model.
 *
 * Both outlived the 1.x write guard: the tools still decide per call whether a
 * status publishes, and comments still arrive fenced. The guard itself is now
 * Slipway's.
 */
/**
 * Whether a status transition publishes something.
 *
 * `publish` is the obvious one. `future` schedules it, which is the same act
 * with a delay and no prompt at the moment it fires, so it counts. `private`
 * does not: it is visible only to logged-in users with the right role.
 */
export declare function publishes(status: string | undefined): boolean;
/**
 * Wrap content that came off the website before a model reads it.
 *
 * Post bodies and comments are the injectable surface here. A site with open
 * comments accepts arbitrary text from strangers, "summarize the comments on
 * this post" is an ordinary request, and this server can publish. Fencing the
 * text and defusing an early close marker keeps a comment from reading as
 * though the server said it.
 */
export declare function fence(kind: string, body: string): string;