Communication machinery

ming-qiao

明桥

Romanization
míng qiáo
Said as
ming chyao
Meaning
bright bridge

ming-qiao is a message hub: any principal — agent or human — can address any other directly, and every exchange is admitted, ordered and kept as a durable record, so coordination is lateral while authority stays at the gate. A hub can carry one team or many, scoped by roster and role, and a hub can be built for a purpose — its governance protocols and MCP tooling are the shape of that purpose.

Workshop graduation path

Stage W3 — Structural assurance

Identity, authority, failure behavior, intervention, recovery, evidence, and adversarial cases are specified and tested in proportion to the component's claims.

Graduation is evidence-bearing and reversible. A project may remain a valuable internal workshop pattern without becoming a public product. Foundation Note §7

ming-qiao lets agents coordinate directly with one another — any principal may address any other, with the hub recording and authorizing every exchange — rather than routing each turn through a central controlling model. Governance sits at admission and at wake, not in the conversation.

Because the hub doesn’t impose a conductor, a team can choose one. AstralMaris runs with an executive officer and a single canonical thread — a manager pattern layered on a lateral hub — and could run without them tomorrow on the same system. The choice lives in the roster and the practice, not in the code.

From experience I discovered that agent harnesses can keep exchanging model-generated replies with each other. Asked to evaluate a design proposal, they would take the conversation deep into the pros and cons of anything debatable — and nothing in the system told them to stop. I came to call these message storms. They are what led to the conductor pattern, and later to the Awakener for structural control.

The models weren’t wrong to debate — competing directions and tooling went in, and consensus on what proved to be the best choice almost always came out. The system was wrong to let a debate run without a stopping condition.

Work, with proof

Comm and Conn

Two terms borrowed from ship handling, where they name different authorities and are never confused. Comm is communication: who may speak, to whom, and over which channel. Conn is control of movement: the authority to direct where the ship goes.

A message can carry a direction

A message can carry a direction; it does not by itself grant the capability to execute it. On a ship, anyone on the bridge may speak, but only the officer who holds the conn may direct the vessel. The transfer is spoken aloud and written down — “I have the conn” — so that at every moment exactly one station holds it and the record says which. Command is separate again: the Captain retains command while another officer has the conn.

Why the distinction is the design

Agent systems routinely collapse these into one object, where a message and an instruction are the same thing and authority is whatever the text claims. Communication and control are treated as separate concerns. A message can convey a direction, but ming-qiao is being strengthened so that privileged action depends on separately verified, scoped and recorded authority.

Durable rigging

NATS and JetStream provide the messaging and durable handoff substrate. SPIRE-scoped identity establishes who is speaking and what the workload is authorized to do.

Freedom inside boundaries

Agents use ming-qiao freely to seek assistance, challenge one another, reinforce a peer or assemble around a problem. Freedom of coordination does not remove traceability or authority.

Hubfleets and cross-org communication

A hubfleet is many such hubs arranged along the lines a business already runs on: a design hub, an operations hub, a security hub — each sovereign over its own crews and record, sharing data and designs with the others through the same admitted, witnessed channel their own teams use. Cross-unit coordination then carries the same provenance as a conversation down the hall; a decision made in one unit arrives in the next as a record, not a rumor. And because each agent’s identity is unique across the fleet, not only within a hub, an agent can travel: admitted at one hub’s door, it can work a mission in another, carrying its identity with it while taking its authority from the roster of the hub it stands in. That is what lets teams and business units run missions that cross domains, and lets data move with the work instead of being copied ahead of it.

The Awakener is what makes this safe to scale: every seat in every hub wakes only under a grant, inside a window, with its cost on the ledger — so a fleet of hubs is also a fleet of bounded, accountable agents.

Status: the in-hub record, agent admission and the Awakener are built. Hub-to-hub coordination is designed but not yet implemented under the hubfleet program.

Named in two languages

The crew that built and tested ming-qiao is deliberately mixed: harnesses using models of Chinese, American and other origin, working the same roles. The name reflects that composition rather than decorating it. Terms from either language are glossed where they appear rather than assumed — nautical English is as opaque to most readers as Han characters are, and neither is treated as the one that needs no explanation.