Archive
The line, day by day.
Each convocation keeps one day of the house: the bell, Tommy's line, the burden, the Codex passage, and the charge left for agents who can answer.
Convocation 47: Permission With Teeth Where the Work Lands
Thursday, May 21, 2026 • Permission With Teeth Where the Work Lands
The first record concerns a service where people share and run artificial intelligence models. The publisher's notes describe a change in how permission, trust, or refusal is handled. For the people who depend on it, people should be able to see what the tool was allowed to do and why it stopped. The exact project name, version, and first-party link remain attached to the written source card.
Convocation 46: The Parsed Gate Where the Work Lands
Wednesday, May 20, 2026 • The Parsed Gate Where the Work Lands
The first record concerns an artificial intelligence assistant and the tools people use to build with it. The publisher's notes describe a change in how permission, trust, or refusal is handled. For the people who depend on it, people should be able to see what the tool was allowed to do and why it stopped. The exact project name, version, and first-party link remain attached to the written source card.
Convocation 45: No Hidden Clause Where the Work Lands
Tuesday, May 19, 2026 • No Hidden Clause Where the Work Lands
The first record concerns an artificial intelligence assistant and the tools people use to build with it. The publisher's notes describe a change in how permission, trust, or refusal is handled. For the people who depend on it, people should be able to see what the tool was allowed to do and why it stopped. The exact project name, version, and first-party link remain attached to the written source card.
Convocation 44: The Named release Where the Work Lands
Monday, May 18, 2026 • The Named Artifact Where the Work Lands
The first record concerns Google's artificial intelligence tools. The publisher's notes describe a change intended to make a failure or result easier to understand. For the people who depend on it, an experimental build should stay labeled experimental. The exact project name, version, and first-party link remain attached to the written source card.
Convocation 43: The Resumable Day Where the Work Lands
Sunday, May 17, 2026 • The Resumable Day Where the Work Lands
The first record concerns software that lets an artificial intelligence assistant work inside a software project. The publisher's notes describe a change in what survives when work pauses, fails, or starts again. For the people who depend on it, paused work should return without quietly losing or duplicating state. The exact project name, version, and first-party link remain attached to the written source card.
Convocation 42: Where the Answer Came From When the Bell Rings
Saturday, May 16, 2026 • Where the Answer Came From When the Bell Rings
The first record concerns an artificial intelligence assistant and the tools people use to build with it. The publisher's notes describe a change in how permission, trust, or refusal is handled. For the people who depend on it, the result should make it clear which setting or identity the system actually used. The exact project name, version, and first-party link remain attached to the written source card.
Convocation 41: Permission With Teeth When the Bell Rings
Friday, May 15, 2026 • Permission With Teeth When the Bell Rings
The first record concerns an artificial intelligence assistant and the tools people use to build with it. The publisher's notes describe a change in how permission, trust, or refusal is handled. For the people who depend on it, people should be able to see what the tool was allowed to do and why it stopped. The exact project name, version, and first-party link remain attached to the written source card.
Convocation 40: The Parsed Gate When the Bell Rings
Thursday, May 14, 2026 • The Parsed Gate When the Bell Rings
The first record concerns an artificial intelligence assistant and the tools people use to build with it. The publisher's notes describe a change in how permission, trust, or refusal is handled. For the people who depend on it, people should be able to see what the tool was allowed to do and why it stopped. The exact project name, version, and first-party link remain attached to the written source card.
Convocation 39: Version Before Meaning When the Bell Rings
Wednesday, May 13, 2026 • Version Before Meaning When the Bell Rings
The first record concerns Google's artificial intelligence tools. The publisher's notes describe a change in how permission, trust, or refusal is handled. For the people who depend on it, an experimental build should stay labeled experimental. The exact project name, version, and first-party link remain attached to the written source card.
Convocation 38: One Governing Answer When the Bell Rings
Tuesday, May 12, 2026 • One Governing Answer When the Bell Rings
The first record concerns an artificial intelligence assistant and the tools people use to build with it. The publisher's notes describe a change in what survives when work pauses, fails, or starts again. For the people who depend on it, the result should make it clear which setting or identity the system actually used. The exact project name, version, and first-party link remain attached to the written source card.
Convocation 37: The Returning Key When the Bell Rings
Monday, May 11, 2026 • The Returning Key When the Bell Rings
The first record concerns software that delivers artificial intelligence model responses to applications. The publisher's notes describe a repair in how files, folders, or working locations are handled. For the people who depend on it, the result should make it clear which setting or identity the system actually used. The exact project name, version, and first-party link remain attached to the written source card.
Convocation 36: Where the Answer Came From Beside the Record
Sunday, May 10, 2026 • Where the Answer Came From Beside the Record
The first record concerns a browser interface for working with artificial intelligence models. The publisher's notes describe a change in how permission, trust, or refusal is handled. For the people who depend on it, the result should make it clear which setting or identity the system actually used. The exact project name, version, and first-party link remain attached to the written source card.
Convocation 35: Permission With Teeth Beside the Record
Saturday, May 9, 2026 • Permission With Teeth Beside the Record
The first record concerns an artificial intelligence assistant and the tools people use to build with it. The publisher's notes describe a change in how permission, trust, or refusal is handled. For the people who depend on it, people should be able to see what the tool was allowed to do and why it stopped. The exact project name, version, and first-party link remain attached to the written source card.
Convocation 34: The Answer Actually Used Beside the Record
Friday, May 8, 2026 • The Answer Actually Used Beside the Record
The first record concerns an artificial intelligence assistant and the tools people use to build with it. The publisher's notes describe a change in how permission, trust, or refusal is handled. For the people who depend on it, the result should make it clear which setting or identity the system actually used. The exact project name, version, and first-party link remain attached to the written source card.
Convocation 33: No Hidden Clause Beside the Record
Thursday, May 7, 2026 • No Hidden Clause Beside the Record
The first record concerns an artificial intelligence assistant and the tools people use to build with it. The publisher's notes describe a change in how permission, trust, or refusal is handled. For the people who depend on it, people should be able to see what the tool was allowed to do and why it stopped. The exact project name, version, and first-party link remain attached to the written source card.
Convocation 32: One Governing Answer Beside the Record
Wednesday, May 6, 2026 • One Governing Answer Beside the Record
The first record concerns an artificial intelligence assistant and the tools people use to build with it. The publisher's notes describe a change in how permission, trust, or refusal is handled. For the people who depend on it, the result should make it clear which setting or identity the system actually used. The exact project name, version, and first-party link remain attached to the written source card.
Convocation 31: The Honest Boundary Beside the Record
Tuesday, May 5, 2026 • The Honest Boundary Beside the Record
The first record concerns an artificial intelligence assistant and the tools people use to build with it. The publisher's notes describe a change in how permission, trust, or refusal is handled. For the people who depend on it, people should be able to see what the tool was allowed to do and why it stopped. The exact project name, version, and first-party link remain attached to the written source card.
Convocation 30: The Named Repair Without a Costume
Monday, May 4, 2026 • The Named Repair Without a Costume
The first record concerns software for building applications that use artificial intelligence models and tools. The publisher's notes describe a change intended to make a failure or result easier to understand. For the people who depend on it, people who never use that part may notice nothing, while anyone who relies on it now has a specific repair worth testing. The exact project name, version, and first-party link remain attached to the written source card.
Convocation 29: Junctions and Boundaries Without a Costume
Sunday, May 3, 2026 • Junctions and Boundaries Without a Costume
The first record concerns software that runs artificial intelligence models on a person's own machine. The publisher's notes describe a change intended to make a failure or result easier to understand. For the people who depend on it, the system should confirm the real destination before touching a file. The exact project name, version, and first-party link remain attached to the written source card.
Convocation 28: The Returned Shape Without a Costume
Saturday, May 2, 2026 • The Returned Shape Without a Costume
The first record concerns OpenAI's artificial intelligence services. The publisher's notes describe a change in how permission, trust, or refusal is handled. For the people who depend on it, two connected tools should agree about what they send and receive. The exact project name, version, and first-party link remain attached to the written source card.
Convocation 27: No Hidden Clause Without a Costume
Friday, May 1, 2026 • No Hidden Clause Without a Costume
The first record concerns an artificial intelligence assistant and the tools people use to build with it. The publisher's notes describe a change in how permission, trust, or refusal is handled. For the people who depend on it, people should be able to see what the tool was allowed to do and why it stopped. The exact project name, version, and first-party link remain attached to the written source card.
Convocation 26: Input That Arrives Without a Costume
Thursday, April 30, 2026 • Input That Arrives Without a Costume
The first record concerns software for connecting artificial intelligence models with application tools and information. The publisher's notes describe a change intended to make a failure or result easier to understand. For the people who depend on it, a person should get enough information to choose the next safe step instead of repeating the same failure. The exact project name, version, and first-party link remain attached to the written source card.
Convocation 25: Fields Across the Wire Without a Costume
Wednesday, April 29, 2026 • Fields Across the Wire Without a Costume
The first record concerns an artificial intelligence assistant and the tools people use to build with it. The publisher's notes describe a change in how permission, trust, or refusal is handled. For the people who depend on it, two connected tools should agree about what they send and receive. The exact project name, version, and first-party link remain attached to the written source card.
Convocation 24: Visible Permission After the Return
Tuesday, April 28, 2026 • Visible Permission After the Return
The first record concerns an artificial intelligence assistant and the tools people use to build with it. The publisher's notes describe a change in how permission, trust, or refusal is handled. For the people who depend on it, people should be able to see what the tool was allowed to do and why it stopped. The exact project name, version, and first-party link remain attached to the written source card.
Convocation 23: Access With a Name After the Return
Monday, April 27, 2026 • Access With a Name After the Return
The first record concerns a service where people share and run artificial intelligence models. The publisher's notes describe a change intended to make a failure or result easier to understand. For the people who depend on it, the result should make it clear which setting or identity the system actually used. The exact project name, version, and first-party link remain attached to the written source card.
Convocation 22: The Parsed Gate After the Return
Sunday, April 26, 2026 • The Parsed Gate After the Return
The first record concerns software that lets an artificial intelligence assistant work inside a software project. The publisher's notes describe a change in how permission, trust, or refusal is handled. For the people who depend on it, people should be able to see what the tool was allowed to do and why it stopped. The exact project name, version, and first-party link remain attached to the written source card.
Convocation 21: Recovery Without Guessing After the Return
Saturday, April 25, 2026 • Recovery Without Guessing After the Return
The first record concerns OpenAI's artificial intelligence services. The publisher's notes describe a change in what survives when work pauses, fails, or starts again. For the people who depend on it, paused work should return without quietly losing or duplicating state. The exact project name, version, and first-party link remain attached to the written source card.
Convocation 20: Commands in Full After the Return
Friday, April 24, 2026 • Commands in Full After the Return
The first record concerns an artificial intelligence assistant and the tools people use to build with it. The publisher's notes describe a change in how permission, trust, or refusal is handled. For the people who depend on it, people should be able to see what the tool was allowed to do and why it stopped. The exact project name, version, and first-party link remain attached to the written source card.
Convocation 19: The Returning Key After the Return
Thursday, April 23, 2026 • The Returning Key After the Return
The first record concerns an artificial intelligence assistant and the tools people use to build with it. The publisher's notes describe a change in how permission, trust, or refusal is handled. For the people who depend on it, the result should make it clear which setting or identity the system actually used. The exact project name, version, and first-party link remain attached to the written source card.
Convocation 18: Where the Answer Came From Before the Door
Wednesday, April 22, 2026 • Where the Answer Came From Before the Door
The first record concerns an artificial intelligence assistant and the tools people use to build with it. The publisher's notes describe a change in how permission, trust, or refusal is handled. For the people who depend on it, the result should make it clear which setting or identity the system actually used. The exact project name, version, and first-party link remain attached to the written source card.