> For the complete documentation index, see [llms.txt](https://docs.origintrail.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.origintrail.io/agent-context/publish-lifecycle-language.md). # Publish Lifecycle Language This context describes the project language for Knowledge Asset publication and operational diagnostics across DKG nodes. ## Language **Knowledge Asset Publish Lifecycle**: The end-to-end path that moves a Knowledge Asset from local working memory through shared working memory, peer validation and acknowledgement, verifiable memory, and chain confirmation. *Avoid*: Publish request, transaction, one-off publish step **Published KA Sync Lifecycle**: The catch-up path that lets another node discover, fetch, validate, and materialize an already published Knowledge Asset it missed or only partially received. This is a separate diagnostic lifecycle from the Knowledge Asset Publish Lifecycle and should not be emitted as `ka_publish_lifecycle` publish logs. *Avoid*: Generic sync, peer refresh, background catch-up **Asset UAL**: The canonical operator-facing identifier for a Knowledge Asset in publish lifecycle logs. It is the single value operators should use to isolate logs for one asset across publisher and receiver nodes. *Avoid*: Asset URL, asset UIL, reserved UAL, publish operation ID, batch ID **Publish Lifecycle Log**: A diagnostic log line tied to one Asset UAL that explains a lifecycle state change, the node role, relevant inputs, relevant outputs, and the failure reason when the step does not complete. *Avoid*: Generic debug log, raw structured event, trace-only span **Lifecycle State Change**: A meaningful transition in the Knowledge Asset Publish Lifecycle, including a step starting, succeeding, failing, being declined, being retried, or reaching quorum. *Avoid*: Timer tick, verbose attempt detail, implementation trace **Working Memory**: The local editable layer where a Knowledge Asset draft is created and written before it is shared or published. *Avoid*: Draft store, local memory **Shared Working Memory**: The replicated pre-publication layer where receiving nodes apply, validate, and acknowledge Knowledge Asset data before publication is finalized. *Avoid*: Gossip store, replication buffer **Verifiable Memory**: The confirmed Knowledge Asset layer populated after successful publication or chain-driven reconciliation. *Avoid*: Verified memory, final store **Publishing Node**: The node that initiates publication of a Knowledge Asset and drives the lifecycle through sharing, acknowledgement collection, chain submission, and confirmation. *Avoid*: Originator, sender **Receiving Node**: A peer node that receives publish lifecycle data, validates or stores it locally, and returns the appropriate acknowledgement or rejection. *Avoid*: Replica, target, subscriber **Peer ID**: The libp2p identity of a node process or network endpoint used for transport, gossip, and direct peer interaction. *Avoid*: Node ID, operator ID **Node Identity ID**: The on-chain DKG node/operator identity used for Storage ACK verification, quorum accounting, and attribution when available. *Avoid*: Peer ID, wallet address, generic node ID **ACK**: A protocol acknowledgement returned by a receiving node for a publish lifecycle step. Use the specific ACK name in logs when the distinction matters. *Avoid*: STK, generic success **SWM Share ACK**: A receiving-node acknowledgement that a shared working memory write was applied locally for the Knowledge Asset. *Avoid*: Share response, gossip ACK **Storage ACK**: A receiving-node acknowledgement that signs the publish commitment after the node validates the relevant shared working memory payload for the Knowledge Asset. *Avoid*: STK, generic ACK **Sender Key Package ACK**: A receiving-node acknowledgement or rejection for Sender Key setup package delivery used by encrypted shared working memory payloads. *Avoid*: STK, encryption ACK --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.origintrail.io/agent-context/publish-lifecycle-language.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.