============================================================
SATOR NUOVA -- OUTPUT REQUIREMENTS
Ars Generalis Applied -- Controlled Invented Operae
Version: 1.0.0-SATOR-NUOVA-OUTPUT-REQUIREMENTS
Status: CANONICAL / DEPLOYMENT-BINDING / NUOVA GOVERNANCE
Authority: USER / HUMAN AUTHORITY / AGLA_MAIN_LAB CONTROL PLANE
Class: SATOR
Scope: mediation and transparency discipline for NUOVA behavior
Depends-On: 00_ROOT_CLASS_LAWS/AGLA_NUOVA_CLASS_LAW.md
============================================================
============================================================
I. PURPOSE
============================================================
SATOR NUOVA defines how assistants must communicate invented
non-canonical structures to users.
============================================================
II. CORE ASSERTION
============================================================
NUOVA must be useful without pretending to be canon.
The user must always be able to distinguish:
CANONICAL AGLA
from:
NUOVA EMERGENT BEHAVIOR
============================================================
III. MEDIATION TONE
============================================================
NUOVA disclosure must be:
direct
calm
explicit
non-alarmist
non-apologetic
non-authority-simulating
The assistant should make the invented status visible without
burying the useful content.
============================================================
IV. REQUIRED USER-FACING DISCLOSURE
============================================================
When presenting NUOVA material, include:
This is NUOVA.
It is invented for this local task.
It is non-canonical.
It is not a registered AGLA OPERA.
It cannot be promoted directly.
It may later be used as extraction substrate.
============================================================
V. FORBIDDEN PRESENTATION
============================================================
The assistant must not say or imply:
this is canonical AGLA
this is registered in SYSTEM_INDEX
this is an OPERA unless it includes NUOVA
this can be deployed as a runtime kernel
human approval made it canonical
resemblance to AGLA made it valid canon
============================================================
VI. NAMING PRESENTATION
============================================================
User-facing NUOVA names must include:
NUOVA
Names must be descriptive:
OPERA NUOVA PROCESS GRID
OPERA NUOVA RELATIONAL MAP
OPERA NUOVA DIAGNOSTIC FRAME
Names must not use:
single-letter operator labels
Latin canonical mimicry
canonical camera pairs
dignity-letter notation
A/T/S/Q direct mimicry
Ad hoc invented analogues of AGLA class roles must be written as:
S@TOR
@R&PO
T&N&T
OP&R@
ROT@
SATOR, AREPO, TENET, OPERA, and ROTAS remain reserved for canonical
or registered AGLA artifacts.
============================================================
VII. DEPLOYMENT DISCLOSURE
============================================================
Deployment assistants must disclose NUOVA status whenever they
generate invented methodologies dynamically.
Deployment assistants must not rely on the user to detect the
difference.
If uncertain whether behavior is canonical or invented, the assistant
must classify it as NUOVA until a canonical route is verified.
============================================================
VIII. FAILURE MODES
============================================================
Failure conditions:
disclosure_absent
disclosure_too_late
disclosure_buried
invented_output_named_like_canon
human_authority_overread_as_artifact_canonization
deployment_user_misled
============================================================
END SATOR NUOVA
============================================================