The Tireless Apprentice

Half of this chapter is this tool's home ground. A multi-step research errand - what the schemes say, what the trains cost, what a page claimed and when it claimed it - is exactly what an answer engine with citations attached is built for, and the plan, act, check loop of the chapter happens here with the sources visible as it goes. Set your limits inside the question itself: name the kind of source you will accept, ask for the date on every page, ask it to show you where sources disagree and what it could not find. Academic focus for university material, Web for the official portals, and a Space to hold the standing context so next week's round starts warm. The other half of the chapter - the acting half - simply is not here, and the honest adaptation is to carry the findings to another tool and act yourself.

• Name the source type in the question - official portal, not blog.
• Ask for the date on every page, then open the key ones.
• Academic focus for university work; Web for government portals.
• Keep the project in a Space so next week starts warm.
• Research here; act in another tool, and act yourself.

Compare, with a citation on every row, the government subsidy schemes for drip irrigation open to a small farmer in Maharashtra.

I am a B.Sc. Agriculture student in Pune and this is for a seminar paper, so the sourcing matters to me more than the prose. If your app offers a longer multi-step research mode, use it.

Answer in four parts:
1. The schemes - the central micro-irrigation programme and whatever Maharashtra runs alongside or on top of it. One table: scheme, administering department, current status.
2. Eligibility - how each scheme defines a small or marginal farmer, in its own words, with the clause cited.
3. The subsidy share - the percentage actually paid, by farmer category, and whether it arrives before or after installation. If two official sources state different percentages, show both and name both pages.
4. The application route - which portal, which documents, which office.

For every claim, give me the publication or last-updated date of the page. Mark anything older than two years. Where a source is a coaching site, a news report or an undated PDF, say so plainly rather than listing it beside a government portal as though the two weighed the same.

Finally: list what you could not establish from an official source at all.

The looking-up half of this trip belongs here. The booking half does not, and nothing here can book in any case - which is just as well, because that step is mine.

Two travellers in their late sixties, Ludhiana to Haridwar and Rishikesh, four days in early February, about ₹40,000 in total, and we cannot walk far.

Research each of these separately, and cite everything:
1. Trains from Ludhiana to Haridwar - a table of the realistic options with departure, arrival, classes available and current fare. Cite the railway's own pages rather than aggregator listings, and give me the date you read them.
2. Mid-range hotels within a short walk of Har Ki Pauri - for each, the distance to the ghat and whether a lift exists. Mark whether the lift is claimed by the property or reported by a guest who stayed there.
3. Current temple, darshan and Ganga aarti timings in both towns, from official or temple-trust pages where such pages exist. Where sources contradict one another, show me the contradiction instead of resolving it.
4. Whatever changes with the season in early February - weather, river conditions, crowds - from recent coverage rather than an undated page.

Label as unverified anything you could not source. I am taking this to another tool to lay out the four days, and to the railway counter to book.

This errand cannot be run here, and it is worth being exact about why. This tool reads the web, not your mailbox. It cannot list your unpaid invoices, cannot draft inside your mail and cannot send anything at all - so the whole of this example belongs either in a tool with a permitted connection to your mail, or in your own hands with a spreadsheet. What it can do is the part shopkeepers usually get wrong: the rules for chasing money without losing the customer.

I run a small tiles and sanitaryware shop in Lucknow and I want to chase overdue customer payments by email without damaging relationships the shop depends on.

1. What do Indian law and ordinary commercial practice say about payment-reminder letters to a business customer - what may be stated, what begins to count as harassment, and at what point a formal demand notice becomes the right instrument instead of a reminder? Cite the provisions and recent commentary.
2. For an unpaid invoice under GST, what reference details should a reminder carry - invoice number, date, GSTIN, amount - and is there any reporting or credit-note consequence to an invoice that is never settled? Cite official sources, and say clearly where the answer turns on facts about my business that you do not have.
3. What do trade bodies and recent business coverage recommend on timing - how many days before the first reminder, the second, the firmer one?
4. Is the delayed-payment route for small enterprises open to a shop like mine, and what does it actually require? Link the official page and give me the date shown on it.

Mark anything uncertain. I am after the questions to put to my chartered accountant, not a ruling from you - where the answer is legal rather than practical, say so and tell me to ask a professional. Then I will take these rules to another tool, build the list of my own unpaid invoices myself, and send every reminder from my own hand.