Identity
Authentication establishes who is present; it does not by itself authorize a consequential operation.
Security
Control is part of the operating architecture.
Neptlium separates identity, authorization, privileged operations, financial state and provider evidence. These are architectural principles, not claims of certification, insurance, regulatory approval or perfect security.
Control boundaries
A consequential action crosses more than one boundary.
- 01Identity
- 02Authorization
- 03Ownership
- 04Policy
- 05Auditability
- 06Reconciliation
Authority
Roles, ownership, policy and resource state remain server-enforced boundaries.
Privilege
Provider secrets, service credentials and privileged commands stay outside public browser authority.
Evidence
Operational transitions should remain attributable and reviewable rather than inferred from presentation state.
Fail closed
Missing credentials, unavailable dependencies or unverified capability must not become simulated success.
Replay resistance
Consequential operations are designed to resist accidental duplication and unsafe replay.
Data boundaries
Ownership, row-level controls and service boundaries constrain access according to the responsible subsystem.