NFL Pulse

Privileged workspace

Staff

Production staff access requires SSO, MFA, least privilege and audit. This fixture uses a local test identity only. Every action on these pages is executed by the API, which is the only enforcement point: the rights gate, the editor-role gate, the separation of audit from editorial authority and, when the dormant critical-alert control is switched on, its two-distinct-editor rule are all applied server-side. Nothing here can bypass them, and a refusal is shown with the server's own reason.

Intake reference data was refused by the server (HTTP 403)

Fixture identity headers are not accepted in production mode. Use a Cognito or staff SSO bearer token.

This is the server enforcing authorization, not a display problem. The acting identity does not hold the role this endpoint requires. Nothing on this page can grant it.

Manual link-first intake

Creates a Source Item, a Claim at status Attributed with its status-history row, supporting Evidence and one feed Signal. The rights gate runs first: a state outside the approved set, or a missing legal basis reference, is refused 422 and nothing is written.

SourceEventCanonical URLMust not already be ingested; a repeat is refused 409. Fixture URLs only -- no live NFL source is contacted.Rights stateFrom the API's own approved set. Anything outside it is refused by the server.Legal basis referenceRequired. The rights gate refuses publication without one.Historical publication time (UTC)When the source itself was published. Leave blank if unknown -- it is stored as unknown, never as today. Read as UTC. A future time is refused by the server.Claim textStored as the Claim's normalized text.Signal label

Attach a further Source Item to an existing Claim

This is the path a repeated claim actually arrives on: another outlet carries something the Claim already says. Constitution section 11 decides whether it earns a second feed card. Suppression is not rejection -- the Source Item is ingested, the Evidence attached and the existing card's attention metadata updated; what the repetition does not get is a second feed position unless it adds a NAMED material ground.

ClaimSourceCanonical URLRights stateLegal basis referenceHistorical publication time (UTC)When the source itself was published. Leave blank if unknown -- it is stored as unknown, never as today. Read as UTC. A future time is refused by the server.Evidence typeDirectionA contradicting Source Item is attached, not discarded. Conflict is shown, not resolved by hiding one side.Lineage typeIndependence chain tagOptional. Derived from the Source Item id when left blank.Derives from Source ItemWhere the editor already knows this derives from an existing item. Selecting one makes the independence state below required.Derivation independenceMaterial groundsComma-separated. Leave blank to name none: a repetition with no named material ground does NOT get a second feed card.NoteReleased with postThe post that reveals this Evidence to readers; it must be on the same Event as the Claim. Leave blank: a new feed card reveals it, and with no new card it stays unreleased (listed below) until a post is named.

Evidence waiting for a post

Readers cannot see these until a post that reveals them is released (release clock, Task 013).

No unreleased Evidence.