GC-1
The record of who authorized what, within which scope, and what evidence exists for the outcome. The other parts depend on it.
How GC-1 works
Knowing which AI system performed an action is only part of the picture. Organizations require evidence of who authorized it, what was permitted, and what happened. GuardianChain brings these elements together in a record that can be inspected and verified.
Design-partner stage
Record what actually happened.
Did the action stay within those limits?
We record who authorized the AI to act.
We capture the scope, limits, and duration of that permission.
We link the AI’s actions to their recorded outcomes.
Who authorized the AI to act, what was permitted, and for how long? A prompt alone is not a clear record of permission.
Logs held by the tool that did the work are not a record the recipient can lean on.
Work moves between assistants, editors and services. Context and limits are lost at each hop.
The party receiving the work needs to inspect it without trusting the producer's summary.
Security and incident teams need evidence they can reconstruct from, and a path back.
GuardianChain connects who authorized an action, its permitted scope, the consequential decision, and independently verifiable evidence of the outcome.
A named, accountable person or role grants the action. A prompt or API key is not a grant.
What may be done, on which resources, under which conditions, and until when. Refusals and restraint are recorded too.
The consequential decision made by an agent or automated system, linked to the authority and scope it relied on.
A portable record a recipient can inspect independently, without trusting the producer's own summary.
Identity, orchestration, tool connectivity, policy, and logging all matter, and we build on them. However, none of these systems alone establishes a complete chain from human authorization to a
verifiable outcome.
| Criteria | Identity providers | Agent orchestration | Tool connectivity | Policy engines | Logs and observability | GuardianChain architecture |
|---|---|---|---|---|---|---|
| Primary job | Authenticate people, services and agents | Plan and run multi-step agent work | Connect agents to tools and data | Evaluate rules at decision time | Record events inside each system | Connect everything, alongside the systems above |
| Who authorized | Partial coverage | Requires other tools | Requires other tools | Requires other tools | Requires other tools | Architectural focus |
| Permitted scope | Requires other tools | Partial coverage | Partial coverage | Yes | Requires other tools | Architectural focus |
| Decision linked | Requires other tools | Yes | Yes | Partial coverage | Partial coverage | Architectural focus |
| Independently checkable | Requires other tools | Requires other tools | Requires other tools | Requires other tools | Partial coverage | Architectural focus |
Three architectural roles, with workflow fit and availability qualified through design-partner discussions.
The record of who authorized what, within which scope, and what evidence exists for the outcome. The other parts depend on it.
How GC-1 worksWhere a person grants, bounds, watches and ends a machine session, so authority is explicit at the moment it matters.
How GuardianBridge worksA statement a recipient can check without trusting the producer: what was claimed, by whom, under what authority, with what support.
How FactReceipt works



Controlled research, not a forecast of routine failure. Read the sources and their limits
We are working with a small number of teams that have a real delegation, handoff or reconciliation problem. You get direct access to the builders and influence over scope. Applying implies no platform access, commitment or guarantee.
Inquiries are stored only to respond and evaluate partnerships. Do not send secrets or sensitive evidence. Read the privacy notice.
This records your interest only. Email delivery is not active yet.
The tools behind this website, alongside selected names from the wider GuardianChain stack. Directory listings are not live platform integrations, partnerships or endorsements.
Tools used to build and operate this informational site.
Attached to the workspace. Email sending is not implemented.
Referenced in the GuardianChain technology directory. Not a live integration on this site.
Names and marks belong to their respective owners, shown unmodified for identification. No affiliation or endorsement is implied.