Disclosures and updates

When a thread has downstream derivations — copies made by shipments or slices — its owner controls what those downstream teams can see of it. That choice is a disclosure: the source team selects which fields, files, and identifiers flow down the Fabric chain. What is disclosed is shown faithfully; what is withheld simply doesn’t appear downstream.

Disclosure runs in both directions for you:

• As a source, you push disclosures from threads you own.
• As a recipient, disclosed changes arrive as updates you can review and bring into your own thread.

What is disclosed is shown faithfully to every downstream team; what is withheld simply doesn't appear. Recipients choose whether to adopt disclosed changes into their own copy.

Note

These features ride on the Fabric surface, whose availability depends on your organization’s configuration (it is enabled when Shipments or Slicing is enabled). If Updates is missing from your navigation, it isn’t enabled (see the FAQ).

Pushing a disclosure

You push from a source thread you own — from its Fabric explorer’s Push disclosure action, or the same button on the thread’s Lineage card. This opens the Push disclosure page.

1. Choose what to disclose. The left side lists the thread’s assets by section — Positions, Data, Files, Identifiers — with All / None shortcuts. Items already disclosed show a Disclosed badge; changed ones show New or Updated. Private items can’t be selected (“Private — can’t be disclosed”).
2. Preview. The right side shows what downstream consumers will see through this thread’s fabric chain — exactly the disclosed rendering, nothing more.
3. Optionally toggle Advance cursor to reveal the thread’s recent events downstream. You can also push with no asset changes at all — a “cursor-only push — reveals recent events, no asset changes.”
4. Optionally add a Reason — it is recorded on the Fabric timeline.
5. Click the push button (for example Push 3 assets). On success: “Disclosure pushed — downstream consumers can see the update.”

Disclosure is chain-wide

As the page itself warns: “Disclosure flows the whole way down the Fabric chain — everyone downstream sees this. Once disclosed, it can’t be un-seen, only redacted later.”

Revising later

Push again whenever the thread changes — the composer marks what’s New or Updated since your last disclosure. An asset you take back out of the disclosure appears downstream as Removed (“removed from this link — no longer disclosed”) or Redacted (“redacted by the source — details withheld”); downstream teams keep any local copy they already adopted, but see no further detail.

Receiving updates from your sources

When an upstream source pushes a disclosure to a thread you own, DICE surfaces it as an update in three places:

• On the thread — an updates panel showing “Updates waiting for your decision”, with a per-source view of everything disclosed to this thread.
• The thread’s Updates page — Updates for <thread>: “Review what your sources disclosed and choose what to bring into this thread.”
• The app-wide Updates feed — the Updates page in the navigation lists every thread of yours with pending updates (“New information disclosed by sources of your threads”), searchable by thread or source name, with a Review action per row.

You can Dismiss rows from the feed — this clears the reminder only; the disclosed information stays available and you can still review it from each thread’s Updates page at any time.

Reviewing an update

Each disclosed item is one row — a Field, File, Identifier, or Certificate — with a status:

Status	Meaning
New	The source disclosed something not on your thread yet.
Update	The source changed something you already carry a copy of.
Needs review	It can’t be applied automatically — for example a replaced file, or information not linked to anything on your thread yet.
Removed by source	The source withdrew it from the disclosure; your local copy is untouched.
Changed locally	Your copy has diverged from the source’s.
Skipped / Hidden locally	You decided earlier; some decisions “can be brought back”.
In sync	Your copy already matches.

Each row shows the comparison — “Source says” versus “This thread has” — and offers the matching action:

• Add to thread — take a new item onto your thread.
• Update local copy — apply the source’s change to your existing copy.
• Use source info — resolve a Needs review item by taking the source’s version.
• Acknowledge — for certificates: note it without adding a copy (including voided ones — “the voided file is on this thread — hide your copy, or acknowledge to keep it”).
• Skip — decline it: “The source information stays visible; this thread just won’t take it in.”
• Hide local copy — when the source removed or voided something you’d adopted: keeps the record in history but removes it from your thread’s active data by making the local copy private and archived. You can restore it later. If you already disclosed that item onward, DICE reminds you to also remove it from your own Fabric disclosure.

Every decision can carry an optional note. Adopting applies the change to your copy — your thread stays yours; nothing changes on it without your action.

Review all opens a batch review that applies every automatic New/Update row at once with a single Add and update confirmation; Needs review items still require individual decisions.

Anyone who can see the thread can look at its updates, but “only an editor of this thread can apply them.”

The disclosure record

Every push is recorded. In the Fabric explorer, select a link and open its Timeline tab to see the Disclosure timeline: each disclosure revision, who made it (the Actor), when the event cursor advanced, and any reason that was entered at push time. This gives both sides — source and recipient — the same durable record of what was disclosed and when.