# Strategy Funnel: Open Questions for Claude

Use this worksheet before running the Daily Strategy Funnel scheduled task. Answer as much as you can, save it in your own Strategy Funnel directory, and point Claude at it alongside the main scheduled-task prompt.

The goal is to remove ambiguity before the task runs unattended. If a question does not apply, write `N/A`. If you do not know yet, write `TBD` and keep Phase 2 disabled until the missing pieces exist.

## 1. Project location and access

1. What is the exact project directory Claude should use?
   - Answer:

2. Can Claude read and write files in that directory during the scheduled task?
   - Answer:

3. Which files are authoritative references that Claude must read first?
   - Answer:

4. Which files or folders must Claude never edit?
   - Answer:

## 2. Daily target

1. How many fresh candidates should Claude try to queue each run?
   - Answer:

2. What is the maximum number of ideas Claude may evaluate before stopping?
   - Answer:

3. What should Claude do if it cannot find enough high-quality candidates?
   - Answer:

## 3. Sources

1. Which forums, newsletters, repositories, journals, blogs, or websites should Claude scan?
   - Answer:

2. Which social accounts or watchlists are trusted enough to include?
   - Answer:

3. Which sources are out of scope because they produce too much noise?
   - Answer:

4. Should Claude only use the last 24 hours, or is a longer lookback acceptable?
   - Answer:

5. Are there source types Claude should summarize but never quote directly?
   - Answer:

## 4. Asset universe

1. Which instruments, markets, symbols, timeframes, or formats are in scope?
   - Answer:

2. Which ideas are portable enough to queue with a warning?
   - Answer:

3. Which ideas should be hard-rejected because your infrastructure cannot support them?
   - Answer:

4. Are there symbol or naming mappings Claude must apply between source material and your execution venue?
   - Answer:

## 5. Output scaffold

1. What file type should Claude produce for each candidate?
   - Answer:

2. What exact sections, fields, modules, or blocks must every candidate contain?
   - Answer:

3. Which optional flags or modules should default off?
   - Answer:

4. What naming convention should Claude use for folders, files, classes, functions, or strategy IDs?
   - Answer:

## 6. Audit rules

1. What defects have previous automated runs produced?
   - Answer:

2. What rules should prevent those defects from happening again?
   - Answer:

3. What counts as a hard reject during drafting?
   - Answer:

4. What counts as a soft warning that can still enter the queue?
   - Answer:

## 7. Deduplication

1. What existing files, indexes, folders, or rejected records should Claude check before queuing a candidate?
   - Answer:

2. What fields should form the deduplication hash?
   - Answer:

3. How many hash characters should Claude use?
   - Answer:

4. How should Claude tag related but non-identical ideas?
   - Answer:

## 8. Validation

1. What required-presence markers must appear in every valid output?
   - Answer:

2. What dynamic checks should Claude run beyond simple marker presence?
   - Answer:

3. How many redraft attempts are allowed before rejection?
   - Answer:

4. Where should rejected drafts and rejection reasons be written?
   - Answer:

## 9. Phase 2 backtesting and optimisation

1. Should Phase 2 be enabled now, or skipped until infrastructure is ready?
   - Answer:

2. What is the exact working directory for Phase 2?
   - Answer:

3. What runtime or interpreter should Claude use?
   - Answer:

4. What command runs the backtester?
   - Answer:

5. What command runs the optimiser?
   - Answer:

6. What result files prove that backtest and optimisation completed?
   - Answer:

7. What should Claude log if Phase 2 fails or is unavailable?
   - Answer:

## 10. Review dashboard and logs

1. What columns should `index.csv` contain?
   - Answer:

2. What sections should `queue.md` contain?
   - Answer:

3. What format should each `runs.log` entry use?
   - Answer:

4. Where should Claude write the daily final summary?
   - Answer:

## 11. Final safety checks

1. What must Claude never do automatically?
   - Answer:

2. What requires manual review before promotion?
   - Answer:

3. What disclaimer or warning should be copied into candidate notes?
   - Answer:

4. What should Claude do if instructions conflict?
   - Answer: