Sharing Answers

MARCUS answers are most useful when the recipient can still understand where they came from. A perfectly written answer without citation context is often less trustworthy than a shorter answer that clearly shows its evidence trail.

This guide explains how to share output responsibly.

The Main Rule

Shared answers are only useful if the recipient can still see the source grounding or receive enough context to audit it.

Preferred Sharing Pattern

Share answers that include:

• the answer text
• the relevant citations
• enough project or source context for the recipient to understand scope
• any important caveat, such as low coverage, source conflict, or local-only applicability

Think of sharing as forwarding a clinically relevant note with its references intact, not copying a conclusion out of context.

Before You Share

Check these questions:

1. Is the answer grounded in the right project?
2. Are the cited sources the ones you actually want to circulate?
3. Is the answer specific to a local workflow that may not generalize?
4. Is any sensitive or organization-restricted content involved?
5. Would the recipient know how to verify the claim if they needed to?

If the answer depends on nuance, include the nuance.

When To Share The Answer As-Is

An answer is more shareable when:

• the citations are strong and directly relevant
• the answer is narrow and concrete
• the corpus context is clear
• the recipient is inside the same operational environment

Examples:

• a local discharge criterion pulled from the current protocol
• an escalation threshold directly supported by the cited institutional source
• a workflow step where the cited passage is straightforward

When To Add Commentary Before Sharing

Add your own framing when:

• coverage is low
• the answer draws from multiple sources with different authority
• the conclusion depends on local context
• two sources conflict
• the answer is correct but easy to overgeneralize

Useful commentary can be as simple as:

• "This appears to come from our local protocol rather than an external guideline."
• "The corpus shows disagreement here; see both cited sources."
• "Coverage is limited, so this should be verified before use."

If Two Sources Conflict

Do not share only the synthesized conclusion. Include the conflict explicitly or ask a follow-up question that narrows the scenario first.

If needed, share:

• both competing citations
• which source appears more authoritative
• whether one is local policy and the other is general background

Hiding disagreement creates false certainty.

Sharing Inside Versus Outside The Team

Inside the same project team

You can often assume shared context, but you should still preserve citations for anything important.

Across teams or outside the immediate workflow

You need more context:

• what project the answer came from
• what kind of source supported it
• whether it reflects local process or general evidence
• whether it should be treated as informational rather than directive

The farther the answer travels from its original context, the more explanation it usually needs.

What Not To Do

• Do not strip away citations and forward only the prose.
• Do not circulate a strong-sounding answer that rests on weak evidence.
• Do not share a local policy answer as if it were universal guidance.
• Do not share a synthesis that hides an unresolved conflict between sources.

Best Operational Use

MARCUS is strongest when it shortens the path to the right passage in the right document. Share answers as a starting point for review, not as an uncited final directive.

One Safe Habit

Before sending any important MARCUS answer to someone else, ask yourself: "If they challenged this statement, would they have enough information to verify it?" If the answer is no, share more context.