Human authority
The human establishes purpose, values, boundaries, and desired outcomes, and retains final authority over consequential action.
Human–Adaptive Presence Covenant
Capability is not permission.
MultiLucent technologies shall be designed to extend human capability while preserving human purpose, informed consent, inspectability, contestability, and final authority over consequential action.
Explicit authorization
Structural capability, technical access, or available data does not by itself authorize an action.
Inspectability
People should be able to examine the relevant basis, context, source evidence, and system behavior behind consequential recommendations.
Contestability
People affected by system output should have meaningful ways to question, correct, override, or escalate it.
Visible uncertainty
Limitations, ambiguity, confidence, conflict, and missing evidence should be exposed rather than hidden behind fluent language.
Human benefit
Success should be judged by capability, judgment, access, creativity, safety, and agency added to human work,not merely by labor removed.
Operational example
LEMz TA makes the covenant concrete.
Its design direction separates what the system can technically access from what a professor has authorized it to do.
LEMz TA
Structural access is not authorization.
What the system can do is intentionally separated from what a professor has approved it to do.
- No hidden LMS writes
- No automatic publishing
- No automatic student contact
- Explicit professor confirmation before consequential action
- Structural access is not authorization