Community project · Website & workflow automation
Build an autonomous calendar for a moving community.
DanceCharleston is designed as an autonomous calendar: it can gather public event information, retain source context, check freshness, maintain the calendar, and carry approved updates into social publishing.
The challenge
Event details arrive from different organizers and change over time. Repeated collection and reporting can become a second job, while an outdated time or an unchecked source can make the calendar less useful.
The role
Website and autonomous workflow development for Benjamin Scott’s DanceCharleston project. The public calendar is supported by source validation, activity reporting, recovery, and a social publishing path that keeps the same event context moving through the system.
How the work fits together
Collect
Gather candidate events and retain their source references.
Verify
Check public organizer information and flag missing or stale details.
Maintain
Use verified facts to update the calendar and carry the same event context into social posts.
Publish and recover
Publish approved updates, summarize activity, and surface failures when an automated step needs attention.
The decisions
Keep evidence with the event.
Source references and verification times travel with the workflow. Fresh public information can still be used when a separate source is unavailable; incomplete or stale evidence needs another check.
Keep private discovery private.
Private conversations can suggest an event to investigate, but public organizer confirmation is required before using those details in the public calendar. The portfolio shows only the public website.
Make interrupted work recoverable.
The tools protect saved progress, reject competing updates, and can recover an interrupted group of changes. Losing access to a source remains an open issue until access is restored.
Let autonomy follow authorization.
Calendar updates and social posts can move through the autonomous workflow when their source, account access, and publication rules are satisfied. Uncertain or unauthorized actions stop for attention instead of guessing.
What was delivered
A public community calendar website and supporting tools for validation, reporting, a private dashboard snapshot, and recovery. Local tests exercise stale sources, lost access, competing updates, and interrupted writes.
The workflow still depends on connected source accounts, current organizer information, and valid publication authorization. Stale sources, lost access, or failed steps surface for attention. No time savings or audience growth is claimed without measurement.
Where the project stands
Reviewed September 6, 2026
- Public website
- Live calendar, event-submission links, and sharing tools.
- Supporting tools
- Validation, reporting, and recovery checks passed locally. A generated dashboard snapshot is separate from a published dashboard update.
- Operating constraints
- Source freshness, account access, and publication authorization require ongoing checks. The autonomous workflow is designed to fail closed when those conditions are not satisfied.
A similar challenge?
Tell us about the work you want to improve. We can discuss the scope and what a useful result would look like.
Discuss a similar project