Development record
lens
coredraftlens
A lens is one direction the librarian searches in around a source. The nine are the same for every subject; what changes is how each reads. For a game, principles and key features means design principles, mechanics and visuals; for a development process, it means key features and the assumptions behind them. The librarian writes down how it read each lens, so the person can correct it.
When to use
When naming what a reading pack covers, or correcting how the librarian read the subject.
When NOT to use
For a check that depends on the kind of document (a review's scoring scale, an advertisement's exaggeration): that is a form check.
Examples
- For "writing a video game", the evidence-and-reception lens finds period reviews and named critics' verdicts.
Related terms
Frontmatter
| term | lens |
|---|---|
| bounded_context | core |
| status | draft |
| definition | One of nine broad questions the librarian asks around every source (principles and key features, context and timeline, alternatives, evidence and reception, use and best practice, people and sources, rights and media, open questions and glossary, fit to my project), each read for the subject at hand. |
.abcd/development/brief/glossary/core/lens.md
open on GitHub ↗ · commit history ↗