Skip to content

Latest commit

 

History

History
12 lines (12 loc) · 3.35 KB

0-crew-automation-creation-team.md

File metadata and controls

12 lines (12 loc) · 3.35 KB
kind added
title an automation records the crew it was made in, and codeaf app reads a crew's orders by it
pr 0
surface
engine
invalidates
Was true: no automation recorded where it was made beyond its conversation, and a crew could not list what was made in it. Is true now: an automation records Origin.Team from the creation context the door that accepted its turn's opening message stated — the crew's exact id for crews.message, a new member's first brief (members.start) and the goal crews.start hands its manager; explicit none for the person's own send and first words in codeaf app. A door that states nothing (plain Submit, the terminal surface, an older app or client, words the app writes itself, a row saved before the field) leaves it UNKNOWN; absence is never read as none.
Was true: a message carried nothing about the crew it was sent for. Is true now: session.Submission.Creation (*CreationContext, nil = unknown, {} = none, {team} = exact) and remote SubmitArgs.creation carry it; the engine proves at acceptance that the team exists in its own teams file and holds the receiving conversation, and records a team it cannot prove (forged, unrelated, another profile's, or a conversation with no teams) as UNKNOWN; the message itself is never refused for its context. A closed crew is proven like an open one. Only the context the engine proved is journaled (the door's raw claim never is), on the person's line, so a turn asked again after a takeover keeps its crew: the journaled stamp is reused as written and NOT proven again against today's teams file, so a member removed, a manager changed or a crew closed after acceptance never turns that turn unknown; the id is never re-checked or moved.
Was true: Automation.Crew, the crew an order belongs to, was the only crew field. Is true now: it is unchanged and unvalidated at creation; Origin.Team is a separate fact, never written by change or update (Store.Update keeps the stored one whatever the caller passes), and never inferred from membership, the current manager or the workspace.
Was true: a host that keeps no message marks refused nothing about crews. Is true now: still true — a crew message to such a host is sent as its words, and the team is unknown there.
Was true: orders.list was the only orders read. Is true now: an engine naming orders.made_in serves {crew, limit?, cursor?} as a page of the orders whose recorded creation team is that crew, read in one statement (one snapshot) over at most 500 stored rows and 2 MiB of stored bytes sized before any is read, answering at most 256 KiB of encoded orders, with unknown, the count of untagged or non-JSON orders in the same stretch; a surface sums unknown over the walk. only the fields an order shows are read out of a matching document (never a watch's memo), and ids over 30 bytes are never read out; a document of any crew over 2 MiB stops every crew's walk at it with too_large until it shrinks. next is an opaque cursor (≤ 128 bytes) bound to the crew (another crew's is bad_params) and to a walk revision that creates, deletes and creation-team rewrites move (also from an older build, through triggers in the store file; user_version is unchanged) and runs, status and ordinary edits do not; a moved revision is stale_cursor and a row too large to carry is too_large with the cursor unmoved. orders.list keeps its shape and filter.