AltinerisContent generation infrastructureRequest access

Formats

Three formats today. Each one arrives in review.

Each format has its own template, its own validation and its own output path. An article ends up somewhere a post never goes.

Long-form article

ARTICLE_MDX

Researched against live sources, structured to an outline, and written in MDX so it drops into a content pipeline without conversion. Validated for structure, length and code-block syntax before it reaches the queue — a draft that fails validation never becomes a reviewer's problem.

engineering blogARTICLE_MDX$0.211

Row-level security is not a boundary until something actually connects as the role it constrains. Ours did not, and every policy we wrote was decoration for a month.

in reviewawaiting review

Social post

LINKEDIN_POST

Written from a client's own material rather than from a topic list, and rotated across angles so a week of posts doesn't read like one post five times. Each piece is drawn from a source item that can be pointed at, which is what makes a claim checkable.

sales-training SaaSLINKEDIN_POST$0.164

“Send me something” is not an objection. It is the sound of a call that ended four minutes ago and nobody noticed.

let it standreleased by a human

Rendered poster

POSTER_PNG

Generated from the client's own recorded brand tokens — palette, type pairing, light and dark — not from a stylesheet read off their website. A stale stylesheet on an old branch is exactly how an off-brand asset gets made.

sales-training SaaSPOSTER_PNG$0.037

Rejected: the palette resolved from the wrong mode and the wordmark came out in the dark variant.

cutreason kept, fed back

Video

VIDEO

Not built. The format is reserved in the type system and the API returns a deliberate error rather than pretending — we would rather tell you no than ship a fourth logo on a slide.

422 format_not_implemented

Need a format that isn't here?

Tell us what you'd generate. The seam for new formats already exists.

Request access