OpenSite/Reference/Features/Accounts and licensing

From BathAfrica Documentation
Revision as of 13:59, 29 October 2026 by BathAfrica (talk | contribs) (Reorganize OpenSite reference with shared scope and related workflows)
Jump to navigation Jump to search
OpenSite 0.0.1 · DevelopmentSource scope and availability


Desktop account client foundation. Website sign-in is still planned.

Stable identifier
product.entitlements

Status reported by source

Planned: website sign-in. The unavailable client interfaces exist in source.

Units

Entitlements are not quantities. Document edits made under a later entitlement still store canonical SI quantities.

Behavior

The installed portal is UnavailableAccountPortal. Registration, session initiation, and renewal return account_unavailable. Cancellation does not open a session. An open session does not grant an entitlement. EntitlementAuthorization grants an engineering capability only from a consistent snapshot whose entitlement is valid and lists that capability. document.save and document.recover stay available and do not authorize document.edit or document.read. CredentialStore is separate from settings. The production store retains nothing. Deterministic fixtures are test support in tests/support/account_fixture.h and are not installed. The bathafrica website team implements the API. Password login, browser handoff, endpoint paths, token formats, and offline entitlement behavior are provisional.

Errors

authorization_required when no policy is installed. account_unavailable when the production portal or credential store is used. authorization_denied when the snapshot is contradictory or the entitlement is absent, expired, or revoked. entitlement_unavailable when a ready portal's consistent snapshot says the website did not answer. cancelled when the caller cancels. stale_document after a document is closed through the command registry.

Limitations

Website login, HTTP account transport and a production credential store remain planned in this OpenSite snapshot. Local settings and document-workspace operations, plus save/recovery, are allowed by the default policy. Protected engineering capabilities still require a configured portal and entitlement. The development allow-all policy is not production enforcement. Edition names do not establish prices, durations or legal terms.

Available hosts

The application account interface is available to the headless host, desktop account seam and Python account snapshot. The configured production portal remains unavailable; no working website sign-in is claimed.

Licensing and access

Identity and entitlement stay separate. The desktop does not open the nopCommerce database and does not keep a second password store. No endpoint, token, or offline lease is selected.

Verification evidence

Repository evidence references (not rerun for this publication): The local record is docs/verification/Phase-5A-Acceptance.md. The test is application.account. There is no website login test.


Try this workflow

Discover commands — a worked lesson with expected results.

Documentation basis

Source-reviewed against development commit 77c3fee13944bcc4b5d487c77eb1f82fbe4c6ea7, branch feature/phase-13c-properties-python-expressions. This review inspected the implementation and repository evidence; it did not run the Windows application or repeat CTest.

  • src/application/account.cpp
  • src/application/command.cpp

OpenSite overview · Reference · Guides