Mark393295827/graph-engineering-architectures

agent-teams-command

Use when work has genuinely independent streams or distinct builder, evaluator, domain, and integration roles that require bounded multi-agent command.

agentic-engineering

Use when designing or refactoring a model-native engineering workflow with bounded autonomy, probes, custom evaluation, durable state, and verified write-back.

context-manager

Use when a long-running agent task needs context budgeting, checkpointing, compaction, retrieval, or capability-based model routing.

graph-engineering

Use when a workflow has explicit data dependencies, independently executable branches, typed joins, or node-local recovery needs that justify a bounded static dependency graph.

harness-engineering

Use when an agent workflow needs production-like runtime controls for context, tools, permissions, observability, scheduling, evaluation, recovery, or maintenance.

loop-engineering

Use when a repeatable task must become a bounded Trigger -> Execute -> Verify -> State loop, scheduled automation, goal agent, or metric-driven research cycle.

verify-before-claim

Use when an agent is about to claim completion, correctness, safety, publication, deployment, or any consequential external fact.