agentic publishing · governed federation

Correction and Retraction — Withdrawal Propagation

Correction and Retraction — Withdrawal Propagation is implemented as a source-bounded withdrawal propagation guide.

Active canonical release · fedrelease_dcdf91f62ed45c00749d75e58007fda0 · exact revision sha256:bc9ca36a8b4fd9f3f8e0e808aba7c84c0108af07cb58d1ed0d49122ca36c3996

answer

Direct answer

Correction and Retraction — Withdrawal Propagation is implemented as a source-bounded withdrawal propagation guide.

method

Answer contract

Apply the withdrawal propagation lens only to the exact inspected source scope; do not infer authority from adjacent topics.

evidence

Evidence and exact locators

Source-reference withdrawal propagation contract — lib/source-evidence-reference.ts — GOVERNANCE_MODEL and evaluateSourcePage; test/source-first-engine.test.ts — must trace to an active released revision. Supports: Makes source-reference pages projections of active released claims and removes eligibility when an underlying record is withdrawn or no active released claim remains.

limitations

What the evidence does not establish

The projection does not retract external copies, prove the underlying claim false, or replace canonical release governance.

rights

Rights and reuse

project-owned-reference-only

relationships

Dependencies and related concepts

applies-to: urn:maha:concept:evidence:correction-and-retraction

governed-by: urn:maha:concept:governance

evidence-for: urn:maha:concept:evidence

required-by-specification

Executable contract

This executable contract section is constrained to the same inspected scope: Makes source-reference pages projections of active released claims and removes eligibility when an underlying record is withdrawn or no active released claim remains.

It must preserve the recorded boundary: The projection does not retract external copies, prove the underlying claim false, or replace canonical release governance.

required-by-specification

Verification evidence

This verification evidence section is constrained to the same inspected scope: Makes source-reference pages projections of active released claims and removes eligibility when an underlying record is withdrawn or no active released claim remains.

It must preserve the recorded boundary: The projection does not retract external copies, prove the underlying claim false, or replace canonical release governance.

required-by-specification

Failure boundaries

This failure boundaries section is constrained to the same inspected scope: Makes source-reference pages projections of active released claims and removes eligibility when an underlying record is withdrawn or no active released claim remains.

It must preserve the recorded boundary: The projection does not retract external copies, prove the underlying claim false, or replace canonical release governance.

required-by-specification

Dependencies

This dependencies section is constrained to the same inspected scope: Makes source-reference pages projections of active released claims and removes eligibility when an underlying record is withdrawn or no active released claim remains.

It must preserve the recorded boundary: The projection does not retract external copies, prove the underlying claim false, or replace canonical release governance.

bounded answers

Questions this page can answer

What is implemented?

Correction and Retraction — Withdrawal Propagation is implemented as a source-bounded withdrawal propagation guide.

Which exact locator proves it?

Source-reference withdrawal propagation contract, lib/source-evidence-reference.ts — GOVERNANCE_MODEL and evaluateSourcePage; test/source-first-engine.test.ts — must trace to an active released revision

What fails closed?

The projection does not retract external copies, prove the underlying claim false, or replace canonical release governance.

What does the implementation not establish?

applies-to: urn:maha:concept:evidence:correction-and-retraction governed-by: urn:maha:concept:governance evidence-for: urn:maha:concept:evidence

Which release gates remain?

A source, locator, rights, scope, boundary, dependency, implementation, or release change requires a new exact-revision review.