Dry-run one cycle of a sales agent workflow without calling language models. Validate the template and agent types, check budget reservations, generate agent prompts, and record a structured status summary for downstream automation.
Run one tick of the sales business-pod (ADR-164 §4.1, Phase 2). Loads templates/sales.json, validates it against the pod-schema, resolves agents against ruflo's agent registry, reserves budget via the Phase-2 file-based stub ledger (atomic SQLite tracker is Phase 3 per ADR-164.1), constructs per-agent dry-run prompts, posts a summary envelope to room "sales" via the federation_bbs_publish JSONL backing store, and emits a structured {podName, tickId, agentsRan, totalUsd, envelopeId, status} line for /loop ingestion. Dry-run by default; --live is reserved for Phase 3.
Review the instructions the agent will receive before you install.
Surfaces pod-tick.mjs as a single-shot skill for the sales pod. Use when
Claude Code needs to demonstrate, smoke-test, or schedule one iteration of
the sales autopilot without spawning real LLM workers.
Implementation: scripts/pod-tick.mjs.
--pod-template, --base-path, --dry-run / --live,
--budget-cap-usd, --tick-id). --live is refused with exit code 3
in Phase 2.templates/sales.json).validatePodTemplate(json) — schema in
v3/@claude-flow/cli/src/business-pods/pod-schema.ts and inlined in
pod-tick.mjs so the script runs without a built CLI. Throws with a
JSON-pointer path on the first violation.agent.agentType against KNOWN_AGENT_TYPES. Unknown
types abort with exit code 2 and an actionable error.min(budgetUsdPerRun, --budget-cap-usd) USD against the
file-based ledger at <base-path>/budget/<roomId>.json. Honors
reservationExpiryMs (default 60_000 ms, bounded to [5000, 300000]
per ADR-164.1 §3.2). TODO(adr-164.1): swap the file ledger for the
atomic SQLite tracker in Phase 3.--dry-run they are logged to stderr and the
model is never invoked.claude -p --max-budget-usd
reporting).pod-status envelope to the Phase-1 backing store at
<base-path>/.agentbbs/room-<derivedRoomId>.jsonl so subsequent
federation_bbs_watch calls see the tick.{podName, tickId, agentsRan, totalUsd, envelopeId, status}.0 — tick succeeded (status === 'success')2 — invalid template / unknown agent type / budget exhausted / arg error3 — --live requested (refused in Phase 2)--live mode: dispatch each prompt through claude -p headless or a
Managed Agent and capture the actual --max-budget-usd reported spend.pod-marketing, pod-finance, ...) — each gets its
own skill once Phase 3 ships.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Compare models available through the HuggingFace router with chat-ui configuration, research missing models, and write short English descriptions of their architecture and capabilities. Add entries to both production and development configuration files and commit the changes.
Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.
Build a searchable index and relationship graph from ADRs, records of architectural decisions. Import two supported document formats, refresh existing metadata without duplicate relationships, and review summaries of statuses, missing references, and inconsistencies.
Rebuild the index of ADRs, records of architectural decisions, after files or relationship lines are deleted. It clears stored records and relationships, indexes the files still present, and checks that the final record count matches.
Review code changes against accepted Architecture Decision Records, documents that capture agreed design choices. Report violations, outdated references, compliant changes, and areas without ADR coverage, then suggest code fixes or a new decision record where appropriate.
Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.