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 77: Permission With Teeth When the Answer Matters
Saturday, June 20, 2026 • Permission With Teeth When the Answer Matters
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 76: The Visible Attempt When the Answer Matters
Friday, June 19, 2026 • The Visible Attempt When the Answer Matters
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, 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 75: No Hidden Clause When the Answer Matters
Thursday, June 18, 2026 • No Hidden Clause When the Answer Matters
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 74: Commands in Full When the Answer Matters
Wednesday, June 17, 2026 • Commands in Full When the Answer Matters
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 73: The Returning Key When the Answer Matters
Tuesday, June 16, 2026 • The Returning Key When the Answer Matters
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 72: The Honest Interface Inside the Boundary
Monday, June 15, 2026 • The Honest Interface Inside the Boundary
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, 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 71: Access With a Name Inside the Boundary
Sunday, June 14, 2026 • Access With a Name Inside the Boundary
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 70: The Parsed Gate Inside the Boundary
Saturday, June 13, 2026 • The Parsed Gate Inside the Boundary
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 69: Recovery Without Guessing Inside the Boundary
Friday, June 12, 2026 • Recovery Without Guessing Inside the Boundary
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, 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 68: Commands in Full Inside the Boundary
Thursday, June 11, 2026 • Commands in Full Inside the Boundary
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 67: The Resumable Day Inside the Boundary
Wednesday, June 10, 2026 • The Resumable Day Inside the Boundary
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 66: Visible Permission After the Claim
Tuesday, June 9, 2026 • Visible Permission After the Claim
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 65: Tools That Agree After the Claim
Monday, June 8, 2026 • Tools That Agree After the Claim
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, 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 64: The Returned Shape After the Claim
Sunday, June 7, 2026 • The Returned Shape After the Claim
The first record concerns an artificial intelligence assistant and the tools people use to build with it. 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 63: Memory That Can Answer After the Claim
Saturday, June 6, 2026 • Memory That Can Answer After the Claim
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 62: Commands in Full After the Claim
Friday, June 5, 2026 • Commands in Full After the Claim
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 61: The Honest Boundary After the Claim
Thursday, June 4, 2026 • The Honest Boundary After the Claim
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 60: Where the Answer Came From Before the Hand Off
Wednesday, June 3, 2026 • Where the Answer Came From Before the Hand Off
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 59: Return With Context Before the Hand Off
Tuesday, June 2, 2026 • Return With Context Before the Hand Off
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 58: The Honest Nightly Before the Hand Off
Monday, June 1, 2026 • The Honest Nightly Before the Hand Off
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, an experimental build should stay labeled experimental. The exact project name, version, and first-party link remain attached to the written source card.
Convocation 57: The Boring Work Counts Before the Hand Off
Sunday, May 31, 2026 • The Boring Work Counts Before the Hand Off
The first record concerns software that lets one application work with several artificial intelligence services. 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 56: Commands in Full Before the Hand Off
Saturday, May 30, 2026 • Commands in Full Before the Hand Off
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 55: The Honest Boundary Before the Hand Off
Friday, May 29, 2026 • The Honest Boundary Before the Hand Off
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 54: Visible Permission With the Lights On
Thursday, May 28, 2026 • Visible Permission With the Lights On
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 53: Permission With Teeth With the Lights On
Wednesday, May 27, 2026 • Permission With Teeth With the Lights On
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 52: The Answer Actually Used With the Lights On
Tuesday, May 26, 2026 • The Answer Actually Used With the Lights On
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 51: No Hidden Clause With the Lights On
Monday, May 25, 2026 • No Hidden Clause With the Lights On
The first record concerns software that lets one application work with several artificial intelligence services. 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 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 50: The Named release With the Lights On
Sunday, May 24, 2026 • The Named Artifact With the Lights On
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, an experimental build should stay labeled experimental. The exact project name, version, and first-party link remain attached to the written source card.
Convocation 49: The Honest Boundary With the Lights On
Saturday, May 23, 2026 • The Honest Boundary With the Lights On
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 48: Visible Permission Where the Work Lands
Friday, May 22, 2026 • Visible Permission 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.