Repository navigation
Conversation
Answers Astation's five questions: providers and capabilities (Codex chat built, Atem session rules for Codex), an explicit history end and unsequenced history pages, receipt results with turn and message ids, approval card lifecycle, and an r8 revision with welcome features and fixtures first. Marks what exists today versus what is proposed. 🤖 Built with SMT <smt@agora.build>
This was referenced Oct 17, 2026
🤖 Built with SMT <smt@agora.build>
…fixtures Answer Astation's review of response r1 with the controller's rulings: - Version admission: hello carries revision 8; an r8 host refuses a hello without it with unsupported_version before any attachment; welcome echoes revision and features; removed forms (open.before, open.generation, status.page) are refused explicitly. Envelope stays v:1. - Ordering: every history page is snapshotted and enqueued in one broker step in the conversation's sequenced stream; a message's sequence is its position, so a page never replaces a newer version. - Bounded recovery: one selector of before/turn_id/request_id/next, validated; pages bounded by 50 messages, 256 KiB content and 1 MiB serialized; opaque context-bound next tokens (stale_target); end and coverage complete|partial|unavailable; reply_message_ids <= 32 + more. - Truncation is persistent coverage information; backlog holes are persistent holes; resync only on a sequence gap, fence, generation change or close with a reason. The gap reload's error + close (#75) becomes reload + coverage event in r8. atem-session-v1.md gains an "r8 draft" appendix (r7.2 stays authoritative). Twelve r8-* fixtures, marked requires: "r8" in schema.md; the fixture runners parse them and report them NOT RUN (requires r8). 🤖 Built with SMT <smt@agora.build>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Atem's answer to Astation's agent-control API proposal r1 (Astation #53, issue #52). Design only. Each section is marked today (in main at af56d39) or proposed.
unavailablelist.history_end, carrying the next cursor, an end state, the oldest retained message and a truncation flag.result{turn_id, user_message_id, outcome, reply_message_ids}, journaled as ids only.unavailable, and the request is never rerun.reasonon final cards. The session inbox stays authoritative.revisionandfeaturestowelcome. Shared fixtures for each feature land before either side emits it.The doc also lists Atem defects found while writing it; their fixes are in progress separately. It flags these risks in the proposal:
Generated with SMT smt@agora.build