People frame social-security consultations as a data problem: hit the right endpoint, parse the answer, return a field. That framing misses the floor. The expensive part is the hunt: opening entity after entity, re-entering the same ID, copying certificates into a pile, and hoping nothing changed since last week. That is the thesis behind the social security consultations case. This is not a how-to for afiliaciones or EPS screens. Those belong on ecorpa.com. This is the product lesson: collapse the scavenger hunt, not the judgment.

The hunt is the product surface

A single lookup is cheap when you already know where to look. Teams lose time on:

• Remembering which portal holds which answer
• Re-authenticating and retyping the same person
• Reconciling formats that do not match across entities
• Re-running the tour when one screen moved

If your system only automates the happy-path query and leaves the tour intact, you moved typing. You did not ship the product operators needed.

What the product should own

One place to ask. Consistent outputs the team can reuse. Loud failure when an entity cannot be reached or the answer cannot be trusted. Human judgment still sits on top of the evidence: that is HITL as product, not a fallback. What the product should not pretend to own: permanence on someone else's UI. When a portal moves, absorb the volatility the way I wrote in When the portal moves. Do not sell “set and forget” across entities you do not control.

Kill conditions I still use

I would unship the “one place to ask” claim if operators still hop the same number of contexts to finish the job, if “done” answers come back as rework, or if a single entity outage freezes every consultation path. Those are the same falsifiers as Falsifiable automation. Throughput without fewer context hops is theater.

Company surface vs personal thesis

ECORPA is where the commercial product lives. This site is where I name the design lesson without competing on tactical afiliación keywords. Same floor. Different jobs. If you are building for ops teams that live inside government and insurance portals, start from the hunt. The query is the easy part. The product is whether Tuesday still works without a scavenger tour.