PublicWire
Back to edition
Reference runHeldRevision 1

Proposed downtown parking rule change

The reference run contains conflicting effective dates in two sections of one captured source packet, so the workflow holds the item before drafting.

·

  1. Capture sourcescomplete
  2. Identify claimscomplete
  3. Check evidenceblocked
  4. Classify relevanceskipped
  5. Write from claimsskipped
  6. Publication boundaryblocked
Finding at capture

What the run established

The reference run contains conflicting effective dates in two sections of one captured source packet, so the workflow holds the item before drafting.

Why it matters

Residents should not act on a parking-rule date while sections of the captured packet disagree. The contradiction remains visible instead of being averaged into a confidence score.

Who may be affected

No affected group has been established.

Interrogate the record

Start with your question

Move from the result to the exact claims, sources, agent catches, and revisions behind it.

Answers stay inside the disclosed case record.
Input to output

1 supported claim across 1 source

Every supported statement below points to a bounded excerpt from a captured, versioned source. Open a claim to see the exact receipt, then follow the source link to inspect the original context.

Exact receipts
2
Independent URLs
1
Still checking
0
Inspect claim 1City source domain · parking packet scenario
Inside the check

Follow the pivotal decisions

Conflicting dates stoppedBounded reference run

Proposed downtown parking rule change

Two sections of the same packet disagree. The system preserves both instead of guessing.

Run contractInput → agent checks → output
02 · Agent impact

Conflicting dates stopped

Two sections of the same packet disagree. The system preserves both instead of guessing.

Supported
1
Disputed
1
Drafts created
0
03 · OutputNo article emitted

The workflow stopped before prose

The public result is a typed hold: contradiction. Unsupported material never becomes an article.

Downstream writer and publication calls were not invoked.

Follow the handoffsSelect any step
Claim and evidence ledger

Receipts, not a confidence score

Living source record

What changed and what it affected

PublicWire keeps each captured source version and rechecks linked claims when the source changes. A missing page alone never becomes a correction or retraction.

Source timeline

  1. capturedCaptured packet · reference v1City source domain · parking packet scenario

Evidence disagreement assessments

Equal-authority conflictMaterial disagreement remains open

Two sections of the same captured official packet provide different effective dates. The resolver cannot select one by voting, so the material date remains held.

This assessment does not change the claim’s verified status by itself. It is linked to 2 disclosed source receipts and the affected claim.

Reference activity

Scenario event projection

Contract fixture

Latest activity: Desk check completed: held.

  1. capture

    1 source captured, including municipal parking scenario packet.

  2. extract

    2 material claims identified for checking.

  3. verify

    1 supported; 1 disputed.

  4. verify

    The verify boundary held the item: contradiction.

  5. verify

    Desk check completed: held.

Immutable record

Updates and corrections

    No revision history yet.

    Corrections and source refreshes will remain visible here.