The action is enabled and its expiry is shown. The step is re-checked when taken.

Decide who may do what, where, and under which authority.
LOREAXIS is the authority plane for a studio where people and agents work on the same code: tenants and roles, policy decisions, workspace leases, source access per agent, hardware-bound keys, revocation and audit. Nothing acts on context alone.
The one rule
UI context is not authority.
The shell shows context: tenant, project, environment, product. It never implies permission. Every button that acts is a request LOREAXIS may refuse, and every refusal says what happens next and who can change it.
- 01Context is shown[Studio] / ironics-platform / Staging. Navigation, not permission.
- 02An action is requestedAgent Builder-7 · operated by Dana K. asks for
source.pushonrelease/next. - 03LOREAXIS decides, every timeOne of seven outcomes, with an expiry. The action does exactly what the decision allows, and is re-checked at each step.Needs approval · REQUIRE_APPROVAL
Decision states
Seven outcomes. Each one says what happens next.
Every state is a word and an icon, never a colour alone. Only ALLOW enables the action. Sensitive reasons are never shown.
The action is disabled and the screen says who can change it. An explicit deny always wins.
The action waits for the named approvers. Approving creates a new decision, never a patched one.
The case routes to CLEARANCE. No legal, identity or payment detail is ever shown here.
The step needs a fresher sign-in than the session has. Nothing is lost.
Authority ran out. Nothing continues on a stale decision. Refreshing asks LOREAXIS again.
Access was withdrawn. Running work stops at its next step. The operator is told it was revoked.
No decision, an unknown revocation state, or a decision for someone else. Treated as a deny, never as allowed.
Roles and policy
Tenants, projects, roles. Policy decides per action.
A studio is a tenant. Its people hold roles in projects, and agents act only under a named operator. Policy turns a request into one of the seven outcomes, per action and per resource, with an expiry. There is no standing permission to act; there are decisions, and they run out.
- People and tenant membership, with the IRONICS account as the identity.
- Roles per project; approvers named by capability, such as
source.push.approve. - Work Packages: the scope, evidence and limits a piece of work runs under.
- Workspace
- wsp_01m3hbs0g0e229x53fp13ekqy3
- Holder
- Agent Builder-7 · operated by Dana K.
- Under
- WP-3 · Port the inventory UI
- Valid
- Today 09:00 until 17:00
- Grants
- workspace.read · workspace.write · build.run · test.run
Workspace leases
A workspace is held, not owned.
A hosted machine or a runner of yours is used under a lease: who holds it, under which Work Package, with which capabilities, until when. When the lease ends, so does the authority to act in it. CONCORD opens workspaces only inside a lease LOREAXIS issued.
Source access per agent
Read, commit, push. Set for each agent, not for the repo.
Link a GitHub repository once. Then give each agent its own source access: read only, read and commit, or push with the approvals you require. The agent never holds a GitHub credential of its own; LOREAXIS signs each operation under the decision that allowed it.
| Agent | Read | Commit | Push |
|---|---|---|---|
| Agent Builder-7 operated by Dana K. | Yes | Yes | With approval |
| Agent Reviewer-2 operated by Priya N. | Yes | Yes | No |
| Agent Builder-3 operated by Tom A. | Yes | No | No |
Revocation
Revoke a person, an agent or a key and the change reaches every run, lease and runner. Removing a role or membership ends an open connection and its workspace. Running work stops at its next step and the operator is told it was revoked. Nothing waits for a token to expire. Signing a computer out of the studio takes effect within seconds.
- 11:52Dana K. revoked Agent Builder-3
- 11:52Run stopped at its next step · lease ended
- 11:52Tom A. notified: Revoked · REVOKED
Hardware-bound keys
Keys for SSH and runners are created in the machine’s TPM or OS key store by concord ssh setup and never leave it. A key names its machine and its person; a stolen file is not a key.
- Key
- key_01m3hbt7q2n8e4ra6wd0ks9x1c
- Bound to
- win-build-01 · TPM
- Person
- Dana K.
- Exportable
- No
Audit
Every decision, lease, revocation and key event is recorded with who asked, who decided and what the answer was. Retention is set per studio.
12:04:18 policy.decide source.commit ALLOW 12:04:31 policy.decide source.push REQUIRE_APPROVAL 11:52:03 access.revoke agp_…c4qcj by Dana K. 09:00:02 lease.issue wsp_…ekqy3 until 17:00 08:41:55 key.register win-build-01 TPM
Roadmap
Planned, not yet shipped.
- CLEARANCELegal and IP onboarding for contributors, routed without exposing detail.
- LEDGER payoutsPayouts to contributors from the authority record.
- ReleaseRelease authority and evidence gates.
- Enterprise SSOSign in through your studio's identity provider.
Who may do what, where, and under which authority.
Tenants, roles and policy; Work Packages; workspace leases; source access per agent; keys; revocation; audit.
How authorized people and agents do the work.
Workspaces, agent runs, take-over and hand-back, draft pull requests and review. CONCORD never invents authority: each step is a request LOREAXIS may refuse.
About CONCORD →Put every agent under a decision.
LOREAXIS is in early access. Tell us about your studio and we will set up your tenant.