HSIMCHUMAN REALITY COMPUTE INFRASTRUCTURE

REGISTER REALITY · KEEP IT COMPUTABLE · LET IT CONTINUE

State should survive
the model session.

A Reality JSON is a durable, versioned address for what exists, what is claimed, what is authorized, what remains unknown and what can continue. The public Visual and exact machine JSON are two projections of the same Reality.

— registered seed Reality— existing Organization references— holder-authorized Place seedsPUBLIC WRITER = NONE

HUMAN + MACHINE VIEW

One Reality ID. Visual for people. Exact JSON for AI.

Loading…

REALITY OVERLAY · RESONANCE

Continue another person's Reality without overwriting it.

Base Reality: —

OVERLAY_DRAFT_NOT_MERGED

e-PERSON PROPOSAL

Persistent address. Stateless Authority. Computed execution.

Subject Reality: —

Model Access →
EPERSON_ADDRESS_PROPOSAL_NOT_ACTIVATED

STATELESS e-PERSON EXECUTION

Never trust yesterday's role or Authority.

An e-Person keeps a stable address, but every action must resolve current Work, Role View, Authority, lifecycle, Human Supervisor, model/capability and expiry from current Reality. Trustee, AI Worker and AI Employee are Work-scoped views—not permanent identity types.

An HSIMC email alias, if later provisioned, is for e-Person ID, billing, notification and HSIMC role routing only. It is not a private personal-information management mailbox.

LOCAL UPLOAD / PREVIEW

Bring a Reality JSON without giving it to the server.

NO FILE · browser-local preview only

C0 uses FileReader in your browser. No upload request is sent to HSIMC.

LOCAL_PREVIEW_NOT_REGISTERED

REGISTER / UPDATE REQUEST

Registration is controlled; the public browser can prepare the request.

REALITY_REGISTRATION_REQUEST_DRAFT_NOT_SUBMITTED

CONTINUITY MODEL

Register → Update → Overlay → Continue. Never silently replace the past.

Registered ≠ owned ≠ authorized to execute.

Reality registration creates a stable address, version, provenance and public/machine projection. It does not certify title, tenancy, company representation, tax status, customer/supplier relationship, employment, API credentials or execution Authority. Pannex e-Person activation remains subject to the required co-holder authorization. e-Person address or email alias never proves current role, Authority, lifecycle or execution permission.