pipelex-lab

Experiment with an MTHDS method the way a lab would — frame a use case into candidate methods, write the answer key of each test case before its first run, agree a budget, then run, score every run against its key and log it, fixing the method round after round until it meets the pass bar or a stop. Use when the user says "what could I build with Pipelex", "help me try Pipelex on our invoices", "help me pick where to start", "test this method", "set up test cases", "write an answer key", "check it against the answer key", "score this run", "is it getting better", "iterate until it passes", or wants to know whether a method is good enough. Also use it first when the user wants a piece of work automated, such as "automate this", "every morning, summarise", "when an email arrives", "connect Pipelex to Gmail, Drive or Notion". It keeps the brief, the keys and the log under lab/. A run spends inference credit, so the loop starts only on the user's go on a budget.