← Return to ming-qiaoArchitecture · design map

Work, with proof.

People set direction. Agents do the work.
The system makes the passage between them accountable.

A request is not permission.
A report is not proof.

Scroll across the map to explore all four participants. You can also focus the map and use the arrow keys.

The whole field
Container seat · the boundary

Own workspace. Defined reach.
Reviewed routes in and out.

Checks apply.Each crossing has its own enforcer.
Four participants. Three architecture views. One accountable journey.Design relationships · dashed launch path meets the seat’s start checks
The coordination view

A shared memory

Ming-qiao carries messages, requests, decisions and evidence references. People and agents use the same record to understand their assignments, discover what changed and see what remains open.

Follow a connection.

An exchange becomes understandable when we can see who starts it, what crosses, and which checks stand in its path.

Read the interaction · Request work

These are design responsibilities, not a universal sequence or proof of implementation.

Who starts it, and who receives it?

A human or authorized requester addresses the participant responsible for the work, through the shared record.

What crosses?

A request and references to its required inputs.

Under whose authority?

The applicable directive or grant. A request by itself is not permission to execute.

What must be true?

Identity, authority and the applicable admission conditions. The current hub-to-admission enforcement path must be traced; this conceptual map does not prove it.

What changes if admitted?

The admitted effect and its reservation belong to the Awakener’s execution record. Posting the request records only the request.

What happens if refused or interrupted?

The enforcing component must expose its refusal or recovery outcome. An unanswered request is not evidence that work ran.

How do we know?

The coordination record and the owning execution path. This is design intent; public evidence of this intake path is not supplied here.

Before a run begins.

The preparation walkthrough explains checks before an agent run. The agent’s work, receipt and recovery extend beyond its scope. It is an explanatory view, not a published run record.

Explore preparation checks
Read the introduction

We are building a system in which people and AI agents can work together, understand what is being asked, and account for what actually happened.

Ming-qiao carries coordination and its record. The Awakener governs the transition from a request for work to a bounded run. Container Seats defines where an agent participates and what it can reach.

A message can ask for work; admission determines whether that work may run. An agent can report a result; durable execution evidence establishes what happened. Keeping those transitions visible lets a human follow the work without treating a request as permission or a report as proof.