Working glossary
Publication is an event at the source; receipt is an event at the reader or system. Their clocks and access may differ.
Educational explanations, fictional scenarios and personal worksheets. No live calls, paid-account test or provider performance certification.
Publication and receipt
Publication is an event at the source; receipt is an event at the reader or system. Their clocks and access may differ.
Amendment
A later version linked to the original instruction. It does not erase what subscribers originally received.
Acknowledgement and fill
Acknowledgement records an order being accepted or rejected; a fill records executed quantity and price.
A vocabulary with evidence subjects attached
Original publication means the first declared instruction for one stable signal identity. An amendment is a later version, not a rewrite that erases the first. Source event time and device receiving time belong to different clocks. A parent references a previous object under the declared journal contract; it is not a cryptographic signature. Acknowledgement says an operational request was recognised, not that the desired quantity executed. Fill and close are execution declarations in this tutorial until actual broker evidence exists. Entry expiry bounds eligibility to start an instruction; it need not terminate an already filled position. Withdrawal can change publication intent without itself generating a closing order.
Filled interpretation finding
The fictional Alpha amendment has source time 09:00:20 and receipt 09:00:45. Its later acknowledgement is received at 09:00:41, which is a delivery inversion relative to the source-ordered journal. The term does not assert fraud or automatically decide which policy was active. Beta's expiry is unfilled in the supplied exercise; Gamma's withdrawal leaves its close unresolved. A financial denominator would require fixed statuses for completed positions, flats, open exposure, cancellations and unfilled instructions. Fourteen rows therefore cannot be relabelled as fourteen independent trades. These terms name what is present and what remains missing rather than awarding authority to familiar language.
What the record still cannot answer
Byte identity is a match to exact source bytes. Authenticity is a different claim about origin or authority. A completed timestamp bound requires its own proof; a declared signal_time field is not independent chronology. Calibration needs a defined event population and independent evaluation, not merely a grade label. An execution policy includes actual order, quantity, fill and recovery semantics. A research hypothetical fill is distinct from broker execution. The original glossary remains alongside these tighter definitions, and no term silently expands its meaning to include data, model rights, favourable outcomes or production certification not supplied in the record.
Declared state and authoritative state are not synonyms
A journal row can declare that something filled, expired or closed. Authority depends on the actual source, permissions, policy and independently inspected evidence. The teaching parser therefore names declared_fill_events rather than authenticated executions and keeps financial fields null. A research LIVE label, source code, merged branch or endpoint inventory also does not prove a production subscriber route. Operational deployment and certification have separate records. A real case should retain those distinctions in both prose and data fields. Replacing a precise declared label with the familiar word verified would add a claim that formatting alone cannot establish, even when the rest of the document is complete.