Clear records.
Deliberate authority.

A company starts with actual people.

Use a confirmed STATIC account to create a company workspace or accept an invitation addressed to that account’s email. Choose your company name, purpose, sector and work display name. You become this workspace’s owner. Office, Connect and Mail launch links are added as a starting point; each app retains its own accounts and permissions.

The first release supports five owned companies per account, fifty joined companies per account, one hundred accepted members per company, five hundred register records including archived records, two thousand explicit relationships, one thousand prepared changes and one hundred active invitations per company.

Workspace roles.

Company roles come from current database membership. A work title, profile label, agent record or app link cannot grant authority. Enterprise membership does not provide access to another STATIC product.

Invite deliberately. Accept explicitly.

Owners and admins create a private invitation link bound to the intended account email. Links expire after seven days, can be withdrawn, work once and require the recipient’s confirmed email. Creating a link does not send email. Share it directly with its intended recipient. The invitation remains valid only while its issuer retains the required authority and account access.

The recipient reviews the company and role, supplies a company display name and explicitly accepts. Invitation secrets are hashed on the server. The join page holds only a pending invitation in this tab’s session storage while sign-in completes, then removes it after acceptance. A wrong-account visitor receives no company invitation preview.

The Company Graph and operating registers.

The graph counts actual accepted people and active records across Teams, Apps, Projects, Agents, Devices, Vendors and Policies. Its category spokes describe the company taxonomy; additional cross-category lines reflect explicit recorded relationships. Select a category to inspect its entries. Add relationships between actual company members and records. Archived records and departed members do not appear as active graph nodes.

Keep objectives, responsible people, milestones and review dates with the work. Policy reading acknowledgments attach to the exact saved version; changing a policy requires a new reading record. Lifecycle checklists document onboarding, transitions or offboarding. They do not themselves revoke app or company access.

Devices and agents are declared registers. They do not collect telemetry, enforce device policy, connect or execute an agent, pause an external process or verify an external authority ceiling. Vendor costs are manual amounts with two decimal places, grouped separately by currency and billing period. No payment, live invoice, bank access or conversion takes place.

S.A.G.E. Enterprise and human decisions.

The operating brief is derived from this company’s recorded dates, proposals and policy readings. It is not an AI chat session and does not run actions automatically. READ → UNDERSTAND → PREPARE → ACT → COMMIT describes the authority sequence.

Editors and above can save ordinary records directly or prepare a proposed record change with its reason. Owners and admins review ordinary proposals. Approved changes can be committed only while the target version and reviewer’s authority still match. Changed or archived targets require a new proposal; a stale approval cannot silently overwrite newer work.

Membership role changes and removals require the owner’s review and a typed COMMIT at application. Workspace ownership is a separate offer requiring the target member’s acceptance and the exact company name. The former owner remains an admin. This transfers control of this software workspace, not legal ownership of a business.

Company privacy and retained records.

Accepted company members can read company records, relationships, decisions and recent activity. Owners and admins can see invitation emails and export company records. Authentication and current membership are checked on every request. The browser revalidates visible workspace access every twenty seconds and on return to the tab; account changes clear the private screen. Revocation blocks subsequent requests but cannot recall information already viewed or exported.

Records are stored on STATIC’s connected backend with transport security and provider storage protections. This workspace is not end-to-end encrypted. Do not place passwords, API keys or sensitive private files in this operating register. This release introduces no file vault, external directory sync, single sign-on federation, device management, security monitoring or compliance certification.

The activity view shows the latest one hundred events; the server retains up to ten thousand recent activity events per company. It is an application activity record, not an independently notarized or immutable ledger. Normal provider backups follow the provider’s backup lifecycle.

Export, leave, transfer or delete.

Owners and admins can download company JSON or a printable HTML report. Export includes current company records, membership, relationships, policy acknowledgments, available decision summaries and recent activity. Decision payloads and invitation secrets are not included. These exports are reference copies, without an automatic import or restore workflow. Keep downloaded material somewhere you control.

Archiving preserves an operating record for later restoration. A non-owner can leave and loses workspace access; company business records remain with the company. Deleting a non-owner’s STATIC account removes their membership and clears account references while company records stay with the company.

An owner must transfer workspace ownership to an accepting member or delete the company before leaving or deleting their STATIC account. Permanent company deletion requires the exact company name and removes Enterprise membership, records, relationships, invitations, decisions, policy readings and activity for everyone. Independent apps, previously downloaded copies and normal provider backups remain outside that action.

The first operating release.

Company Now, the Company Graph, accepted membership, registers, relationships, invitations, reviewed changes, current-version policy readings and exports are available today. The wider Enterprise roadmap retains connected directory and identity systems, external execution, telemetry, lifecycle automation and deeper business-app integration. A manually maintained record is never presented as a connected system.

The original boardroom scene and titanium emblems are STATIC campaign artwork. They do not depict a real customer, company, workforce or measured operating statistics.