# Save work in G2X

Use this playbook when the user wants an agent-authored brief, requirements set, compliance matrix, qualification, proposal section or response kept in G2X. The destination matters: a library document, a saved artifact, a structured pursuit record and an editable proposal section serve different purposes.

## Choose the real destination

Inspect the connected save, import and edit capabilities and read the target's current state. Use an existing G2X ID from the user's accessible records, and resolve ambiguous company, opportunity or workspace names before writing. Choose the appropriate structured destination when it is supported. Do not label a library attachment as an applied proposal edit or an imported requirements set.

If a structured import is unavailable, offer a supported document or artifact save and say what it accomplishes. A request to update a proposal should not quietly become an unrelated personal artifact. Keep doing useful drafting while a consequential destination choice is pending. Do not invent a tool or call a private endpoint to fill a capability gap.

## Preserve content and authorship

Provide the requested complete content in the schema and format the tool accepts. Carry source document and version IDs and valid citations into requirements, qualification and compliance outputs. Keep assumptions, unsupported claims and unresolved questions distinguishable. Save the final work and its supporting evidence. Leave out hidden reasoning transcripts and unrelated conversation history.

Record truthful user or agent authorship. Do not fabricate a Lumen conversation, an internal analysis run, a reviewer approval, a company certification or a source citation. A model-authored draft is not a verified compliance determination. Prefer a save path that does not run G2X analysis; if none exists, explain the consequence before using a combined operation.

For long outputs or files, follow the supported transfer method in [Documents and changes](documents.md). A file link alone does not prove that G2X received or saved the contents. Do not silently shorten the response to fit a tool message. If no complete transfer is available, keep the complete draft and offer the available G2X upload flow.

## Save once and verify

Use supported idempotency controls for creates and the current revision for edits. A conflict means the target changed: read the accessible current version, reconcile the relevant changes and preserve the user's intent. Do not overwrite another contributor's work by retrying blindly. After an uncertain response, inspect the existing result before repeating the save.

Read the result back through the ordinary G2X read capability. Confirm the destination, the identity, the complete content or returned size and hash, and the saved version. Return the actual G2X link so the user can open the work and continue. If only a proposal for review was saved, say that it is pending review; do not claim the edit was applied.

If saving returns an ID and link but no supported readback exists, keep the acknowledgment and say that you could not verify the saved contents. Do not retry the save to check it, and do not treat a link as proof that a proposal was updated. Keep the complete draft available and point the user to the returned G2X destination for review.

Retain references so a later authorized client can pick up the same work. Updating a qualification, changing a bid decision, moving a pipeline stage and recording a CRM interaction remain distinct operations. Make only the changes requested, and do not trigger another analysis just to save a completed result.