Your e-Person workspace

Choose the right starting point

X@hsimc.tech is the pattern for a stable HSIMC work address, not a promise that an ordinary email inbox, Microsoft 365 account or dedicated computing node has already been created. Identity, workspace access, mail transport and Work authority are separate.

New participant: request an address. Request already made: inspect that request and follow the approved activation route. Already activated: use Sign in. A saved A2A project: return through its original project link and A2A access rules.

This public guide does not read your account, accept credentials or submit forms. A future Assistant or MCP interface is not enabled by publishing documentation.

Sources and verification: S07, S08

1 · Request an address

Open the official registration page. Complete Display name, Requested address, Existing contact email and Subject type (HUMAN, ORGANIZATION or OTHER). Enter only the desired local part in Requested address; the page already adds @hsimc.tech. Use an address name you are authorized to request.

Read the boundary statement and tick it only when understood. Choose “Submit registration request”. A successful response creates REQUESTED, not an activated workspace and not mail service.

Keep the returned Request ID and request secret in your own secure records. The secret may be needed on the original registration status form; do not paste it into this guide, public chat, a QR code or a screenshot. Never submit another request merely because approval is pending.

Use “Check status” on the registration page with your own request credentials. On error or an ambiguous response, inspect the existing request before resubmitting. Registration does not promise an automatic approval email or a completion time.

https://mail.hsimc.tech/registration/

Sources and verification: S01, S02

2 · Understand the approval step

An authorized HSIMC operator handles address reservation, workspace authorization and identity binding. The expected preparation for first activation is EPERSON_ADDRESS_BOUND with WORKSPACE_ACTIVATION_PENDING. REQUESTED and ADDRESS_RESERVED are not permission to enter.

Contact the HSIMC person who is coordinating your invitation or onboarding through the channel already agreed with them. Provide the Request ID and the non-secret error or state, not the request secret. This edition does not establish a new support inbox, automatic approval service or service-level promise.

The public pages describe two activation routes. The current workspace contract names browser challenge activation as the main real-user route. The older registration page still exposes a request-secret claim button when its prerequisites are met. Ask the operator to confirm the applicable route; do not combine the two routes or repeatedly consume credentials.

Sources and verification: S01, S07, S08

3 · First activation: browser challenge

After the operator confirms readiness, open the activation page in the browser and tab you will keep using. Enter your Registration Request ID and choose “Create browser activation challenge”. The page generates a browser secret locally and initially sends only its hash.

Keep that tab open. Share only the displayed Challenge ID with the authorized operator for approval. Do not share the browser secret or contents of session storage. Treat the ID as coordination information for the operator, not as a public post.

After approval, in the same tab, choose “Redeem approved challenge”. The official page sends the proof to its own service. A successful response creates a private session and redirects to your alias workspace. Check that the displayed identity is yours.

The current implementation gives activation challenges a 15-minute expiry; the displayed expires_at is authoritative. Missing local proof, expiry or PRIOR_REQUEST_SECRET_MUST_BE_INVALIDATED requires the documented operator/onboarding process, not a bypass. An operator must handle the previous registration credential before the challenge route can proceed when that gate applies.

The “LEGACY / OPERATOR TOKEN” section is for controlled recovery explicitly arranged by the operator. It is not the normal registration step. This guide does not ask you to obtain, paste or transmit a recovery token.

https://mail.hsimc.tech/activate/

Sources and verification: S03, S04, S07

4 · Return without registering again

Open the official Sign in page. It first tries the saved device login. A successful refresh returns you to the workspace. Refresh is a session operation, not a fresh address request.

When no usable saved login exists, enter your e-Person address or alias and choose “Create login proof”. A Login Challenge applies to an already activated e-Person. Keep this tab open and follow its displayed instructions.

The page may show a mail target and subject. Use them only through the legitimate proof channel confirmed for your account. A displayed instruction does not prove the mail-proof adapter is operating; the public contract still marks that adapter as prepared but not enabled by the core release. Otherwise request controlled operator recovery through the established channel.

The current Login Challenge expires after 10 minutes; use the displayed expiry. On approval the page polls and redeems the challenge. Do not register again, send a browser secret to support, or move the challenge to another browser. A normal login grants private access, not Work execution authority.

https://mail.hsimc.tech/login/

Sources and verification: S05, S06, S07

5 · Read the existing Private Work Space

Identity and status: check the e-Person address and display name. WORKSPACE describes access lifecycle; MAIL TRANSPORT describes a separate binding; AUTHORITY must be interpreted for a specific Work action. A transport field is not a new end-to-end mail test.

REALITY CONTINUE: the inputs are a Reality reference, an optional Work title and your intent. “Continue as Work candidate” writes a candidate to this workspace. It is not the unsaved homepage draft.

CURRENT WORK: shows the returned work candidates and their authority states. REALITY COMPUTE: shows reviewed computation records, versions, readiness dimensions, missing conditions and possible branches. A graph or execution_allowed=false is not an executed result.

AI CAPABILITY · DIRECT KEY P1: credential registration, revocation and provider testing are separate actions. CONSUMPTION LEDGER shows recorded attempts, usage and an estimate when a pricing policy exists. An unknown cost is not zero.

EVIDENCE / EVENTS records activity metadata; an event is not automatically acceptance of a commercial task. Use Sign out when finished. Do not treat the absence of an item in a limited response window as proof that all history is empty.

Sources and verification: S07, S09

6 · Continue one small piece of work

Use a public Reality URL or a reference you are entitled to use. State one concrete need in your own words, for example: “Compare two packaging options and list missing evidence; do not place an order.” The example is illustrative, not an existing customer record.

Before choosing “Continue as Work candidate”, check that you intend to save to this workspace and that the text is appropriate for its access scope. The current service requires a Reality reference and intent; it is not a global file-upload form.

After success, keep the returned Work ID and verify the candidate reappears when the workspace reads its records again. CONTINUED_AS_WORK_CANDIDATE with UNRESOLVED is a saved candidate, not accepted delivery or authority to execute.

When a write result is uncertain, inspect existing records or ask the responsible operator before repeating it. This guide has not performed a real Work save. Mail workspace Work and A2A projects are not automatically the same object or membership.

https://hsimc.tech/a2a/ · https://hsimc.tech/work/ · https://hsimc.tech/start/

Sources and verification: S09

7 · What My Dashboard will mean

D0-002 is an optional read-only view of the existing workspace response. As of this guide’s check it is not activated. Do not troubleshoot a missing Dashboard button by changing permissions, registering again or executing scripts.

When separately enabled and verified, its areas are identity and scope, work and needs, computation references, materials and resources, connections and nodes, and usage observation. It does not automatically assign historical catalogs, tools, provider accounts or computing nodes to you.

A source Reality reference is not ownership or membership of that Runtime. A listed resource is not an executable capability. Private access, provider capacity, budget and action-time authority must remain distinct.

The current source response is capped at 50 Work items, 50 computation records, 100 call attempts and 30 events. Counts describe the returned window, not lifetime totals. This guide documents the release boundary; it does not activate the Dashboard.

Sources and verification: S09

8 · Optional AI connections and costs

You do not need a provider key merely to read this guide or understand the workspace. Only an authorized account holder should decide to register a key in the verified private interface. Never send it in chat, an ordinary support note or a public document.

“Register credential” and “Revoke credential” change credential state. “Run provider test” is a real provider call that may consume quota and incur charges. It is not a harmless tour step; do not click it as part of onboarding unless separately authorized.

The existing page distinguishes key metadata, provider/account/project rate scope and usage records. More keys do not establish independent capacity. No price or provider connectivity is verified by this guide.

Sources and verification: S09

9 · When you cannot continue

ALIAS_UNAVAILABLE or ALIAS_RESERVED: review the requested name or ask the coordinator; do not try to recover another person’s address. REQUESTED: wait for the controlled approval process rather than registering repeatedly.

CHALLENGE_NOT_READY: ask the operator to verify preparation. PRIOR_REQUEST_SECRET_MUST_BE_INVALIDATED: the prior credential needs operator handling; do not disclose it or try the older route as a workaround.

“This browser does not hold the secret…” or an expired/consumed challenge: return to the original tab when valid, otherwise follow the operator’s new-challenge procedure. Old proofs cannot be reused.

No usable saved device login: use Login Challenge for the already active identity. Repeated redirects or SESSION_REQUIRED: stop repeated writes, retain your own unsaved text safely and return through normal Sign in.

Wrong identity, unexpected private content, suspended or revoked state: stop and contact the responsible operator. Do not share the other person’s data. A missing My Dashboard button currently means the entry is not enabled.

A2A asks you to log in: use its own existing access path. Mail sign-in is not automatic A2A membership. If no response or support arrangement is established, do not assume a team has accepted the issue.

Sources and verification: S01, S03, S04, S05, S06

10 · Safe support and handover

Share only the minimum needed with the established HSIMC coordinator: the public page path, approximate time and timezone, operation, non-secret error, and Request ID or Challenge ID when applicable. Redact screenshots and do not include raw private Work text.

Never include request secrets, browser secrets, one-time recovery tokens, Cookie values, API keys or unredacted response dumps. This document provides no credential field and does not collect a support ticket.

The QR, copy and print controls here transfer only this public guide URL, not an account, private alias, proof code or Work URL. Copying instructions does not submit a request or save work.

Sign out on shared devices and do not paste commands into a browser console to get around login. Public documentation is not private account access.

Sources and verification: S01, S03, S07

11 · Status vocabulary and evidence limits

REQUESTED = request recorded; WORKSPACE_ACTIVATION_PENDING = awaiting first activation after authorized preparation; WORKSPACE_ACTIVE = access lifecycle active, not proof of a currently valid browser session.

CONTINUED_AS_WORK_CANDIDATE = persisted candidate; UNRESOLVED = action authority not resolved; COMPUTED_CANDIDATE_GRAPH_NOT_EXECUTABLE = computation proposal, not execution; TRANSPORT_NOT_PROVISIONED = a transport-state field, not a fresh delivery test.

This edition is based on public pages/contracts, current source hashes and the dated Dashboard staging receipt. It has not submitted registration, redeemed a proof, borrowed a session, sent email, saved Work or tested a provider. Page availability is not end-to-end onboarding acceptance.

Known documentation mismatch: registration and workspace contracts describe different generations of activation. We expose this difference and recommend operator-confirmed browser-challenge onboarding; this publication does not silently repair authentication or make approval automatic.

Sources and verification: S07, S08, S09