If you want ShipGlows to understand your project corpus, the first step is to give it something readable. The best starting point is a short project pitch tied to a source of truth.
The goal is not to write long marketing copy. The goal is to give ShipGlows a simple reference card it can use to answer four questions quickly:
- what is this project
- who is it for
- what angle describes it best
- where does the source of truth live
Why this helps
When each project has a stable pitch, ShipGlows can:
- recognize the right project faster
- avoid mixing up similar projects
- route a source into the right corpus
- keep useful memory instead of a pile of vague notes
Without a clear pitch, ShipGlows has to guess. With a clear pitch, it can reason.
What a good pitch includes
A good project pitch fits into a few elements:
- project name
- reference URL
- audience
- business angle
- internal framing note
- status
That format is intentionally short. It carries enough information without bloating the fiche.
What comes next
Once the project is introduced into ShipGlows, keep the pitch current. That is the job of the follow-up article: refreshing pitches when the project evolves.
In other words:
- first, bring the project into the system
- then, refresh it when it changes
That order keeps the base clean and avoids treating an old pitch as if it still described the current project.