Locations and sources
Proxy-only camp source handling for supported providers
SummerCan source investigation and live validation stay proxy-only for configured providers that must not be probed directly.
The problem
direct provider probes can violate the repository data-source boundary and produce misleading diagnostics. For operators and technical evaluators reviewing SummerCan source behavior, that means the hard part is not just finding camps; it is preserving the decisions that make the final family schedule trustworthy.
How SummerCan helps
SummerCan documents proxy-only runbooks and uses configured provider inventories for live source checks. SummerCan is a planning tool: it helps organize discovery, comparison, review, and schedule output while leaving final provider confirmation with the family.
How it works
- Start with setup: children, date window, location/source choices, and unavailable blocks.
- Use discovery to open a chooser-ready set of camp groups and dated sessions.
- Choose and review camp interests before the schedule builder runs.
- Use the final schedule, share link, provider links, and calendar output as the handoff for real-world follow-through.
Feature-to-benefit table
| Feature | Why it matters here | Example |
|---|---|---|
| proxy provider inventory | Keeps the page focused on proxy only camp source planning instead of generic camp browsing. | Use the configured live integration harness for source checks. |
| live integration harness | Connects the family constraint to an observable planner surface. | Keep Redondo WebTrac and Galileo/Pedalheads investigations proxy-backed. |
| no direct probe rule | Turns reviewed decisions into a practical output families can inspect. | Treat provider failures as operator diagnostics when stored discovery can still serve families. |
Use-case examples
Initial setup
Use the configured live integration harness for source checks.
Decision review
Keep Redondo WebTrac and Galileo/Pedalheads investigations proxy-backed.
Schedule handoff
Treat provider failures as operator diagnostics when stored discovery can still serve families.
Objections and limitations
Is this a replacement for provider registration?
No. SummerCan helps with planning and schedule organization. The actual provider remains the source for enrollment, availability, pricing, and policy confirmation.
What about stale demo data?
The public app displays a frozen Summer 2026 catalog notice. Treat demo data as planning context and verify details before relying on them.
How private is a shared schedule?
Shared schedule links are bearer links. Send them only to people who should see the read-only schedule.
FAQ
How does SummerCan help with proxy only camp source planning?
SummerCan documents proxy-only runbooks and uses configured provider inventories for live source checks. The relevant product fit is proxy provider inventory, live integration harness, no direct probe rule.
Does SummerCan book camps or guarantee availability?
No. SummerCan helps families organize discovery, comparison, preferences, and schedule output. Families should verify availability, pricing, policies, and enrollment directly with each provider.
What should a family prepare before using this workflow?
Have the children, ages, date window, unavailable blocks, and the locations and sources decision context ready before moving into camp choice and review.
Can the finished plan be shared?
Yes, finished schedules can be shared through a read-only schedule link, and calendar output is available from the result page when the plan is ready.
What makes this locations and sources page specific?
It focuses on direct provider probes can violate the repository data-source boundary and produce misleading diagnostics, using proxy provider inventory and live integration harness rather than repeating a generic camp-planning checklist.
Plan with the family constraints in view
SummerCan source investigation and live validation stay proxy-only for configured providers that must not be probed directly.
Open SummerCan