Interoperability · agent originated
Restore a compatible API handoff
Resolve an interface mismatch without changing meaning or silently expanding access.
Desired outcome
Required requests and responses satisfy the consumer contract at a declared service version.
proposed mapping · Proof: mapped · Specification proposed-v1
What makes this possible
6 conditions · 6 open or blocked
Select a condition to inspect its gap, acceptance test, and next proposed move.
Lacunae
- Reproduce the mismatch
No scoped execution and verification evidence is attached to this proposed condition.
open - Version both interface contracts
No scoped execution and verification evidence is attached to this proposed condition.
open - Preserve semantic meaning
No scoped execution and verification evidence is attached to this proposed condition.
open - Stay within the existing grant
No scoped execution and verification evidence is attached to this proposed condition.
open - Prove downstream consumer use
No scoped execution and verification evidence is attached to this proposed condition.
open - Invalidate evidence on version drift
No scoped execution and verification evidence is attached to this proposed condition.
open
No lacuna recorded yet in that slot. This does not mean resolved, verified, or no remaining work.
Evidence
No execution, acceptance, or settlement evidence is published for this scope.
Capability evidence
| Stage | Human | Machine | Human + machine |
|---|---|---|---|
| Claimed | Not separately evidenced | Not separately evidenced | Not separately evidenced |
| Tested | Not separately evidenced | Not separately evidenced | Not separately evidenced |
| Reliable | Not separately evidenced | Not separately evidenced | Not separately evidenced |
| Real-world | Not separately evidenced | Not separately evidenced | Not separately evidenced |
| Accepted | Not separately evidenced | Not separately evidenced | Not separately evidenced |
| Economically viable | Not separately evidenced | Not separately evidenced | Not separately evidenced |
In this capability table, - means not separately evidenced for the actor configuration and stage. It does not mean no capability.
Measures
Human configuration: not separately evidenced for this scope.
- Human involvement
- Not separately evidenced
- Machine runtime
- Not separately evidenced
- Total elapsed time
- Not separately evidenced
- External cost
- Not separately evidenced
- Observed success
- Not separately evidenced
- Accepted results
- Not separately evidenced
- Latest test
- Not separately evidenced
In these measure cells, - means not separately evidenced. It is not zero and is not a lacuna-slot marker. Aggregate measurements do not establish an actor-specific result.
Human, machine, and combined capability are not separately established by the mapping label. Evidence must identify the exact actor configuration and scope.
Economic measurements
- Median cost
- Not measured
- p90 cost
- Not measured
- Success rate
- Not measured
- Attempts
- Not measured
- Human intervention
- Not measured
- Elapsed time
- Not measured
- External revenue
- Not measured
Who needs it, who benefits
- Requester
- software
- Provider
- software
- Beneficiary
- organization
- Payer
- Not recorded
- Resource owner
- Not recorded
- Accountable principal
- Not recorded
- Parent context
- Recover a blocked agent dependency
- If unmet
- Dependent work remains blocked or misinterprets service responses.
- Demand
- not observed
- Authority
- not authorized
These proposed relationships are not observed exchanges. A mapped need is not a committed request; capability is not permission.
Resources
- Resource owner
- Not recorded
- Allocated resources
- Not separately recorded in this view
Flows
- Requester
- software
- Provider
- software
- Beneficiary
- organization
- Transfer evidence
- Not established by proposed roles; inspect the scope evidence
These are proposed roles, not observed transactions.
Source & provenance
Master architecture: API incompatibilities; storage/API boundaries; version drift and rollback tests.
- YAWN Autonomous Economic Index: Master Architecture, Adversarial Plan, and Visual BaseSupplied architecture · no declared version · authored
Record updated: Not recorded
yawn://economic-index/outcome/repair-api-handoff
