Blueprints

A blueprint gives a piece of work its shape: the sections it moves through, what each one needs to do, how much each carries, and what the whole thing is for. Gyrium ships with a standard set covering a sales pitch, a project proposal, an investment pitch, a presentation of one product or service and more. You can build your own, so the way your organization structures a particular kind of work stops living in one person's head and becomes something the system holds.

Every organization has kinds of communication the standard set does not cover, and the knowledge of how they are built usually sits with whoever writes best. A blueprint captures that once, so everyone composes that kind of work to the same shape. It turns "the way we usually structure this" into something applied automatically. It carries the shape and never the words, which is what keeps one customer's material out of another customer's work.

Start from a guided set of questions, from an example, or from a deck or document you have already made here. The example path reads pasted text, a URL, or an uploaded text or markdown file, and infers a draft: name, audience, occasion, purpose, formats, and the narrative arc. The path that starts from your own finished work takes the arc, the weight of each section and the shape of each part while deliberately leaving every sentence behind. Gyrium composes the arc, then assembles the underlying rule blocks in code so the structural invariants hold, and voice-scans the result. Your blueprint then behaves exactly like a standard one, with no change to the generation pipeline. Sixty-eight standard blueprints ship with the product. Each organization starts with the ones that fit its kind of work, about two dozen, and the rest wait under Not activated, where an administrator can switch any of them on. Blueprints your own team made are never hidden. "Duplicate to customize" copies the brief, and Gyrium drafts the copy's sections again from it.

One of them is built for a supplier speaking to one customer's engineers. The application presentation starts from the applications the customer runs, and for each shows which of your offerings fits, why it holds up in those conditions, and the proof, ending on one next step. About seven slides, kept light on text.

One of them presents a single thing you sell. The product or service presentation is anchored to one offering: it introduces it to a buying audience, the conditions it works in, how it is built or delivered to answer them, the proof, and where it fits, grounded on that offering's facts.

1. Open Blueprints.
2. Answer the questions, paste an example, upload it as text or markdown, or point it at a deck or document you have already made.
3. Adjust the name, audience, occasion, purpose, and formats.
4. Save. Your blueprint appears wherever your team picks what to make.
5. Share it across the organization if you want others to use it.

Starting from your own finished work covers decks and documents. Web pages, emails and social posts are reused through the example path for now. Popularity and rework analytics are reserved for later, and not surfaced yet. Sharing a blueprint shares it across your own organization; a blueprint never reaches another organization. Standard blueprints are read-only.