This canonical paper page includes Commercialization Proof and Related Resources.
ARXIV:2603.18829 · AGENT GOVERNANCE · SUBMITTED 20 MAR · 21:29 UTC · FRESHNESS STALE
ARXIV:2603.18829AGENT GOVERNANCESUBMITTED 20 MAR · 21:29 UTCFRESHNESS STALEMarcelo Fernandez · arXiv
A formal protocol for secure and auditable admission control of autonomous agents in enterprise environments.
Opportunity summary
Pain A formal protocol for secure and auditable admission control of autonomous agents in enterprise environments.
Evidence 0 refs | 0 sources | 50% coverage
Blocker Evidence verified
A formal protocol for secure and auditable admission control of autonomous agents in enterprise environments. ACP is the admission control layer between agent intent and system state mutation: before any agent action reaches execution,…
Agent Control Protocol (ACP) is a formal technical specification for governance of autonomous agents in B2B institutional environments. ACP is the admission control layer between agent intent and system state mutation: before any agent…
ScienceToStartup currently rates this 8.0/10 on the public viability pass. Specification and implementation: https://github.com/chelof100/acp-framework-en A public repository is linked, so build verification can inspect implementation evidence instead of treating the paper as PDF-only.
Agent Governance moved forward this cycle; last verified April 2026. Public score 8.0/10. Implementation evidence is present through a linked repository.
Continue into Read for claims, analysis, references, and neighboring papers.
mobile layout uses overflow-hidden min-w-0 break-wordsOpportunity summary
Score8.0Public score shown from the verified overall while the stale axis breakdown refreshesAnalysis summary
A formal protocol for secure and auditable admission control of autonomous agents in enterprise environments.
Loading BUILD…
Paper Pack
10.48550/arXiv.2603.18829A formal protocol for secure and auditable admission control of autonomous agents in enterprise environments.
Abstract
Agent Control Protocol (ACP) is a formal technical specification for governance of autonomous agents in B2B institutional environments. ACP is the admission control layer between agent intent and system state mutation: before any agent action reaches execution, it must pass a cryptographic admission check that validates identity, capability scope, delegation chain, and policy compliance simultaneously. ACP defines the mechanisms of cryptographic identity, capability-based authorization, deterministic risk evaluation, verifiable chained delegation, transitive revocation, and immutable auditing that a system must implement for autonomous agents to operate under explicit institutional control. ACP operates as an additional layer on top of RBAC and Zero Trust, without replacing them. The v1.13 specification comprises 36 technical documents organized into five conformance levels (L1-L5). It includes a Go reference implementation of 22 packages covering all L1-L4 capabilities, 51 signed conformance test vectors (Ed25519 + SHA-256), and an OpenAPI 3.1.0 specification for all HTTP endpoints. It defines more than 62 verifiable requirements, 12 prohibited behaviors, and the mechanisms for interoperability between institutions. Specification and implementation: https://github.com/chelof100/acp-framework-en
Source availability
PDF linkedThe paper record includes a public PDF URL.
Extraction status
Derived fallbackRead summaries are estimated from adjacent metadata, not verified extraction rows.
Proof status
verified0 refs; 0 sources; 50% coverage.
What was readable
Derived fallback: Estimated from adjacent evidence; not verified from source.
Viability
Time to MVP
Commercial
Export
Preparing verified analysis
Dimensions overall score 8.0
PROBLEM
A formal protocol for secure and auditable admission control of autonomous agents in enterprise environments. ACP is the admission control layer between agent intent and system state mutation: before any agent action reaches execution, it must pass a cryptographic admission chec...
METHOD
Agent Control Protocol (ACP) is a formal technical specification for governance of autonomous agents in B2B institutional environments. ACP is the admission control layer between agent intent and system state mutation: before any agent action reaches execution, it must pass a cr...
RESULT
ScienceToStartup currently rates this 8.0/10 on the public viability pass. Specification and implementation: https://github.com/chelof100/acp-framework-en A public repository is linked, so build verification can inspect implementation evidence instead of treating the paper as PD...
WHY NOW
Agent Governance moved forward this cycle; last verified April 2026. Public score 8.0/10. Implementation evidence is present through a linked repository.
Agent Control Protocol (ACP) is a formal technical specification for governance of autonomous agents in B2B institutional environments.
Directly and explicitly stated in the abstract as the opening definition of ACP.
partial
ACP is the admission control layer between agent intent and system state mutation: before any agent action reaches execution, it must pass a cryptographic admission check that validates identity, capability scope, delegation chain, and policy compliance simultaneously.
Directly stated in the abstract describing ACP's core function and the specific checks it performs.
partial
The v1.13 specification comprises 36 technical documents organized into five conformance levels (L1-L5).
Directly stated in the abstract with specific numeric details about the specification's structure.
partial
It includes a Go reference implementation of 22 packages covering all L1-L4 capabilities
Directly stated in the abstract with specific counts for packages and conformance levels covered.
partial
ACP defines the mechanisms of cryptographic identity, capability-based authorization, deterministic risk evaluation, verifiable chained delegation, transitive revocation, and immutable auditing that a system must implement
Directly stated in the abstract as a list of specific mechanisms ACP defines for system implementation.
partial
ACP operates as an additional layer on top of RBAC and Zero Trust, without replacing them.
Directly stated in the abstract, clearly positioning ACP relative to other security models.
partial
51 signed conformance test vectors (Ed25519 + SHA-256)
Directly stated in the abstract with specific numeric and cryptographic algorithm details.
partial
It defines more than 62 verifiable requirements, 12 prohibited behaviors
Directly stated in the abstract with specific numeric counts for requirements and prohibited behaviors.
partial
Paper-native neighborhood for concepts, methods, materials, markets, and competitors. Missing lanes stay labeled instead of disappearing behind commercialization gates.
Concepts
Methods
Materials
Markets
Competitors
A formal protocol for secure and auditable admission control of autonomous agents in enterprise environments.
Segment
Agent Governance
Adoption evidence
Public code linked for build inspection
Commercial read
8.0/10 public viability
Direct
Adjacent
Substitute
Unknown
No indexed public discussion is attached to 2603.18829 yet. That is a visibility signal, not a blank module: the monitor is watching the public channels below.
Hacker News
Not indexed yet
Not indexed yet
Bluesky
Not indexed yet
Preview the source document here, or use the hero PDF action for a new tab.
CITED BY
No citing papers are indexed in the public S2S graph yet. This is an explicit zero-signal state, not a hidden lookup.
Foundation
Extension
Commercially relevant
Conflicting
Owned Distribution
Get the weekly shortlist of commercializable papers, benchmark movers, and proof receipts that matter for product execution.
1/3 checks · 33%
Build Passport
Build passport pending - Proof Lab budget No verified cost estimate / $7.00 cap
status
missing
reason
passport_row_missing
proof status
unverified
cost/budget
No verified cost estimate
confidence low
next verification path
Build brief missing until Build Passport data exists.
Source missing: Build Passport payload.
Experiment plan missing until prototype path is available.
No prototype path attached.
Validation checklist missing until required assets, cost, and regulatory flags are verified.
No checklist artifact is attached to the Build Passport payload.
Derived signals show verified:false until source-backed receipts exist.
Evidence coverage
OpportunityKernel evidence_receipt
0 refs / 0 sources / 50% coverage
stale
Verify missing sources before using this as buyer proof. verified:false
Build readiness
BuildPassport EvidenceState
passport absent
stale
Run Proof Lab or inspect typed missing state. verified:false
Artifact maturity
GitHub and Hugging Face maturity payloads
No public artifact surface observed
stale
Open source artifacts or mark the gap as missing. verified:false
Technical feasibility
partial
Current read
Runnable path is not fully verified.
Evidence
No Build Passport payload attached.
Gaps
Next test
Run minimal reproduction from the Build Passport prototype path.
Market urgency
missing
Current read
Buyer urgency is not verified from source.
Evidence
0 references, 0 sources, 50% evidence coverage.
Gaps
Next test
Collect buyer interview, deployment evidence, or cited demand signal.
Buyer clarity
missing
Current read
No budget owner is verified for this paper.
Evidence
Build tab has no CRM, procurement, or operator source.
Gaps
Next test
Map target operator, economic buyer, and procurement trigger.
Defensibility
missing
Current read
Defensibility signals are missing.
Evidence
No defensibility receipt attached.
Gaps
Next test
Refresh defensibility bars with source receipts.
Integration burden
missing
Current read
No public implementation surface observed.
Evidence
No GitHub or Hugging Face payload attached.
Gaps
Next test
Write integration checklist from prototype path and target workflow.
Capital intensity
missing
Current read
No observed cost estimate is verified.
Evidence
Cost passport has no observed_usd value.
Gaps
Next test
Run cost passport or mark the cost field not applicable.
Regulatory load
missing
Current read
No regulatory classification is attached.
Evidence
Build Passport ledger does not include regulatory flags.
Gaps
Next test
Classify regulatory flags before commercialization planning.
No named scientific founder assigned.
Paper authors are not treated as operators without consent.
People
No named person assigned.
Gaps
Next verification path
Prototype owner missing.
Build Passport does not name an implementer.
People
No named person assigned.
Gaps
Next verification path
Operator workflow not sourced.
No buyer or workflow interview attached.
People
No named person assigned.
Gaps
Next verification path
No GTM owner verified.
No CRM or outreach source attached.
People
No named person assigned.
Gaps
Next verification path
Regulatory need unclassified.
No clinical or regulatory source attached.
People
No named person assigned.
Gaps
Next verification path
ARTIFACTS
No public artifacts yet.
DEFENSIBILITY
Defensibility and confidence evidence pending.
WATCHTOWER
No verified watchtower monitor rows yet.
FORESIGHT
No prediction yet — minted on next Foresight batch.
OPPORTUNITYKERNEL CHANGES SINCE LAST VIEW
No verified OpportunityKernel changes since the last view.
COMPETITIVE LANDSCAPE UPDATES
No verified competitive landscape changes yet.
RELATED PAPER UPDATES
No verified related paper changes yet.
SIGNAL CANVAS HISTORY AND DELTAS
No Signal Canvas history deltas yet.
TIMELINE
Save this paper to start tracking momentum - commits, demos, and score changes appear here.
No tracked events yet.
Score trend will appear after multiple data points.
BUZZ
Buzz trend pending.