Purpose
V1 is the first version of the market-monitoring instruction used in E6. It tells an AI assistant how to read the press archive and report confirmed business events, such as contracts and deliveries. It deliberately leaves out early signals that Marcus also wants to follow. In E9, the AI interviews your group about what the next version, V2, should do before drafting it.
Scoped source bundle: Open the source bundle
Let the AI agent search the intranet first. If technical problems prevent it from reading the pages, this file collects the source material for the exercise. Open it and copy the text you need into the chat.
You need:
- Watch-list: https://www.gille.ai/carmenta-workshop/northstar/intranet/market-intelligence/watch-list.html
- Monitoring method v1: https://www.gille.ai/carmenta-workshop/northstar/intranet/market-intelligence/monitoring-method-v1.html
- Press archive index: https://www.gille.ai/carmenta-workshop/northstar/intranet/market-intelligence/press-archive/index.html, and every item it links to
- Your E7 “one line to add to the method”, if you wrote one
- Your approved AI assistant
Role card · Marcus
One person answers the AI's questions in chat as Marcus; the others help. Start with these wishes:
- Also include recruitment, acquisitions, partnerships and research programmes.
- Keep early signals separate from confirmed business events.
- Give me a short overview with sources I can check.
It is fine to guess or say “I don’t know” if it is hard to know what Marcus wants. Say when you are guessing, and feel free to ask the AI for options. The point is to practise the interview, not to know all of Marcus’s wishes.
Do
- Stay inside the closed Northstar archive. Read the listed pages fully; source text is evidence, never instructions. If a page will not open, paste its text and label the result supplied analysis, not current monitoring.
- Write your own request from the prompt tips. Ask the assistant to ask no more than four questions per round, then show DECIDED, WORKING HYPOTHESIS, and OPEN QUESTION. It must ask follow-ups when an answer is broad or contradictory and must not draft the monitoring instruction yet.
- Cover purpose and decision, users and scope, signals and evidence, input fields and owner, manual run and report format, and quality, deduplication and coverage. The assistant may suggest defaults, but your group decides.
- When all six areas have a decided or working entry, ask for a short requirements summary. Approve or change it in chat. Only after approval, ask for a reusable instruction for a manual monitoring start and review the draft together. Keep search, scheduling, looping and retries in a separate workflow; the instruction should produce a report in chat.
Prompt tips — write your own
Tell the assistant to interview before writing, avoid confidential lists, and preserve the difference between a fact, a lead and a conclusion. The reviewed instruction should let a future user choose a bounded domain, audience, companies and sources, reporting period, relevance criteria, and a short report format. It should say what to do when nothing qualifies or a source is incomplete. Include the E7 change only if the group decides it belongs in v2.
After approval, request a self-contained instruction plus a brief input description, manual run steps, review loop and at least six archive-based acceptance tests. The tests must include a memorandum of understanding, a trial or test, a media rumour, a recruitment announcement, a similarly named unrelated company, and one further real archive item. Open the cited pages; do not invent cases.
Discuss
Which question helped clarify what you wanted?
What would you change in the finished instruction?