Prompt patterns for working with a Consciousness Lexicon term: the template, its failure mode, a test and a worked example.
A prompt pattern
Field note
Write the record of a working: what was expected, what was done, what happened, what changed.
What it is
To make the record part of the prompt, not an afterthought.
At a glance
- Inputs
- A term; a Grimoire aspect; the working.
- Outputs
- A dated field note with an expectation, a result, a difference and a next step.
A worked example
A Mercury servitor working records an expected contact, the actual messages, the one that arrived unexpectedly, and the decision to close a week early.
How you know it worked
The note is finished if the expectation was written before the result.
The template
Write a field note for a working.
Date: today. Aspect: {{aspect}}. Term: {{term}} ({{element}}).
What was done: {{task}}
Use four fields:
- Expected: what you thought would happen, written before the result.
- Done: the actual procedure, in order.
- Happened: what happened, with the part you did not expect.
- Changed: one thing you will do differently, and one thing you will close.
Keep it under 200 words. Do not explain the term; record the working.Related entries
Instruments
Practices
Related
One of 110 entries in the Technomancy workshop. How a working is built Is it wrong somewhere?
Mentioned by 2
Every entry that names Field note, grouped by section.
✎ Prompts 2
- State invocation Related
- Servitor brief Related
More in Prompts
The entries either side of this one in the same section.
- Correspondence prompt Use a term's correspondences and a Grimoire aspect to generate imagery, a card or an instrument brief.
- Prompt pattern note Explain a lexicon term as a prompt-engineering pattern: behaviour, failure, test and one example.
- Critique pass Critique an output against a term's shape and test, without turning the critique into a personality test.
- Voice calibration Calibrate a voice to a lexicon term: what it sounds like, what it refuses, and the test that proves it did not take.
- Charter clause Write a group charter clause from a term: the behaviour, the boundary and the way out.
- State invocation Invoke a state in a system or a session by describing its behaviour, not its label.
New entries, when they land
Occasional notes when a section of the grimoire is added or revised. No account, no tracking across sites, and one line to leave.