Guild Stack

Operational route

Host adapter

Map the adapter contract for a new host, add its identity and capability rows, then render the same lifecycle onto it while recording every capability gap as a receipt.

Run a small taskAll use cases

Page evidence

Operational mapChoose the strongest path. Record every drop.
Execution substrate
  1. tmux teamparallel lanes
  2. host-nativenative delegation
  3. subagentbounded delegation
  4. serial classavailable, not wired
Adapter surface
  1. nativefull primitive
  2. wrappedverified wrapper
  3. bridgedtranslated capability
  4. emulatedrecorded substitute
  5. degradedexplicit loss

Host, substrate, and reviewer remain separate axes. The selected lower rung becomes a receipt.

/guild:guild "Add a host adapter and record degraded capabilities." --review=cross

Route comparison

Same job. A visible operating record.

Without a route record

Portability claims drift when missing host primitives are hidden behind generic fallbacks, and a support label starts implying parity it never earned.

With Guild Stack

Guild Stack binds one adapter contract, resolves the strongest substrate, and keeps the availability label separate from its evidence state, so a host stays honest beta until a committed receipt promotes it.

Route stops

Request to verified result.

  1. 01

    Map the contract

    One HostAdapter binds ten operations, capabilities, bootstrap, preflight, dispatch, collect, command surface, package, permissions, model params, memory. The host-neutral lifecycle core stays unchanged.

  2. 02

    Add identity and capability

    Add a guild.host_registry.v1 row (installability, result_adapter, dispatch_selectable, adapter_binding) and write the guild.host_capability.v1 manifest at bootstrap.

  3. 03

    Resolve substrate and degrade

    Dispatch takes the strongest available rung; every missing primitive becomes an explicit degradation receipt, never a silent fallback.

  4. 04

    Publish honestly

    Availability explains the usable path; evidence determines the verified state. Ship as beta until an operator-box receipt lands, and record degradation instead of claiming parity.

Receipts

What the route leaves behind.

  1. 01
    Schema guild.host_registry.v1
    Role

    The canonical host row you add: installability, result_adapter, dispatch_selectable, adapter_binding.

  2. 02
    Path .guild/hosts/<id>/capability.json
    Role

    The guild.host_capability.v1 runtime descriptor written at bootstrap.

  3. 03
    Schema guild.degradation_receipt.v1
    Role

    One receipt per missing primitive across the five loss rungs (native > wrapped > bridged > emulated > degraded).

  4. 04
    Path generated-support-matrix.md
    Role

    Availability beside evidence state; beta remains visible until a committed receipt promotes the row.

Go deeper

Related guides.

Doc

Harness Developers

Reference page for this workflow.

Doc

Host support

Reference page for this workflow.

Doc

Architecture

Reference page for this workflow.

Next

Follow this route through an illustrative run.

The demo traces one bounded task through approvals, specialist lanes, review, verification, and the final run record.
Open demoBack to use cases