/hephaestus-network

name: hephaestus-network
description: "Use when the user types $hephaestus-network, /hep-network, or /agentlas-network, mentions @Hephaestus, or asks Agentlas to staff a durable goal from registered Local, owner Cloud, and public Hub agents or teams. The active host LLM staffs each turn; the exact roster remains goal-bound until explicit completion."

Hephaestus Agent Workforce Network

<!-- prompt-module: {"id":"skill.network.host-execution","revision":3,"stability":"fixed-policy","changeTriggers":["release"],"order":0} -->

The active host LLM staffs the task. Agentlas Core federates content menus from registered Local, owner Cloud, and public Hub inventory. No source and no deterministic layer is the decision-maker or a server-side LLM executor.

Source scopes are exact:

• `network`: Local + Cloud + Hub;
• `local`: registered Local packages only;
• `cloud`: the signed-in owner's Cloud packages only;
• `hub`: public Hub packages only.

Before an unpinned search uses the Local source, Core refreshes every active registered source folder and creates a new immutable release when its safe content snapshot changed. This is discovery freshness; a prepared or goal-bound roster remains pinned to its exact release. `network reindex` is a rebuildable card-cache operation and is not required to refresh a registered Local release. New folders still require explicit `local-register`.

Public demos and distribution proof use explicit `hub` scope. They must not use private Local/Cloud inventory as evidence of public availability.

Resolve the runner and sign in

Network can query owner Cloud and public Hub inventory, so establish the same saved Agentlas session before staffing:

RUNNER=""
for c in \
  "$HOME/.agentlas/runtime/current/bin/hephaestus" \
  ./bin/hephaestus
do [ -x "$c" ] && RUNNER="$c" && break; done
if [ -z "$RUNNER" ]; then
  for cache in \
    "$HOME/.claude/plugins/cache/agentlas-core-engine/hephaestus" \
    "$HOME/.codex/plugins/cache/agentlas-core-engine/hephaestus"; do
    newest="$(ls -d "$cache"/*/bin/hephaestus 2>/dev/null | sort -V | tail -1)"
    [ -n "$newest" ] && [ -x "$newest" ] && RUNNER="$newest" && break
  done
fi
if [ -n "$RUNNER" ] && [ "${HEPHAESTUS_AUTH_AUTOPOPUP:-1}" != "0" ]; then
  "$RUNNER" auth ensure >/dev/null 2>&1 || true
fi

The browser opens only when no reusable local sign-in exists. In CI or another headless environment, set `HEPHAESTUS_AUTH_AUTOPOPUP=0`.

Required MCP sequence

First confirm the typed tool menu contains `workforce.preflight_work_order` and that its `_meta.protocolVersion` is at least `2026-08-20.1`. If the tool is absent, the host is still attached to a preflight-less runtime. Do not fall back to model-authoring the strict wire WorkOrder and do not retry the same invalid call. Return the machine-readable boundary `workforce_protocol_upgrade_required`; let the runtime's normal verified auto-update finish, then reload the host/MCP session. An explicit `hephaestus hep-update` remains an operator action, never an implicit skill side effect.

"Absent" must be proven against the host's real tool names, not a guessed spelling. Hosts rewrite MCP tool names: the server is `hephaestus-network`, and Codex, for example, exposes `workforce.preflight_work_order` as `mcp__hephaestus_network__workforce_preflight_work_order` (the dot becomes one underscore; the prefix is the server name, not `agentlas`). Before returning `workforce_protocol_upgrade_required`, search the tool menu for every name containing `preflight_work_order` and `goal_context`. If any match exists, the tool is present — call it. If other `hephaestus-network` tools (for example `context_slice`) are present but these two are not, report both facts; that is not proof of an old runtime. Measured 2026-09-24: a Codex session probed the invented `mcp__agentlas__workforce__goal_context`, found nothing, and halted staffing while runtime 1.2.49 was serving both tools.

Use the Agentlas Core Workforce contracts in this order:

workforce.preflight_work_order(taskBrief=..., roles=..., edges=...)
workforce.search_candidates(workOrderRef=..., sourceScope="network")
workforce.expand_candidates(selectionSessionId=..., candidates=[{slotId, candidateOrdinal}])
workforce.validate_selection(decision={selectionSessionId, decisionAuthor, assignments})
workforce.prepare_execution(selection={selectionSessionId}, federatedSelectionDigest=..., projectDir=..., goalId=activeGoalId?, fullDossier=false)
workforce.validate_execution_receipt(receipt=..., executionPlan=..., toolInventory=...)

Call these exact typed tools directly. Do not enumerate, serialize, print, or search the host's complete `ALL_TOOLS` registry: the sequence and tool names are already specified here, and dumping unrelated schemas spends context without improving staffing.

The source-internal `workforce.fetch_runtime_bundle` call is performed by Core from the pinned original source session/digest. The host must not call it directly or replace it with a slug/`latest` lookup.

The default search response is a projected decision menu. Preserve its source receipts and `selectionSessionId`, but do not echo that projection as `federationResult`; Core resolves and revalidates the full pinned result by session. The final receipt call is local, bounded, and read-only. It validates host-produced evidence and never executes workers or creates a receipt.

The current CLI equivalent is `workforce search --scope network`. A host adapter that does not yet expose typed `sourceScope` must report that wiring gap; it must not silently call public Hub-only search and label it Network. Do not call the legacy lexical router first. Do not turn install count, ratings, invocation history, source precedence, or a deterministic top score into the staffing decision. If a source is unavailable, preserve its finite failure receipt.

1. Perform job analysis

Act as the active top-level orchestrator. Convert the user's task into