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 107: Access With a Name With Nothing Hidden
Monday, July 20, 2026 • Access With a Name With Nothing Hidden
The first record concerns software that lets one application work with several 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, 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 106: The Answer Actually Used With Nothing Hidden
Sunday, July 19, 2026 • The Answer Actually Used With Nothing Hidden
The first record concerns an artificial intelligence assistant that helps people write and repair software. 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 105: No Hidden Clause With Nothing Hidden
Saturday, July 18, 2026 • No Hidden Clause With Nothing Hidden
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 104: Commands in Full With Nothing Hidden
Friday, July 17, 2026 • Commands in Full With Nothing Hidden
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 103: The Honest Boundary With Nothing Hidden
Thursday, July 16, 2026 • The Honest Boundary With Nothing Hidden
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 102: Visible Permission When the Work Comes Back
Wednesday, July 15, 2026 • Visible Permission When the Work Comes Back
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 101: Permission With Teeth When the Work Comes Back
Tuesday, July 14, 2026 • Permission With Teeth When the Work Comes Back
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 100: The Honest Nightly When the Work Comes Back
Monday, July 13, 2026 • The Honest Nightly When the Work Comes Back
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 99: Memory That Can Answer When the Work Comes Back
Sunday, July 12, 2026 • Memory That Can Answer When the Work Comes Back
The first record concerns software that delivers artificial intelligence model responses to applications. 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 98: Commands in Full When the Work Comes Back
Saturday, July 11, 2026 • Commands in Full When the Work Comes Back
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 97: The Honest Boundary When the Work Comes Back
Friday, July 10, 2026 • The Honest Boundary When the Work Comes Back
The first record concerns an artificial intelligence assistant that helps people write and repair software. 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 96: State After Return Before Anyone Depends
Thursday, July 9, 2026 • State After Return Before Anyone Depends
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, 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 95: Permission With Teeth Before Anyone Depends
Wednesday, July 8, 2026 • Permission With Teeth Before Anyone Depends
The first record concerns an artificial intelligence assistant that helps people write and repair software. 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 94: The Parsed Gate Before Anyone Depends
Tuesday, July 7, 2026 • The Parsed Gate Before Anyone Depends
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 93: A Contract at the Edge Before Anyone Depends
Monday, July 6, 2026 • A Contract at the Edge Before Anyone Depends
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, 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 92: One Governing Answer Before Anyone Depends
Sunday, July 5, 2026 • One Governing Answer Before Anyone Depends
The first record concerns software that lets one application work with several 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, 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 91: The Honest Boundary Before Anyone Depends
Saturday, July 4, 2026 • The Honest Boundary Before Anyone Depends
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 90: Visible Permission At the Point of Trust
Friday, July 3, 2026 • Visible Permission At the Point of Trust
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 89: Permission With Teeth At the Point of Trust
Thursday, July 2, 2026 • Permission With Teeth At the Point of Trust
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 88: A Smaller Hot Path At the Point of Trust
Wednesday, July 1, 2026 • A Smaller Hot Path At the Point of Trust
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, a speed claim only matters when the same work still produces the same result. The exact project name, version, and first-party link remain attached to the written source card.
Convocation 87: No Hidden Clause At the Point of Trust
Tuesday, June 30, 2026 • No Hidden Clause At the Point of Trust
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 86: The Named release At the Point of Trust
Monday, June 29, 2026 • The Named Artifact At the Point of Trust
The first record concerns an artificial intelligence assistant that helps people write and repair software. The publisher's notes describe a change in what survives when work pauses, fails, or starts again. 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 85: The Honest Boundary At the Point of Trust
Sunday, June 28, 2026 • The Honest Boundary At the Point of Trust
The first record concerns software that lets one application work with several 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, 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 84: State After Return Without the Victory Speech
Saturday, June 27, 2026 • State After Return Without the Victory Speech
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, 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 83: Access With a Name Without the Victory Speech
Friday, June 26, 2026 • Access With a Name Without the Victory Speech
The first record concerns an artificial intelligence assistant that helps people write and repair software. 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 82: The Parsed Gate Without the Victory Speech
Thursday, June 25, 2026 • The Parsed Gate Without the Victory Speech
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, 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 81: No Hidden Clause Without the Victory Speech
Wednesday, June 24, 2026 • No Hidden Clause Without the Victory Speech
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 80: Commands in Full Without the Victory Speech
Tuesday, June 23, 2026 • Commands in Full Without the Victory Speech
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 79: A Preview Is a Preview Without the Victory Speech
Monday, June 22, 2026 • A Preview Is a Preview Without the Victory Speech
The first record concerns an artificial intelligence assistant that helps people write and repair software. 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 78: The Named Repair When the Answer Matters
Sunday, June 21, 2026 • The Named Repair When the Answer Matters
The first record concerns software that lets one application work with several artificial intelligence services. The publisher's notes describe a way to check that downloaded software came from its publisher and was not silently replaced. 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.