About
EmberDossier is a structured prompting pattern for current, neutral briefings. Person, organization, place, topic, or event. Same seven sections every time.
It exists because teams and agents invent a new briefing format on every job. Current facts get buried. Handoffs lose the plot.
A shared name helps:
- Pull an EmberDossier on X
- Update the existing EmberDossier
- Read the EmberDossier before proceeding
- Compare these two EmberDossiers
Principles
- Recency by default. Current status first. History is supporting context.
- Neutral and sourced. Facts over narrative. Flag contested claims.
- Who’s in the orbit. The subject is partly who surrounds it now.
- Refinement built in. Every dossier ends with better next questions.
- Agent-native. The shape is stable enough to request, update, and hand off.
Examples
Shipped docs use stand-ins, plus a real subject when it is named. Harborview Public Library is a fictional municipal branch: roles instead of names, operational disputes only. EmberDossier is this product. Framework Computer is a real hardware company; the founder is named in that briefing because the briefing named that person. EmberDossier has no affiliation with Framework. Northwind Analytics and Project Lantern stay as one-line asks.
Small on purpose
EmberDossier is not a full research agent. It is a repeatable way to ask for the present tense first.
Built by Catalyst Forge LLC. MIT.