More supported work.
Prepare the right arrangement and keep permitted work moving when its conditions change.
Digital Authority Infrastructure / enterprise and government
Authority
before action.
OSYRA is developing licensable software to create and govern consequential work, check current authority and conditions at the point of action, and retain the decision basis for later review.
Starting with contracts and work orders informed by current credentials and approved requirements, across people-led workflows, automation and AI agents.
In development, supported by private demonstrators and selected internal synthetic testing.
Prepared for Site A
Current credentials and organisation-approved requirements inform the work order.
Assignment changes to Site B
The clinician remains qualified, but authority and requirements for the changed assignment must be established. The affected release does not proceed merely because the earlier approval exists.
Replacement prepared and checked
Once the required Site B authority is separately established, the successor arrangement is prepared and checked. Supported work can proceed, with the original and the reason for change preserved.
Illustration of intended operation, not a production interface. A release decision is separate from confirmed execution.
Generate
Create credential-conditioned contracts and work orders from approved requirements.
Check
Check the current authority and selected conditions for the defined action.
Govern change
Keep affected work connected to the conditions supporting it.
Retain the basis
Preserve the decision basis and linked history for later review.
Intended product functions under development. The organisation remains responsible for its policy and authority.
01 / The authority question
Technical access
is not always authority.
An agent or system may still be able to act after a credential, approval, delegated mandate or other required condition changes. OSYRA is being developed to check the selected current basis for the exact action.
Understand the action boundary02 / The infrastructure ambition
A common foundation.
Specific actions.
The long-term ambition is reusable digital authority infrastructure across enterprise, government and institutional systems. The near-term work remains focused: one workflow, a credible existing-system comparison and evidence of practical value.
Explore a bounded evaluationThe intended contribution
Better work.
Less work around it.
Credential-conditioned contracts and work orders are the first application. The value must be established in the workflow and in the effort needed to deliver it.
Less checking and rework.
Reduce routine matching, affected-work reconciliation and repeated implementation effort.
Clearer accountability.
Connect the defined action to its authority, decision basis and linked history.
Intended outcomes to establish through comparison, not achieved returns.
Why this matters now
As AI takes action,
accountability must keep pace.
Releasing a work order, committing a purchase or changing an assignment has consequences. Organisations need to define what people and automated systems may do, manage changes and retain a clear basis for review.
Regulation and governance frameworks increasingly address transparency, oversight and accountability. Requirements differ by jurisdiction and use.
Explore the regulatory contextThe work-order lifecycle
One assignment.
A connected history.
Follow a synthetic arrangement from preparation to a separately authorised replacement and later review.
Illustrative progression, not operational status.
01 / Generate
The credentials shape the work order.
Selected credential state, site requirements and organisation-approved templates inform the clauses, parameters and execution conditions—not just a check on a finished document.
The aim: less manual matching of credentials and requirements to contractual terms.
Illustrative work order REV 01 · Prepared
- Professional credential
- Current throughout
- Assignment
- Site A
- Terms and parameters
- Site A requirements • approved assignment terms
- Execution authority
- Not yet checked for release
- Execution effect
- Not attempted
Preparation basis recorded
- Credential and role requirements selected
- Approved template and relevant terms applied
- First work-order version prepared
02 / Authority
Who or what may release this arrangement?
The clinician remains qualified. Separately, the workflow checks whether the acting person, agent or service has the required delegated authority for this site, role and assignment.
The aim: useful automation within a defined mandate—not permission inferred from system access.
Illustrative work order REV 01 · Within Site A scope
- Professional credential
- Current throughout
- Assignment
- Site A
- Terms and parameters
- Site A requirements • approved assignment terms
- Execution authority
- Release permitted for Site A only
- Execution effect
- Not attempted
Authority basis recorded
- Professional credential remains current
- Delegated release scope checked for Site A
- No action has yet been executed
03 / Release
The person is still qualified. This release is held.
The assignment is moved to Site B. The original work order and the agent’s Site A mandate do not establish the required basis for the new destination. Technical access remains available; the affected release waits.
The aim: stop the unsupported release without treating the professional as globally invalid.
Illustrative work order REV 01 · Hold release
- Professional credential
- Current throughout
- Assignment
- Site B requested / Site A terms
- Terms and parameters
- Original Site A terms cannot authorise Site B
- Execution authority
- Site B authority not established
- Execution effect
- Not attempted
Hold and reason retained
- Site B requested before execution
- Current requirements and authority rechecked
- Release held; no Site B action attempted
04 / Change
Replace the affected work. Preserve its history.
A separately authorised Site B grant is received and checked. A successor work order is then prepared using the receiving site’s approved requirements, linked to the original, and checked for release. New terms alone cannot create authority.
The aim: less chasing and reissuing, with affected versions and dependencies kept connected.
Illustrative work order REV 02 · Replacement checked
- Professional credential
- Current throughout
- Assignment
- Site B
- Terms and parameters
- Site B requirements • approved receiving-site terms
- Execution authority
- New Site B grant checked
- Execution effect
- Not attempted
New release basis retained
- New Site B authority recorded separately
- Revision 02 prepared and linked to revision 01
- Original retained; new conditions rechecked
05 / Review
Understand what supported the work.
In this fictional sequence, the new release is permitted after its required basis is retained. An execution attempt follows and the receiving workflow confirms that release. A reviewer can distinguish the earlier hold, the new authority, the successor and its recorded effect.
The aim: easier review, without substituting a later explanation for the basis used at the time.
Illustrative work order REV 02 · Release confirmed
- Professional credential
- Current throughout
- Assignment
- Site B
- Terms and parameters
- Site B requirements • approved receiving-site terms
- Execution authority
- Site B release permitted
- Execution effect
- Receiving workflow confirmed release
Decision and effect linked
- Original Site A version and hold preserved
- New Site B basis retained → release permitted
- Attempt recorded → receiving release confirmed
Illustration of proposed operation, not a live product test or legal contract. Organisation-approved terms and substantive authority remain the institution’s responsibility. Verification outages and uncertain execution are separate scenarios.
What would make it worth adding?
Stronger handling of a specified condition, or equivalent control with materially lower delivery or review effort. If existing tools satisfy the requirement at comparable or lower total effort, adding OSYRA may not be justified.
Explore the evaluationWho benefits
Operate it.
Deliver it.
Build it into your product.
The customer’s operational result and the partner’s delivery model are separate questions. Both need to work.
Enterprise
Potentially less routine checking, fewer unsupported releases, less affected-work reconciliation and more supported work completed.
Explore customer valueTechnology integrators & delivery partners
A reusable selected capability that may reduce repeated engineering, testing and review across related workflows, provided delivery and support economics remain worthwhile.
Explore partner deliveryGovernment & public institutions
Defined institutional rules, controlled work, named accountability, human review and an inspectable decision basis.
Explore public-service workSoftware platforms
A selected component that could sit alongside existing identity, policy, workflow or automation products rather than replace them.
Explore platform fitProcurement and supply chains
What happens when a supplier changes after an order is prepared? Explore how the proposed approach could support a separately authorised replacement. The potential value extends from suppliers and operational delivery partners to buying organisations and end customers.
Beyond the ordinary lifecycle
When conditions are uncertain,
the questions change.
Credential fallback, uncertain-execution recovery and longer-term resilience need their own evidence. An ordinary lifecycle test does not establish them.
Verification is unavailable.
Which institution-permitted alternatives and limits apply? Missing information remains uncertainty.
Explore credential fallbackThe execution outcome is unclear.
What happened before retry or correction? Permission, attempt and external effect remain distinct.
Explore recovery and resilienceControl what agents execute.
AI agent governance includes the authority for a consequential action. Technical access alone does not establish the current business mandate. OSYRA’s proposed contribution connects that check to the work, its changes and its decision history.
Development and evaluation
Start with a workflow.
Establish the value.
Private demonstrators and selected internal synthetic testing provide the starting point. Production integration, independent assurance and customer value remain to be established.
Development and evaluationA practical next step
Compare one workflow and a relevant changing condition against the organisation’s existing approach.
Evidence matched to the question
Relevant demonstrators and supporting material can be considered within an agreed evaluation scope.
Start with the work
What changes in
your workflow?
Bring one non-confidential example and the outcome that would make a difference.