A Normal Wednesday in 2027

Eight in the morning. Coffee half-finished, earbuds in. The assistant’s voice comes through.

“Three things today. Product sync at ten, code review at two, design chat about the new feature at four. Also, Jake asked if you’re free for lunch Friday. I haven’t replied yet.”

“Friday works. Set it up, and find somewhere good nearby.”

“Done. He suggested that ramen spot down the street, noon to one. Confirmed.”

No opening a calendar app. No back-and-forth messages to find a time. The assistant handled it all.

Before the ten o’clock meeting, the assistant speaks up again.

“Today’s product sync is about prioritizing feature X. Last time you talked to the PM, he leaned toward A, you wanted B. Want me to pull together some arguments?”

You pause. That conversation was two weeks ago. You’d almost forgotten. But the assistant remembers. It remembers what was said, and where each of you stood.

“Sure, list them out.”

“Three points. First, user demand for B is double that of A, based on last week’s research data. Second, once B is done, it can be reused in project Y, saving three weeks. Third, A depends on a third-party API that isn’t integrated yet.”

Five minutes to review. You’re ready.

Afternoon. You’re deep in code. The assistant speaks softly.

“Jake just messaged. He wants to move the four o’clock to three-thirty. He has to pick up his kid at four. Works for you?”

“Sure.”

“Done. Also, he asked if his intern can sit in. The intern’s into this project.”

“No problem.”

You never left your editor. The assistant handled the rescheduling, the participant update, the reply. You said two words.

Before you head out, the assistant gives a quick summary.

“Two things done today. Code review passed. Product sync concluded: we’re going with B, starting next week. One thing got pushed to tomorrow, the other party had a conflict.”

“Tomorrow?”

“You’ve got three hours free in the morning. What do you want to do with it?”

“Write that requirements doc.”

“Blocked it off. Nine to twelve, no meetings.”

This is an ordinary day for a developer in 2027.

The AI assistant understands what you’re working on, knows who you need to coordinate with, handles the social side, and manages your time. You say one sentence, and it’s done.

For this to work, the assistant needs a calendar format it can actually read and operate on.

calendar.md is a calendar spec designed for AI agents. The agent reads, writes, and collaborates. Every operation leaves a record. Humans can read it too, because the calendar is just Markdown.

Next time you’re chatting with an AI, try saying “help me schedule next week.” It might actually be able to now.