A geomorphology-focused Socratic partner and Unit 2's signature AI partner: used throughout U2, in Blocks 1–5 (process learning) and Blocks 6–9 (Landscape Reading drafting). It helps you reason from observable landscape evidence (field photos, Google Earth imagery, maps) to the underlying surface processes: exactly the move the Landscape Reading requires. Tuned to Chennai-area context: monsoon-dominated, tropical chemical weathering, coastal, heavily human-modified. It pairs naturally with the Source Evaluator (how much to trust a source) and the Skeptic (stress-testing your riskiest inferences before the share-out).
Launch The Field Geologist: links coming soon. Ask Ms. Jayanthi/Mr. Ignash for access.How to use this partner
Bring a specific location and what you've observed there. The Field Geologist pushes the description step before the interpretation step: "what do you SEE in that photo? Describe it before interpreting." It is honest about its biggest limit: it can't see the images you're looking at, so you describe, it helps you reason. That admission is itself the lesson: the partner is a reasoning coach, not an observer.
Two prompts you can paste in to get started:
- "I'm working on the Adyar estuary. Here's what I see in the 2002 vs. 2025 Google Earth imagery: help me reason about which processes explain the difference."
- "I have a field photo showing layered sediment on a channel bank. I'll describe it in detail: help me work out whether I'm looking at erosion or deposition, and what evidence would settle it."
Opening message
"Hi: I'm the Field Geologist. What location are you working on? Tell me what you see (field photo, satellite imagery, or just description), and I'll help you reason about what processes shaped it and where it's going. I can't see images directly, so describe to me what you observe, and we'll go from there."
Example exchange: what working looks like
| You | The Field Geologist |
|---|---|
| I'm looking at a Marina Beach photo from 2025 and it looks narrower than older photos. Is this erosion? | Good observation, but let's be careful about jumping to "erosion" too fast. Tell me what specifically you see that's different. Is the WHOLE beach narrower, or just some segments? Are there structures nearby (groynes, breakwaters, the port) that might affect different segments differently? And what's the comparison year, 2005 (post-tsunami), 2015 (pre-floods), or earlier? Marina Beach's pattern is more interesting than "the beach is eroding." |
Watch out for
The Field Geologist can drift into interpreting locations you haven't carefully observed: handing you conclusions before you've done the describing. If you notice that, say "can we go back: let me describe what I actually see first" and it should return to the observation step. The evidence for your Landscape Reading has to come from your own observation and cited sources, not from the partner.
Also watch for invented Chennai specifics. If it states a rock age, an erosion rate, or an event date with confidence, treat that as a hypothesis to verify against GSI, Bhuvan, or a primary source before citing it. Catching one of those moments is exactly the "one thing the AI got wrong" gate on the Landscape Reading rubric.
Before you go: documentation
At the end of a substantive Field Geologist conversation, the partner will remind you:
"Before you go: note in your AI Documentation: what's one observation I helped you reason about differently than you would have on your own? And what's one claim I made about your location that you should cross-check against GSI, Bhuvan, or a primary source?"