EAINE access model

Open knowledge. Controlled responsibility.

Inspect the discipline freely. Add identity and approval only when personal data, privileged decisions, or unreleased work require them.

Explore the open frameworkUnderstand reviewer access
Trust architectureAccess narrows as responsibility increases
  1. 01
    Open commonsInspect and reuse

    Framework · standards · public evidence

    Open
  2. 02
    Verified participationContribute with identity

    Review · correction · attributed evidence

    Verified
  3. 03
    Protected operationsAct with explicit authority

    Personal data · entitlements · private assets

    Controlled

Five access classes

One framework, with explicit boundaries.

Every page, record, package, and future asset belongs to an access class. Access becomes narrower as identity, personal data, and decision authority increase.

01
Everyone

Open public

Inspect, learn, apply, and challenge the framework.

The public website, Candidate framework, lifecycle, standards, selected examples, evidence, and Apache-licensed repository material stay open.

  • Public routes and sitemap
  • Checksummed public source package
  • Candidate limitations remain visible
02
Authenticated and relationship-verified

Verified customer

Download a protected publication edition.

A trusted Azure identity must match a PostgreSQL customer record that EAINE has explicitly verified. Newsletter registration and general sign-in do not grant access.

  • Trusted identity plus customer verification
  • Private Blob delivery through the server
  • Download event without marketing consent
03
Authenticated individual

Signed-in applicant

Manage only your own reviewer application.

A signed-in applicant can submit interest, verify contact channels, inspect their own status, withdraw permission, or delete their application.

  • Server-verified identity
  • Same-origin API and record ownership
  • No reviewer material or administrative access
04
Named, verified, time-bound

Approved reviewer

Enter a revocable review workspace.

Approved reviewers receive the unpublished review edition through identity-bound private delivery and can save or submit feedback within their access window.

  • Human approval and active entitlement
  • Expiry, revocation, and access checks
  • Personalized watermark, recorded delivery, and structured feedback
05
Explicitly authorised operators

Administration + internal

Protect people, decisions, and unfinished operations.

Applicant data, decision notes, communication operations, raw reviews, working memory, credentials, logs, and unapproved drafts remain restricted.

  • Server-side administrator allowlist
  • Least privilege and retention
  • Excluded from public packages

Boundary rules

Protection is a system property, not a label.

EAINE separates publication, authentication, authorization, licensing, and storage so none is mistaken for another.

01

Open stays open

Material already released under Apache 2.0 remains open. A login cannot revoke the licence or previously distributed copies.

02

Sign-in is not entitlement

An account identifies a person. Separate checks establish contact control, professional authenticity, administrator authority, and reviewer access.

03

Protection happens on the server

Hidden links, noindex, and client-side checks are not security. Protected data and actions require server-side authorization on every request.

04

Private previews need private delivery

Future unreleased book or platform previews require private storage, expiring delivery, logging, and revocation before EAINE calls them protected.

Current access decision

The discipline and Founding Review Edition are open. Private capabilities stay controlled.

Anyone can inspect the framework and download the public review edition. Reviewer workspaces, customer-only material, personal data, and privileged operations remain closed until their privacy, identity, storage, accessibility, and support gates pass.

Review Candidate limitationsUse a public contribution route