A boundary, not a badge.

Authentication does not imply organization membership or resource access. Organization roles are composed from explicit claims, may be assigned at a defined scope, and are re-evaluated by the context that owns the requested operation.

• Verified account lifecycleRegistration, email verification, recovery, opaque sessions, and password screening avoid unnecessary account disclosure.
• Multi-factor optionsPlatform passkeys, roaming FIDO2 security keys, TOTP authenticators, and single-use recovery codes are supported.
• Fresh privileged sessionsSensitive owner and security actions require a recently confirmed strong authenticator.
• Versioned roles and invitationsAssignments refer to an explicit role version; invitations are email-bound, expiring, single-use, and revalidated at acceptance.
• No implicit external membershipA public contributor can propose work without silently becoming a member of the target organization.

Pipeline orchestration resolves and records a canonical plan, while a separately operated rootless supervisor executes user code. The application container never receives a Docker or Podman socket.

External-contributor execution

• Exact grantAn authorized maintainer grants one exact repository revision and one resolved plan, not a moving branch.
• Restricted authorityUntrusted jobs receive no protected secrets, privileged mode, host mounts, deployment authority, package publication authority, or trusted cache writes.
• Immutable attemptsLogs, test results, and artifacts belong to an immutable attempt. Retrying creates new history.
• Honest uncertaintyRunner loss after possible execution becomes indeterminate rather than silently running user code again.

Mozaic keeps working state and public state distinct. New resources start non-public; an authorized user publishes specific project and repository state or a specific immutable knowledge checkpoint.

• Ancestor visibility is enforcedA project cannot become effectively public through a private organization, and a repository cannot bypass private ancestors.
• Public readers receive a bounded viewPublic pages expose only permitted project metadata, published knowledge, public source, visible work, trusted builds, releases, and activity.
• Knowledge publishes a checkpointReaders do not see an editor’s changing working state unless an authorized user deliberately publishes a new revision.
• Package lifecycle stays auditableVersion bytes are immutable; unlisting and deprecation are metadata changes, while elevated purge retains a tombstone.

Security-relevant state changes produce governance audit evidence. The operated topology also exposes component readiness, runner state, storage integrity, backup posture, incidents, migration state, and delivery queues to supported operator views.

• Trace context and typed errorsHTTP boundaries retain diagnostic context without turning internal failure into a false success.
• Durable delivery stateMail, notifications, events, and signed outgoing webhooks use persistent handoff and idempotent processing.
• Storage verificationBlob state and integrity scans can identify missing, mismatched, unsafe, or unverified data.
• Backup posture is explicitThe operator receives a persistent critical warning when remote recovery is not configured and total host loss remains unrecoverable.