[L'OREAL] Public read access to compiled SQL / _UPD_ view DDL

Where we stand: with the API key we read and write data maps and query the OData views, and the full loop has now run live on the AI - POC release — an AI-generated rule written in, read back, compiled to SQL, the ETL build triggered, and the view deployed. Everything beyond the data-map write, however, rides the interactive session token (concento-authtoken), which we measured at 300 seconds of life and which only a person completing SSO + MFA can mint. That single constraint is what separates a working PoC from an unattended service.

2. Public read access to compiled SQL / UPD view DDL.

On our test object, 10 of its 11 rule tasks have their logic stored only as view SQL in the database, with no rule in Syniti (104 fields across the release). COMMAND_TEXT being null means this SQL is invisible to the API key.

Our safety procedure around every build — capture all view definitions before, verify byte-identical after, restore on any regression — therefore works today only through the session-authed SQL Editor.

Without a durable read path there is no automatable backup, and a build is an unrecoverable risk.